Service
Hosting and maintenance
After launch, the connection still needs supervision. We operate within conditions we agree in writing. This website does not publish SLA percentages.
Who it is for
Teams that do not want the first integration to sit unattended, and that prefer a named operating path instead of informal chat support.
What it includes
- Monitoring of the agreed components
- Planned updates
- Incident response according to the contract
- Continuity practices you approve
Deliverables
- An operating environment
- A support path
- Change notes
- A list of what is in and out of the operating scope
What we need from you
- Access rules for the environment
- Contacts for incidents
- A change window you can live with
- Clarity on who approves production changes
Process
- 1
Agree conditions
Hours, channels and what “down” means.
- 2
Take over
Operate the components in scope.
- 3
Change
Apply updates you approve.
- 4
Review
Look at incidents and remaining risks together.
Questions
Do you publish uptime percentages here?
No. Availability commitments belong in the agreement for each project.
Does maintenance include new features?
Not by default. New tools or systems are a change of scope.
Can we host it ourselves?
Yes. Then this service may shrink to advisory support, or not apply.
Related
Need an operating model after launch?
We will only describe hours, channels and limits in a written agreement — not as marketing claims on this page.
Discuss operations