Who Assurance Is For
BuildXLR8 clients after the platform ships. Operations Reset clients who want ongoing care on the smaller deployment.
Assurance starts the day Operations Reset or BuildXLR8 hypercare ends, so there is no gap between delivery and the first month of maintenance. The same engineers who built the platform keep it healthy afterward.
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
If a built feature deviates from its written acceptance criteria, the fix is included at no extra charge.
The Bug vs Change Line
We draw the line in writing.
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 BuildXLR8 cycle.
Scoped as a new BuildXLR8 cycle, not Assurance work:
Hosting, Decoupled
Application care is Assurance. Hosting is WebXLR8.
Assurance covers application-layer maintenance, patches, updates, and monitoring, custom-priced per build, no matter where the platform runs. Hosting is separate and never bundled into Assurance.
Assurance
Maintenance, patches, updates, and monitoring. Custom-priced per build, prepaid annual.
Hosting (separate, under WebXLR8)
If you want us to run the infrastructure, hosting is billed separately under WebXLR8.
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 plan is not fixed for life. It scales every time the platform does, in writing, before the new rate begins.
STAGE 1
Platform ships
Assurance scope locked at handover, sized to what was delivered.
STAGE 2
New BuildXLR8 cycle
New modules or features ship through a BuildXLR8 cycle, adding surface area to maintain.
STAGE 3
Re-scoped, then it repeats
We send the new scope and rate in writing. You sign off, and stage 2 starts again on the next cycle.
FAQ
Assurance questions, answered.
Anything not on this list? Book a fit call and we will work through it together.
What does BuildXLR8 Assurance cover?
Security patches, dependency updates, server-side maintenance, SSL renewal and backups configuration, uptime monitoring with alerts, and bug fixes against the accepted spec. New features and changes are scoped as a new BuildXLR8 cycle.
What is the difference between a bug and a change?
A bug is a built feature deviating from its accepted spec, and bugs are covered under Assurance. A change is the spec itself moving: a new feature, a new module, or a change to how something is meant to behave. Changes are scoped as a new BuildXLR8 cycle.
How is Assurance priced?
Custom-priced per build, in the region of ten to twenty percent of the build cost per year, prepaid annual. The plan scales with what it covers, so once a BuildXLR8 cycle adds to the platform's footprint, Assurance is re-scoped and re-priced.
Do you host the platform or do we?
Assurance covers application-layer maintenance regardless of where the platform runs. Hosting is a separate matter: if you want us to run the infrastructure, it is billed separately under WebXLR8, not bundled into Assurance. The deployment stays portable, transferable to your account on request.
What does Assurance not cover?
New features, new modules, and changes to a feature's accepted behaviour are scoped as a new BuildXLR8 cycle, not Assurance work. Hosting is billed separately under WebXLR8.
What happens to Assurance when we scope a new BuildXLR8 cycle?
Assurance is re-scoped and re-priced after each new cycle ships, since new features add surface area to maintain. Re-scoping is in writing, and you sign off before the new annual rate begins.
Can I get Assurance on just a 30-Day Operations Reset deployment?
Yes. Assurance is available on Operations Reset deployments too, and 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. Then one incident catches the team unprepared, and the platform you spent months building goes offline for the wrong reason. Assurance is the layer that keeps it from getting there.