Botlane Managed
We run it. You use it.
Monitoring, updates, backups and maintenance handled by the people who packaged the system — so the thing you bought stays running without becoming somebody's second job.
What kind of engagement this is
An ongoing arrangement with a monthly cost and a notice period. It sits on top of a deployed system; it does not replace one.
Process
How it works
Onboarding, then steady state. The interesting part is what happens when something changes.
- 01
Onboarding
We take over an existing deployment or deploy it first. Access is scoped to what operating the system actually requires, and that scope is written into the agreement.
- 02
Monitoring
Health endpoints and system metrics are watched continuously. You are told about a problem by us, not by your customers.
- 03
Updates
New releases are applied on an agreed cadence, with the release notes shared before the upgrade rather than after it.
- 04
Backups
Backups run on schedule and restores are tested periodically. A backup nobody has restored is a hypothesis, not a backup.
- 05
Change requests
Configuration changes, new integrations and workflow adjustments are requested through a single channel and tracked to completion.
- 06
Reporting
A regular written account of what ran, what was updated, what broke and what was done about it.
Included
What Managed covers
- Continuous health and availability monitoring
- Version updates and security patches on an agreed cadence
- Scheduled backups with periodically tested restores
- Upgrade and rollback execution, including the decision not to upgrade
- Configuration changes on request
- A named operational contact and a single support channel
- Regular written reporting on what happened and why
From you
What we need from you
- A deployed system — either yours or one Botlane deployed
- Scoped operational access to the infrastructure it runs on
- A named business owner who can approve changes
- Somewhere to send reports and escalations
Boundaries
Who does what.
Stated plainly so nobody discovers the line during an incident.
| Stage | Yours | Botlane’s |
|---|---|---|
| Day to day | Using the system and deciding what it should do. | Monitoring, updates, backups, maintenance and operational support. |
| When something breaks | Telling us anything you saw that we could not, and approving changes that affect the business. | Diagnosis, fix or rollback, and a written account of what happened. |
| When something changes | Requesting it through the agreed channel. | Assessing it, saying whether it is Managed scope or Custom work, and doing it or quoting it. |
Not included
What this is not.
Managed keeps a system running well. It does not change what the system does, and it does not make Botlane the owner of your infrastructure.
Cost
How this is priced.
Priced monthly against the systems under management and the environments they run in. We do not publish an uptime figure or a response-time target yet, because we have no production history to back one — see the trust page for what that means. When we can evidence a number, it will appear in the agreement.
Ask for a scoped quoteQuestions
Common questions about Botlane Managed.
Do you publish an SLA?
Not yet. No Botlane system has closed all twelve release gates or accumulated production history, so any uptime or response-time figure would be invented. Commitments are agreed in writing per engagement, and a published SLA will follow real operating data rather than precede it.
Where does the system run under Managed?
On infrastructure you own, in your accounts, under your billing. Our access is scoped to what operating the system requires and is set out in the agreement.
Can we take it back in-house later?
Yes, and the documentation is written for exactly that. The system is a self-hostable release either way — Managed is an operational arrangement, not a lock-in mechanism.
What if we only want updates, not full management?
Say so when we scope it. The line between what you keep and what we take is written into the agreement rather than assumed.
Not deployed yet?
Deploy installs and configures the system first, then Managed keeps it running.