We build it. We run it. We get paged for it.
Stalance writes, ships and operates web platforms, e-commerce systems and data pipelines. The engineers who scope your project write its code, because that is how we run our own: 20+ storefronts in 8 countries, on a platform we built.
// no slideware. you get diffs, dashboards and a written scope.
Services
Web platforms
Multi-tenant, multi-domain, multi-language. One codebase, many brands, no copy-paste forks.
E-commerce engineering
Catalogues, variants, search and filters that hold up at millions of listings.
Data pipelines
Feeds, scrapers, classification. Pipelines that tell you when they are lying.
Cloud and operations
Deploys without 5xx. We watch it and get paged when it breaks.
Things we believe
Five rules we work by. They apply to our own systems first.
- A check that cannot fail is not a check.Every gate we ship is proven red on a planted defect before we trust its green.
- “No errors” is not “healthy”.We watch our systems and get paged when they break. A quiet dashboard is not proof that it is fine.
- Measure before you claim.The numbers on this site are rounded from production.
- Boring technology, on purpose.A proven open-source stack, a small surface area, and runbooks for the parts that bite.
- Whoever wrote it gets the page.No handover to a support desk that has never read the code.
Our own production, in numbers
- Brand lines
- 7
- Storefronts
- 20+
- Countries
- 8
- Merchant programmes
- 50+
- Product listings
- 4,000,000+
// measured on production, 22 Oct 2026.
How an engagement runs
01 readWe read before we quoteRepo, infrastructure, incident history. You get a written read-out first.02 scopeA written scopeWhat we will build, what we will not, and how we will both know it works.03 buildRiskiest part firstSmall reviewed changes, deployed behind checks you can read.04 runRun it or hand it overAgreed in the written scope: we operate it, or hand over with runbooks your team will actually use.Technical review is available on request.
Tell us what is broken
One paragraph is enough: what the system does, where it hurts, and what “fixed” would look like. An engineer reads it, not a ticket bot.
Received. An engineer has it now.
Not a ticket queue: one of the people who would do the work reads your message and writes back to personally. No auto-reply is coming; this is your confirmation.
Write to us
The form is not available right now. Email [email protected]: one paragraph is enough, and an engineer reads it.