Server and cloud administration. You run the business.
Maintenance with alerts. I respond during business hours, in the same time zone as Berlin (CET/CEST), and take critical incidents in the evening too, until 22:00. A monthly contract, no annual lock-in.
Or email jacob@codelevel.pl.
I reply within 1 business day.
What the plan covers
- Security updates in an agreed window, critical patches within a few working days.
- Backups outside the infrastructure provider, and regular restore tests with a report.
- Monitoring and alerts: uptime, disk, memory, certificates, and on the higher plans application and database metrics too.
- A pool of hours for changes, and a monthly report.
- Configuration in your repository (Terraform, Ansible), so nothing depends on me alone.
What I do not promise
I do not run a night on-call. Alerts fire at any hour, but I respond during business hours, and in the evening for critical incidents. If you need someone to react at three in the morning, this offer is not for you.
What I work with
- Servers: Linux (Ubuntu), dedicated servers and cloud at Hetzner and OVH.
- AWS: EC2, ECS, EKS, RDS and Aurora, CloudWatch.
- Containers: Kubernetes and k3s.
- Databases and cache: MySQL, MariaDB, PostgreSQL, Redis, Valkey.
- Web traffic: Nginx, Varnish.
- Configuration and monitoring: Terraform, Ansible, Prometheus, Grafana.
Plans and response times
Three plans, depending on the number of servers and environments. Hourly and emergency rates are on the pricing page.
Server
EUR 190 per month
one server or VPS: a shop, a website, an app
Scope and response times
- Hours included
- 1 h
- Monitoring and alerts
- uptime, disk, CPU and RAM, TLS certificates
- Security updates
- monthly; critical ones within 3 working days
- Backups
- daily, off-provider, kept 14 days
- Restore test
- quarterly, with a report
- Monthly report
- what I did, state of updates and backups
- Additional hours
- EUR 60/h
- Response: P1 on working days, 8:00–18:00
- within 2 h
- Response: P1 in the evening, 18:00–22:00
- outside the plan, emergency rate
- Response: P2
- next working day
- Response: P3
- 3 working days
Business
EUR 350 per month
up to three servers, or one small AWS environment
Scope and response times
- Hours included
- 4 h
- Monitoring and alerts
- the same plus application and database metrics, logs
- Security updates
- every 2 weeks; critical ones within 2 working days
- Backups
- daily, encrypted, kept 30 days
- Restore test
- monthly, with a report
- Monthly report
- plus infrastructure costs and trend
- Additional hours
- EUR 55/h
- Response: P1 on working days, 8:00–18:00
- within 1 h
- Response: P1 in the evening, 18:00–22:00
- working days, within 2 h
- Response: P2
- 4 working hours
- Response: P3
- 2 working days
Growth
EUR 690 per month
up to about eight servers, AWS with several environments, k3s or EKS
Scope and response times
- Hours included
- 10 h
- Monitoring and alerts
- the same plus dashboards and business alerts
- Security updates
- weekly or as released; critical ones within 1 working day
- Backups
- as in Business, plus point-in-time database restore
- Restore test
- monthly, plus a yearly failure drill
- Monthly report
- plus a quarterly cost review
- Additional hours
- EUR 55/h
- Response: P1 on working days, 8:00–18:00
- within 30 min
- Response: P1 in the evening, 18:00–22:00
- every day: working days within 1 h, weekends within 2 h
- Response: P2
- 2 working hours
- Response: P3
- 1 working day
- Monitoring and alerts run around the clock. I respond during business hours, in the same time zone as Berlin (CET/CEST), and take critical incidents in the evening too, until 22:00. I do not run a night on-call.
- A monthly contract with one month’s notice, no annual lock-in.
- The first month is onboarding: inventory, monitoring, backups and runbooks for incidents.
- The configuration lives in your repository (Terraform, Ansible). Unused hours roll over to the next month.
- Response times do not apply while I am on holiday, which I announce at least 30 days ahead, or off sick. For that time we agree together who takes the alerts, and the runbooks are in your repository.
P1: production is down, or there is an attack or a leak. P2: serious degradation with no workaround. P3: a change or a question.
Posts on this topic
Describe your situation in a few sentences
I will reply with questions, or straight away with a proposal and a price.
Or email jacob@codelevel.pl.
I reply within 1 business day.
From a case study: a SaaS platform I built on AWS has 99.99% availability over a year. See the case study