Six senior engineers. A small list of partners.
Orynix started in 2021 because the founders wanted to do the work themselves, not staff it out. We've stayed small on purpose: a handful of partnerships at a time, almost all of them running for more than a year.
Four things we keep coming back to.
None of these are profound. They're the patterns we've watched pay off again and again across the projects we've shipped.
Six engineers, no offshore
Everyone here has a decade or more of production software behind them. There's no junior tier, no resourcing team, and no contractor pool we draft from when the project starts.
The interesting decisions are in the code
Schema choices, API contracts, the wording on an empty state: that's where products actually get shaped. We don't outsource those to a wireframe.
We're better at the long version
Most of our partnerships run multiple quarters. The first project teaches us your domain; the third is when we stop asking obvious questions and start saving you time.
Production incidents are part of the work
We've been on call long enough to make outages less dramatic, both for ourselves and for the teams we're embedded with. We write the runbook before we need it.
How we make day-to-day decisions.
- 01
Obvious code beats clever code
The line of code we're proudest of when we write it is usually the one we rewrite a year later. We default to whatever the next engineer would expect to find, and we earn complexity only when there's a measurable reason to.
- 02
Performance is part of the design
Latency, bundle size, and database response times shape what the product feels like to use. We pick budgets for them at the start of a project instead of treating them as cleanup work at the end.
- 03
Whoever builds it should be able to maintain it
Code gets read more often than it gets written. We optimize for the engineer who has to debug it on a Tuesday morning a year from now. Sometimes that engineer is us. Usually it's someone on your team.
- 04
Pick the boring infrastructure
Postgres, Redis, a job queue, and one of the major cloud providers. We spend our novelty budget on the parts of the product the user actually sees.
Two or three new partners a quarter.
Tell us a bit about the project. A 25-minute call is usually enough to figure out whether we're a fit. If we're not, we know people who probably are.