Botlane Deploy
We install it, configure it, and hand you the keys.
A fixed-scope engagement that ends with a running system on your infrastructure, validated against its release gates and documented well enough for your team to take over.
What kind of engagement this is
A one-off engagement with a defined end, not a retainer. When the handover is signed off, the system is yours to run — unless you decide you would rather we did.
Process
What the engagement looks like
Six stages. You always know which one you are in, and each ends with something you can inspect.
- 01
Scope and prerequisites
We agree which system, which environment, and which integrations. You get the prerequisite list up front rather than discovering it mid-install.
- 02
Infrastructure setup
Host provisioning, container runtime, storage, TLS termination and network rules on infrastructure you own.
- 03
Installation and configuration
The pinned release is installed and configured, with secrets supplied at runtime and configuration validated before the system accepts traffic.
- 04
Integrations
The system is wired into the tools and data it needs — the channels, the calendar, the notification path, whatever the system's page lists.
- 05
Acceptance validation
We run the system's acceptance suite and walk its primary workflows with you. You see the results, not a summary of them.
- 06
Documented handover
Credentials transferred, configuration written down, runbook walked through with a named owner on your side. The engagement ends here on purpose.
Included
What you have at handover
- A running system on infrastructure you own and control
- Configuration documented, including every value that was set and why
- An operational runbook covering health, backup, restore, upgrade and rollback
- Acceptance results from the system's own test suite
- All credentials and access transferred to your named owner
- A written record of the exact release version deployed
From you
What we need from you
- Infrastructure to deploy onto — your cloud account or your hardware
- DNS control for the hostname the system will run on
- Credentials for the integrations the system connects to
- A named owner who will hold the system after handover
- Someone available to walk the acceptance workflows with us
Boundaries
Who does what.
Stated plainly so nobody discovers the line during an incident.
| Stage | Yours | Botlane’s |
|---|---|---|
| Before handover | Infrastructure access, integration credentials, availability for acceptance. | Provisioning, installation, configuration, integration, validation, documentation. |
| After handover | Running the system — monitoring, backups, upgrades, support for your users. | The release, the documentation and the release feed. Nothing further unless you add Managed. |
Not included
What this is not.
Deploy ends at handover. Two things sit outside it, and both have their own page rather than being quietly bundled into a quote.
Cost
How this is priced.
Scoped per system and per environment, because a single-host install and a multi-environment rollout are not the same job. We quote against the prerequisite list, not a page rate — ask and we will scope it.
Ask for a scoped quoteQuestions
Common questions about Botlane Deploy.
Do I have to use Deploy to run a Botlane system?
No. Self-hosting is the default path and the documentation is written for someone who is not Botlane. Deploy exists because some teams would rather buy the install than schedule it.
Can you deploy onto our existing Kubernetes cluster?
Systems ship as Docker/OCI images with Compose deployment as the supported default. Deploying onto an existing orchestrator is in scope but is scoped separately, since it depends on your cluster rather than on the system.
What happens if the system needs changes during the deployment?
Configuration and integration work is part of Deploy. Anything that changes what the software does is Custom work, and we will say so at the time rather than absorbing it silently and calling it scope.
Who owns the infrastructure?
You do. Deploy puts the system on infrastructure in your accounts, under your billing, with credentials transferred to you at handover.
Want us to keep running it afterwards?
Managed picks up where Deploy hands over — monitoring, updates, backups and maintenance.