Engagements typically run three to twelve months, with one or two of us embedded with your team. We don't do hourly retainers or long-term staffing.
From a single struggling service to a full platform rewrite, this is the work we do most. Recent engagements have included rebuilding a payments reconciliation pipeline that was losing transactions in edge cases, splitting a Rails monolith into three well-scoped Go services, and a six-month overhaul of an order management backend that quadrupled its throughput.
We're language-agnostic in principle, but we ship faster in Go and Elixir than we do in Java. Ask us about that.
PostgreSQL is the foundation of most of what we build. We've designed schemas for everything from a national identity lookup service to a B2B invoicing platform with multi-currency consolidation. We're comfortable with logical replication, partitioning, and the various dark arts of high-cardinality time-series in Postgres.
For streaming workloads we lean toward NATS JetStream for smaller scales and Kafka where the team already runs it. Mostly we'll tell you what you actually need rather than what's fashionable.
Observability that doesn't bury your engineers in dashboards. On-call rotations that don't burn people out. Incident reviews that improve the system rather than identifying scapegoats. The work is mostly about culture and operational maturity, with some infrastructure as a side effect.
We're partial to Prometheus, Grafana, and OpenTelemetry. We've used Kubernetes successfully and unsuccessfully. We'll be honest with you about which it would be in your case.
Two-week engagements for teams considering a larger investment in their platform. We'll look at your codebase, your data, your deployment pipeline, and your on-call history. You'll receive a written report with prioritised findings and concrete next steps. About a third of these turn into longer engagements.
Want to talk about a specific project? Get in touch →