Continuity
Software does not stay finished.
The build ships and the world underneath it keeps moving. Libraries get security advisories, runtimes go end of life, a browser changes something. Assurance is the plan that handles all of that so it never becomes your problem on a Friday evening.
Covered
What the plan handles.
- Security patches, as they are released rather than when something breaks
- Runtime and dependency updates, so the platform does not quietly rot
- Monitoring, with someone reaching a person before a customer notices
- Small fixes and tweaks within the delivered scope
- Defined SLA response times, written into the plan
Not covered
What it deliberately is not.
- New features and new modules, which are a fresh build cycle
- Hosting, which is billed separately through Everydayhost
- Fixing something we shipped broken, which is hypercare and free
The test is simple. A broken thing we built is hypercare. The environment moving under a correctly built thing is Assurance. Anything genuinely new is a build cycle.
Pricing
Custom priced per build.
There is no published rate, and the reason is not coyness. Assurance is scoped against the platform we actually built for you and the level of support you actually want, so it goes into the build proposal alongside the build price. You see the number before you commit to anything, not after.
Plans run from maintenance only through to plans that include a monthly bucket of change hours for tweaks. Each carries defined SLA response times. We also take on platforms built by someone else, though we look at the codebase before saying yes.
Hypercare comes first, and it is free
When a BuildXLR8 build goes live it enters a 60 day hypercare window, longer for more complex builds, at no extra charge and included in the build price. Assurance starts when hypercare ends, so you are never paying us to fix our own defects.
FAQ
Questions about the care plan
What does Assurance cover?
Maintenance, security patches, runtime and dependency updates, monitoring, and small fixes. The test is simple: something we built that broke is hypercare and free. The environment moving underneath something built correctly, a security patch or a library update, is Assurance. Anything genuinely new is a fresh build cycle.
Is it compulsory?
No. You own the code and can maintain it yourself or hand it to anyone you like. Assurance exists because most teams would rather not think about dependency updates, not because we hold anything back without it.
What does it cost?
Custom priced per build, scoped into the build proposal at the time we quote. Publishing a rate would be a guess at your platform's size and support needs, and it would be wrong in both directions.
What happens right after the build ships?
A hypercare window of 60 days, longer for more complex builds, at no extra charge and included in the build price. That is us fixing what we shipped. Assurance starts when hypercare ends.
Does this include hosting?
No. Hosting is billed separately through Everydayhost, and you are free to host on your own cloud instead. Keeping the two separate means you are never stuck with us for infrastructure reasons.
The full build
Put the whole operation on one system you own.
Your whole operation on one system you own, built in 30-day milestone cycles. Priced and approved one milestone at a time, and you can stop after any of them with everything already in your systems.
We keep two Pilot builds in delivery at a time.