service / 06 cloud & devops

Infrastructure
that doesn't page you.

Cloud and DevOps work for us means picking the cheapest stack that still meets your uptime requirement, automating the rollout so deploys are boring, and instrumenting enough observability that a human gets paged when something is actually on fire — not when a healthcheck twitched. We work on Hetzner, DigitalOcean, AWS and bare metal. We don't have a preferred vendor — we have a preferred budget.

— ch. 01 / what you get

What you get

GitHub Actions CI/CD

Lint, type-check, test, build, deploy — all in one pipeline. Preview environments per pull request. Production deploys on merge to main, behind a manual approval gate if you want one.

Zero-downtime rolling deploys

Docker images built in CI, pushed to a private registry, rolled out behind nginx or Traefik with health-check gating. We've shipped 400+ production deploys without measurable downtime across our client base.

Observability that pages humans

Grafana + Prometheus or Datadog (whichever your budget tolerates). Dashboards for the four golden signals — latency, traffic, errors, saturation. Alerts routed to PagerDuty or Slack with on-call rotations defined upfront.

Backups tested by restore

Daily snapshots, off-site replication, and a weekly automated restore drill that actually mounts the backup and runs a smoke test. We've seen too many 'backed up' databases that turn out to be unrestorable.

Cost-aware infrastructure

We aim to spend the smallest amount of money that meets your SLA. Hetzner CX22 ($4/month) handles more than people realise. Largest client on our books pays $24/month for infrastructure across two production services.

— ch. 02 / our approach

Our approach

We pick infrastructure the way a careful builder picks materials: the cheapest one that meets the spec, and no fancier. A $4/month Hetzner VPS runs most Laravel apps on the planet just fine. AWS is the right answer when you genuinely need its services — not because the procurement team is more comfortable with a recognised name.

We containerise everything we ship. Not because Kubernetes is mandatory (it usually isn't), but because Docker means a developer's laptop, the staging VPS, and production all run the same artefact. That eliminates the entire class of 'works on my machine' bugs.

We default to a simple stack: GitHub Actions for CI, Docker Compose on a managed VPS for runtime, Cloudflare in front, S3-compatible object storage (Backblaze B2 or DigitalOcean Spaces) for assets and backups. Most clients never need to graduate from this. The ones that do, we migrate cleanly when the time comes.

— ch. 03 / pricing & timeline

Pricing & timeline

infra audit · 1 week · KES 50,000 · cost + reliability + security review
ci/cd setup · 1–2 weeks · KES 80,000+ · github actions + staging + prod
observability stack · 2–3 weeks · KES 150,000+ · grafana/prom + alerts
managed devops · ongoing · from KES 60,000/month · on-call + ops

Infrastructure provider invoices (Hetzner, AWS, Cloudflare) pass through at cost. We don't mark up hosting.

— ch. 04 / recent example

Recent example

HyipX + AviatorMode infrastructuretwo Laravel-based production services running on a single $24/month Hetzner VPS in Frankfurt with Cloudflare in front and Backblaze B2 for backups. Live since 2022.

Zero unplanned downtime in 18 months
p99 response < 280ms under normal load
Backup restore drill: 4m 12s to working DB on staging

Running production on a stack you don't fully understand?

A one-week audit. Honest read on your reliability, cost, and the things keeping you up at night.