How it works
You delivered an application. It runs somewhere, so now you're also the hosting party, the monitoring service, and the number that gets called when it breaks. That work doesn't scale with your shop, and it's not why you chose this profession.
We take over the operations of what you built. Monitoring, backups, updates, and incidents become our work. You keep developing. Your client keeps one party that picks up when production quits at night.
Billing works however suits you. Sometimes we invoice your client directly, sometimes your shop sits in between and you bill it on. Both forms have been running for years.
Who does what
| What | Who |
|---|---|
| Features and further development | You |
| Releases: you decide what goes live | You |
| The client relationship | You, if you want to keep it |
| Platform and infrastructure | Us |
| Monitoring, backups, and updates | Us |
| Incidents, including at night | Us |
In practice since 2019
This is not a new program. Since 2019 we've been running production for a Dutch software house and for the clients that grew out of it: Spring Boot and Quarkus applications that simply need to stay up. Several of those clients later became direct customers of ours. The shop stayed the developer the whole time.
So an introduction doesn't cost you your client. It gets you a client who calls less about hosting and more about new features.
Where it runs
Dutch datacenters, our own hardware. The prices are right on the product pages: Pods from €100, Managed Servers from €250, Managed Clusters from €1500 per month. Partner setups start from those same list prices, so you can tell your client up front what it costs.
