A Pacific-Northwest engineering practice for Rails + Postgres SaaS teams. We ship features, fix the hard production problems, and own the parts of the stack the rest of the team would rather not — quietly, on schedule, billed corp-to-corp.
One of two backend engineers on a multi-tenant SaaS that grew from $4M to $13M ARR. Six years owning Rails, Postgres, AWS, and the production problems that don't fit on a Jira ticket.
Pick the shape that matches the problem. Each one is built around the way Rails / AWS work actually breaks down — not generic "consulting hours."
A drop-in seat on your Rails team. We pick up tickets, ship features, review PRs, and carry pager weight — same as a full-time senior, just on a contract.
Slow queries, noisy-neighbor problems, a Postgres that's outgrown itself, an S3 bill that's outgrown the company. We diagnose, then fix.
A real REST/GraphQL API for your customers, a third-party data import that has to actually work, an OAuth/SSO story that holds up to security review.
Every engagement is led by the same senior engineer who answers the first email. You get real PRs, written-down decisions, and a clean exit when the work is done.
We'd rather find out fast whether the work is a fit. Send a description of the codebase and the problem; you get an honest read and a quote within 24 hours.
First week is on a no-strings rolling contract. Either side can walk away with no penalty. Most engagements that go past week one run 6+ months.
Real PRs in Git. Decisions written down. Two recurring sync meetings per week max. We work on PT but overlap is flexible.
Levelbrook LLC contracts C2C. MSA, SOW, mutual NDA, and COI (GL + Professional Liability, $1M / $1M) ready on day one. Vendor-management-system onboarding included.
War stories and architectural decisions from the kind of work we actually do — Rails & Postgres at scale, AWS bills that grew teeth, AI tooling that earns its keep, integrations with software that predates HTTPS.
When aggressive denormalization is the right answer — and the count-on-every-page-load pattern that ate a database.
A production server-driven UI across iOS, Android, React, and React Native — and the four traps that almost killed it.
Cutting an S3 line item ~60% without breaking a single user workflow — by treating access patterns, not age, as the unit of work.
Recruiters and staffing partners welcome. Direct clients welcome. End-clients welcome. We respond to every brief inside one business day.