BuildX Assurance
Ongoing care for the operational system we built for you.
After BuildX delivers, the platform enters BuildX Assurance. Security patches, dependency updates, server maintenance, monitoring, and bug fixes against the accepted spec. Your system stays healthy. Your team stays free of the operational debt that takes unmaintained custom software offline.
Monthly care plan
Sized
To the build. Per-build band, indicative. Billed monthly. Cancel monthly.
Security patches and dependency updates
Server maintenance, monitoring, backups
Bug fixes against the accepted spec
A defined slice of small changes each month
Who Assurance Is For
BuildX clients after the platform ships. Pilot clients who want ongoing care on the smaller deployment.
Assurance starts the day Pilot or BuildX hypercare ends. There is no gap between a delivered platform and its first month of maintenance, because the same engineers who built it are the ones keeping it healthy.
For clients who prefer not to subscribe, hourly ad hoc support remains available. But Assurance is the default for anyone who wants to know what is in scope this month without asking.
What Assurance Covers
The safety floor, every month.
Proactive, not reactive. The system stays healthy.
01
Security patches and dependency updates
We track upstream advisories, apply patches against the accepted spec, and run the regression set before deploy.
02
Server-side maintenance
SSL renewal, backups configuration, log rotation, and the boring infrastructure work that keeps systems healthy.
03
Uptime monitoring with alerts
Synthetic checks, error tracking, and alerting tuned to the platform we built. Issues find us before they find your team.
04
Bug fixes against the accepted spec
Where a built feature deviates from its written acceptance criteria, the fix is included. No re-billing for what should already work.
05
A defined slice of small enhancements each month
Copy tweaks, field additions, small adjustments. The plan covers a written quantum each month so the platform keeps adapting without a new cycle.
The Bug vs Change Line
We draw the line in writing.
The hardest part of any maintenance subscription is what happens at the edges. Here is the rule, before you sign.
Assurance
Maintenance of the platform as built.
- Security patches and dependency updates
- Server-side maintenance and monitoring
- Bug fixes (feature deviating from accepted spec)
- Defined monthly slice of small changes
New BuildX cycle
Changes to the spec itself. Scoped as a new BuildX cycle, not as Assurance work.
- New features outside the accepted spec
- New modules or workflows
- Changes to a feature's accepted behaviour
- Major dependency or platform rewrites
THE RULE
A bug is the feature deviating from its accepted spec. A change is the spec itself moving. Bugs are Assurance. Changes are a BuildX cycle.
Hosting, Decoupled
Application care is one line. Hosting is another.
Assurance is priced the same whether you own the cloud account or we host it. The work is application-layer regardless. We do not charge more because we happen to also have the AWS console open.
Assurance line
Always present. Sized to the build, not the cloud bill.
Managed Hosting line (optional)
Only when we hold the infrastructure. Cloud cost pass-through plus a transparent management fee.
Either way, the deployment stays portable. Transferable to your account on request, with the keys, the secrets, and the runbook.
Re-scoping Rhythm
Assurance grows with the platform.
The care plan is not a fixed line for life. It scales every time the platform does, in writing, before the new monthly rate begins.
STAGE 1
Platform ships
Initial Assurance scope locked at handover, sized to what was delivered.
STAGE 2
New BuildX cycle
New modules or features ship through a BuildX cycle, adding surface area to maintain.
STAGE 3
Assurance re-scoped
We send a written update naming what is now in scope and the new monthly rate. You sign off before it begins.
STAGE 4
Rhythm continues
Stage 2 and 3 repeat for as long as the platform grows. Every change in scope is in writing.
You always know what is in scope this month. No surprise charges. No drift between what we maintain and what you pay for.
FAQ
Assurance questions, answered.
Anything not on this list? Book a fit call and we will work through it together.
What does BuildX Assurance cover?
Security patches, dependency updates, server-side maintenance, SSL renewal and backups configuration, uptime monitoring with alerts, bug fixes against the accepted spec, and a defined slice of small enhancements each month. Maintenance of the platform as built, every month, proactively.
What is the difference between a bug and a change?
A bug is a built feature deviating from its accepted spec. Bugs are Assurance. A change is the spec itself moving, a new feature, a new module, or a behaviour change to the system. Changes are scoped as a new BuildX cycle. We draw the line in writing so there is no ambiguity in the moment.
How is Assurance priced?
Monthly care plan, sized to the build. The plan scales with what it covers. After each BuildX cycle adds to the platform's footprint, Assurance is re-scoped and re-priced. You always know what is in scope this month.
Do you host the platform or do we?
Assurance costs the same whether you own the cloud account or we host it. Managed Hosting is an optional separate line that appears only when we hold the infrastructure, priced as cloud cost pass-through plus a transparent management fee. The deployment stays portable, transferable to your account on request.
Can I cancel Assurance?
Yes. Cancel monthly. No long-term lock-in. The plan renews each month, and you can stop at any month's boundary. The platform is yours, the code is yours, the deployment is yours.
What happens to Assurance when we scope a new BuildX cycle?
Assurance is re-scoped and re-priced after each new cycle ships. New features add new surface area to maintain, so the plan grows with the platform. Re-scoping is in writing and you sign off before the new monthly rate begins.
Can I get Assurance on just a 30-Day Pilot Build deployment?
Yes. Assurance is available on Pilot deployments too. The plan is smaller because the surface area is smaller. Hourly ad hoc support also remains available for clients who prefer not to subscribe.
If You Do Nothing
Custom software without ongoing care quietly rots.
Dependency updates lag. Security patches stack up. The first incident is a surprise the team is not equipped to handle, and the platform you spent months building goes offline for the wrong reason. Assurance is the boring, non-negotiable layer that keeps the system alive.
Prefer to read first? Get the BuildX Assurance one-pager →