Solutions
Managed hosting
We run it. You still own it.
The problem
Why this is harder than it looks
Self-hosting is an operating commitment, not a licensing decision. Someone has to patch it, watch it, back it up, prove the backup restores, and plan the upgrade before the version you are on goes end-of-life. Most organisations that struggle with open source did not struggle with the software — they underestimated the operating load.
Method
How we run it
Environment design
Sized on measured load rather than a guess, in a UK or EU region, defined as code. In your AWS account or on our platform — the build is identical.
Backup and tested restore
Backups to your retention policy, and a restore actually performed on a schedule. An untested backup is a belief, not a control.
Monitoring and response
The Grafana stack we would deploy for a client, pointed at your platform, with alerting into our on-call rota to agreed response targets.
Patching and upgrades
Security patches assessed and applied within the SLA. Major upstream upgrades planned, tested in non-production, and scheduled with you — never sprung on you.
Quarterly service review
Measured figures: uptime, incidents, response times against target, patches applied, upgrades due. Whether or not the numbers flatter us.
What you get
- Managed environments for production and non-production
- Backups with a documented, tested restore procedure
- Monitoring, alerting and 24/7 on-call at the Critical tier
- Security patching within the SLA
- Planned major upgrades on an agreed cadence
- Quarterly service review with measured figures
- Full administrative access to your own systems, always
What is out of scope
Stated here rather than discovered in month three.
- Hosting outside the UK or EU. We do not offer it, including on request
- Running platform versions past upstream end-of-life. Upgrading is a condition of continued support, not an upsell
- Supporting infrastructure we cannot reach or code we did not write and cannot review
- Unlimited configuration changes. There is a fair-use change allowance; beyond it, changes are quoted as services
What it costs
Per environment per month, sized on users and load. Non-production environments are charged at a lower rate.
Questions
Things people ask
Our cloud account or yours?
Either, and the price is the same. In your account you see the infrastructure bill directly and keep the commercial relationship with the cloud provider; on our platform it is one invoice. Most clients above a certain size prefer their own account.
What happens if we leave?
You keep a running system. If it is in your account, nothing moves at all — we hand over the runbooks and remove our access. If it is on our platform, we migrate it to yours as a scoped piece of work. There is no exit fee and no hostage-taking.
Can you host outside the UK and EU?
No. Not as a negotiating position — we do not operate in other regions, so we cannot promise a standard of service there that we could meet.
How do you size an environment?
On measured load from your existing system where one exists, or on comparable deployments where it does not, and then reviewed after ninety days against actuals. If we oversized it, we resize it down and the price follows.
Other services
Deployment & configuration
Design, deploy and configure an open-source platform against how your organisation actually works.
How it worksData migration
Profiling, mapping, dry runs at production volume, and reconciliation reporting at every stage.
How it worksSupport & maintenance
Annual support against a deployed platform, with response targets and a quarterly review.
How it worksTalk to someone who will tell you if it is a bad fit
A scoping conversation, not a sales call. We will tell you what the platform does today, what it would cost, and where the risk sits.