API design
We describe each API in OpenAPI before we build it and version it, so the apps that depend on it keep working while it changes.
Backend services and APIs that are easy to change, tested in CI and observable in production.
Hover over or tap a box to see what it does.
We describe each API in OpenAPI before we build it and version it, so the apps that depend on it keep working while it changes.
We start with a modular monolith that has clear internal boundaries. A part becomes its own service only when that pays off in deployment, scaling or ownership.
Sign-in, sessions or tokens, and role-based access that matches who does what in your organization.
Work that shouldn’t hold up a request, such as imports, emails and long calculations, runs as background jobs with retries.
We profile before we optimize, then fix the queries, payloads and code paths that actually cost time.
A test strategy that matches the risk, running in CI, plus logs, metrics and traces so problems show up before your users report them.
We look at the product, the existing code if there is any, the data and the risks, then agree on scope, milestones and what success looks like. Taking over an existing backend usually starts with a short audit to find the fixes with the most impact.
We design and implement in clear milestones. Tests, CI and observability are part of the work from day one, not a phase at the end.
We ship to production with monitoring, documentation and runbooks. Support afterwards can be ad-hoc work or a monthly retainer, depending on your needs.
Thiago Benkendorf, the senior software architect and engineer behind Nithron, does every engagement hands-on. On bigger projects he can coordinate other engineers, as he did with a six-person contractor team on a manufacturing platform rebuild, and he stays your single point of contact.
Yes. We regularly take over and improve existing systems. We begin with a short audit, fix what lowers risk first and then improve the parts that slow the team down, without a big-bang rewrite.
No. Most products can start as a modular monolith, which keeps complexity low and leaves a clean path to split out services later if they are needed.
Usually the one your team already knows and can maintain. We work in Java, C#, TypeScript, Go and Python, and we only suggest a change when there is a clear reason for it.
That is what the handover is for. You keep the OpenAPI specification, the decision records, the runbooks and the tests in CI, and we can stay on for support if you want.
Welcome back! If you booked a call, Proton is emailing you the confirmation with all the details. We look forward to talking.