Products
Two kinds of software come out of this company. Client projects, which we build to a brief and hand over, and our own products, which we build, run, and answer the phone for. This page lists the second kind.
Why we run products of our own
Running a product teaches what a project cannot. We carry the on-call phone for Pyak, so we find out what an unclear error message costs at two in the morning, what a schema migration does to a live tenant, and how much monitoring you need in place before an incident rather than after it. Those answers go into client work the following week.
It keeps our estimates honest
When we quote a SaaS platform, we are quoting work we have already paid for out of our own budget: billing, tenant isolation, rate limits, audit logs, and the admin panel every product turns out to need and nobody asks for in the first meeting. We know what those parts take because we built them for ourselves first.
Built on the stack we recommend
Pyak runs on Python and FastAPI behind a Next.js interface, with PostgreSQL for state and containers on managed cloud infrastructure. There is no separate internal toolkit: what we run for ourselves is what we build for clients, which is why we can tell you what a given choice costs to operate two years in.