//systems engineering · Estonia (EU)
We architect scalable distributed backends, robust APIs, and low-latency cloud infrastructure for enterprise platforms.
//services
Six areas we take on. Every engagement is scoped in writing, priced against named deliverables, and handed over with documentation your team can actually operate.
module_01 · backend
Distributed backends and domain-driven services designed to stay correct under load and legible after two years of change.
module_02 · backend
REST, gRPC and GraphQL interfaces with versioning, contract tests and integration adapters for systems that were never meant to talk to each other.
module_03 · cloud
Reproducible infrastructure as code, CI/CD that engineers trust, and observability that answers questions instead of raising them.
module_04 · audit
Independent review of an existing system: where it will break, what it will cost to fix, and in which order.
module_05 · backend
Profiling, query and index work, caching strategy and load testing against a measured target rather than a guess.
module_06 · consulting
Senior technical judgement on retainer: hiring, vendor selection, roadmap sequencing and investor-grade due diligence.
//estimator
Four numbers you already know — peak load, data volume, read/write mix, availability target — turned into a recommended topology, an indicative infrastructure cost and an engagement band. Deterministic model, published assumptions, no email required to see the result.
error budget: 43 min downtime / month
ha-pair
HA pair behind a load balancer
Two or more stateless nodes, a read replica and a cache tier. Survives a single node loss.
indicative infrastructure
€290 /month
range €230 – €390
indicative engagement
23–43 eng. days
€18,000 – €33,500 @ €780/day
Indicative planning figures generated from public list prices and our own delivery history. Not an offer; a written proposal follows the technical consultation.
//benchmarks
Figures from delivered engagements. Each one states the tested workload and method, with retained baseline and result evidence. An unqualified “10x faster” is not an engineering claim.
API latency
Query plan and cache behaviour
Sustained throughput
Connection and read-path efficiency
Infrastructure cost
Resource and storage efficiency
//principles
You inherit every choice we make. These are the four that shape the rest.
01
Every performance engagement starts with a reproducible load test against the current system. A profile beats an opinion, and it turns "it feels slow" into a number we can hold ourselves to.
02
PostgreSQL until it genuinely will not do. A queue before a service mesh. New technology has to earn its place in a written trade-off, because you inherit the operational cost of every clever decision we make.
03
Timeouts, retries with backoff, idempotency keys, circuit breakers and dead-letter handling are designed in at the start. Retrofitting them into a system that assumed the network always works is most of what a rescue project costs.
04
Repositories, pipelines and infrastructure state live in your accounts from day one. Architecture decision records explain why each structural choice was made, so the next engineer does not have to guess.
//faq
0xProgramming OÜ works with businesses only (B2B): product companies, agencies subcontracting engineering work, and in-house technology teams that need senior backend or platform capacity. We do not take consumer work and we do not sell licences or subscriptions — every engagement is a written service agreement for named work.
Either a fixed price for a defined scope, or a monthly retainer measured in engineering days. Our indicative day rate is €780. The architecture estimator on this site gives a planning range from your load and data figures; a binding written proposal follows the first technical consultation, which is free.
No. It is a deterministic first-pass sizing model that turns peak requests per second, data volume, read/write mix and availability target into a topology, an indicative infrastructure cost and an engagement band. It uses public list prices and our own delivery history. It is planning input for the first conversation, not an offer.
Both, and most of our work is on systems that already carry production traffic. Audits, performance rescue and incremental migration of legacy platforms are a core part of what we do. We do not require a rewrite as a precondition — in most cases we advise against one.
0xProgramming OÜ is an Estonian private limited company, registry code 16634675, EU VAT EE102570771, registered on 19.12.2022 at Pikk tn 14-2, 44307 Rakvere, Lääne-Viru maakond, Estonia. Contracts are governed by Estonian law under EU jurisdiction and the entry is publicly verifiable in the Estonian Business Register.
For website enquiries we are the data controller and process only what the form collects, under GDPR; this site runs on a single server in the United States, which our Privacy Policy states along with the transfer safeguard we rely on. When engaged on your systems we act as a data processor under a signed Data Processing Agreement, working on infrastructure you control and in the regions you specify, with least-privilege access issued for the engagement and revoked at handover. We do not copy production personal data into our own environments, and we do not sell or share data with advertising networks.
Yes. We sign a mutual NDA before any technical detail, code or infrastructure access is exchanged. Send it with your first message, or ask us for ours.
You keep the repositories, the infrastructure state and the documentation, all in your own accounts. We offer an optional support retainer, but nothing in the delivery is designed to require it — handover includes a working session with your team and runbooks written for someone who was not there.
We do not currently publish numerical benchmark claims because the underlying reports and raw results are not publicly available. This page therefore describes representative engineering outcomes without figures. Any future numerical claim will be published only with destination-accessible evidence covering the workload, environment, measurement method and results.
The first technical consultation is free and runs about 45 minutes. Bring your architecture, your load figures or your incident history — you will leave with a written opinion either way, whether or not we end up working together.
registered in the Estonian Business Register
NDA on request. Contracts under Estonian law, invoiced in EUR with EU VAT reverse charge where applicable.