When you need it
Your platform is in production, but nobody owns it day to day. Patches wait, alerts land in a shared inbox, nobody has tested a restore and small changes queue behind product work.
What sets the quote
- Sized by the workloads, resources and environments we look after, counted in a free sizing step with a read-only inventory query (AWS Resource Explorer, Azure Resource Graph or Google Cloud Asset Inventory).
- Three plans follow the size and shape of that estate: Starter, Growth and Scale (see the table below).
- Change hours each month are 4 in Starter, 12 in Growth and 24 in Scale.
- Larger estates, or platforms across several clouds, are quoted after sizing.
What changes
- Alerts reach engineers who respond in business hours: P1 within 1 hour, P2 within 4 hours and P3 the next business day.
- Patches go in every month, and backups are proven by restore checks, not assumed.
- Small changes arrive as reviewed pull requests instead of waiting behind product work.
- Each month you see what was done, what is at risk and what comes next.
What you get
- Monitoring and alerting for the workloads and platforms in scope
- Monthly patching of operating systems, node images, runtimes and platform components
- Backup and restore checks
- 4, 12 or 24 change hours a month by plan, delivered as reviewed pull requests
- Runbooks for the systems in scope, kept up to date
- A monthly report on work done, incidents, open risks and change hours used
- In Growth and Scale, a quarterly security and cost review and a monthly review call
- In Scale, a quarterly architecture review and ongoing cost management
What each plan includes
| Plan | Starter | Growth | Scale |
|---|---|---|---|
| Typical estate | One production environment and a few workloads | Several environments and one container or Kubernetes platform | Several platforms, regions or clusters |
| Change hours per month | 4 | 12 | 24 |
| Reviews | Monthly report | Adds a quarterly security and cost review and a monthly review call | Adds a quarterly architecture review and cost management |
Business hours are Monday to Friday, 08:00–17:00 Finnish time, excluding Finnish public holidays.
Not included
- 24/7 cover (available as the 24/7 critical cover add-on)
- 24/7 security monitoring (SOC or MDR)
- Application code changes (see App Care)
- New builds, and changes larger than your change hours (quoted separately)
What we need from you
- Read-only access for daily work: ReadOnlyAccess on AWS, Reader and Log Analytics Reader on Azure, or Viewer on Google Cloud.
- Write access to your infrastructure repositories and pipelines, so every change goes through a pull request.
- A break-glass admin role for incidents, with every use logged.
- Alerts routed to us, access to your ticket system, and a named contact who approves changes and agrees priorities each month.
How it works
Free 30-minute call, then the free sizing step and a written fixed quote.
Onboarding over 2–4 weeks: access, monitoring and alert routing, runbooks and a first restore check.
Monthly patching, backup checks and changes from your change hours, all in business hours.
Monthly report and reviews by plan, with a minimum term of 3 months and then one month's notice.
24/7 critical cover can be added for the systems that need it.
At a glance
- Duration
- Monthly
- Price
- Fixed quote after a free 30-minute call
- Delivered by
- Vetted specialists, with our lead architect accountable
Related services
App Care
Business-hours care for your live web and mobile apps: security and dependency updates, uptime and error monitoring, backup checks and a monthly allowance of hours for fixes and small changes.
24/7 critical cover
An add-on to Platform Care or App Care: an engineer acknowledges a P1 incident within 30 minutes, 24/7/365, with cover starting after 4–6 weeks of onboarding.