SolutionsCloud and operations
Managed run and on-call
Upgrades, monitoring and incidents handled by the people who built it, with one of us on call 24/7.
How we deliver it
- We monitor what you depend on, so we hear about a problem before your team does.
- We apply upgrades and security patches on a schedule you can see.
- When something breaks, the engineer on call is one of the five of us.
How it works
The people who built a system are the ones who can fix it fastest. Whether we keep it running depends on your team: some want it handed over, some have nobody to run it, and many want to run it themselves with us behind them.
Day to day
Updates and security patches are scheduled, applied in a window you know about, and reported afterwards. When something breaks, an alert reaches whoever is on call, the problem is fixed, and you get a plain explanation of what happened and what changed.
What decides it
- Hours and response
- Which systems need someone at 3 a.m. and which can wait for the morning. Paying for 24/7 on systems that can wait is money better spent elsewhere.
- Who has access
- Named people, with their own accounts and a record of what they did. Shared admin passwords are the first thing to go.
- What you hear from us
- A short report of what changed and what was fixed, and an explanation after every incident, written for the people who pay for it, not only for engineers.
- Leaving
- Everything is defined in code and documented, so you can take it back, or hand it to someone else, at any time.
Proof
We operated a client's production search clusters after building them.
Talk to the person who builds it
Tell us what is slow, stuck, or held together by a spreadsheet. We will tell you what we think in one call, before any proposal.
DanielCo-Founder