We keep your systems up and make your data useful.

A small senior consultancy for platform engineering, SRE, cloud and data. One team from the servers to the dashboards, so nothing gets lost between two vendors.

p99 latency, last 30 daysDay 18: a slow query hits checkout. Day 20: root cause fixed, not just restarted.

When a number on the dashboard looks wrong, the people who wrote the query also know the server it ran on.

The usual setup is one vendor for infrastructure and another for analytics. Each does good work in their own corner. Then the revenue chart drops for a week, and nobody can say if the business changed, the pipeline broke, or a deploy quietly dropped events.

We build and fix both ends. Platform work is done knowing which data has to survive it. Data work is done knowing how the systems underneath behave. Fewer hand-offs, fewer meetings, and one place to call when something looks off.

Ways to start

Short, fixed-scope engagements. You get a written report you keep, whether or not we work together afterwards.

2 weeks

Cloud cost review

We read your GCP or AWS bill line by line, map it to the services that cause it, and find what you pay for and don't use.

A ranked list of savings with effort and risk for each one.

2 weeks

Production readiness audit

Before a launch or after an incident: SLOs, alerting, on-call, failure modes, rollback and backups, checked against how your system really runs.

A fix list ordered by what would hurt you first.

2 weeks

Data health check

We trace your key numbers from the source to the dashboard and check where they drift, duplicate or go missing.

A map of your data, what to trust today, and what to fix.

3 weeks

KPI dashboard sprint

We agree on the handful of numbers that run your business, define them once, and build the dashboard on top.

One live dashboard everyone reads the same way.

Pricing depends on the size of your setup. Tell us about it and you get a fixed quote within a few days.

How an engagement runs

  1. A 30-minute call

    You tell us what hurts. We ask a lot of questions. By the end you know if we can help, and if not, who can. Free.

  2. A written proposal

    Scope, deliverables, timeline and price within a week. Fixed where it can be fixed.

  3. The work

    Two-week iterations with a written check-in. Code, configs and docs land in your repos and accounts, not on our laptops.

  4. Handover

    Your team runs what we built. If they can't, we are not done.

What we won't do

  • Sell you Kubernetes or a data lake you don't need. A managed service or a few VMs is often the right answer.
  • Build a machine-learning model where a good chart answers the question.
  • Write a 60-page strategy deck when a one-page plan will do.
  • Stay forever. The goal is to leave you better off without us.

Tell us what's broken.

A few sentences is enough. We reply within one working day and the first call is free.