Reviewed changes
Every change goes through a pull request reviewed by a second engineer, with the reason recorded. Nothing reaches production from a laptop.
How we work
How we build, test and hand over
A ledger, a PMS integration, a data pipeline or an AI agent: the same rules apply to every system we build or take over. They are written down here so you can hold us to them.
This page is for your CTO, your security lead and your procurement team. If something they need isn't here, ask: we'll answer in writing.
Engineering standards
What every system we build or harden ships with
Tests where it hurts
Automated tests on the paths that touch money, permissions and personal data, run on every change in CI.
Infrastructure as code
Environments are reproducible from the repository. Staging mirrors production; secrets live in a vault, not in code.
Observability
Structured logs, metrics, error tracking and alerts that wake a person up when customers would notice.
Recoverability
Automated backups, and restores that are actually rehearsed. Recovery targets written down and agreed with you.
Handover
Architecture notes, runbooks and decision records, so your next engineer, or your next reviewer, can follow every choice.
How a project runs
From the first call to a system your team owns
- Week 0
Call
30 minutes with an engineer who would work on it, with a mutual NDA first if you want one. You get an honest yes or no.
- Weeks 1–2
First step
A fixed-price review or audit of what you have. You get the findings, a plan and a fixed quote for the build.
- Every week
Build in the open
The named team works in your repository and shows you working software every week, not status reports.
- Each milestone
Handover
Architecture notes, runbooks and an access review at every milestone. You pay per milestone, for work you have seen.
- 90 days
Warranty
We fix defects in our own work free of charge for 90 days after release. After that, monthly care is there if you want it.
Security & compliance
What procurement will ask us, answered
We are a small, senior company, not a certification factory. Here is exactly what we commit to.
- Full termsContracts, warranty, data and supplier terms for regulated clients are on Contracts & security.
- NDA before accessMutual NDA signed before we see code, data or documents.
- Least accessRead-only access for reviews. Named, individual accounts with two-factor authentication, removed when we finish.
- EU data handlingWorking copies and our own systems are hosted in the EU. A GDPR data processing agreement is available on request.
- Your code, your IPEverything we write for you is assigned to you in the contract, from the first commit. No lock-in, no proprietary framework you have to license.
- Supplier terms for regulated clientsWe accept the audit, incident-notification and exit clauses that DORA Art. 30 requires of ICT suppliers to EU financial entities.
- Incident noticeIf we suspect an incident affecting your systems or data, you hear from us without delay, in writing.
- CertificationsWe don't hold SOC 2 or ISO 27001 ourselves today. We work to the controls they require and help clients prepare for their own audits.
AI in our work
Faster tools. The same accountability
We use AI coding assistants every day. They make routine work faster, which is part of how we can hold fixed prices. They don't change who is responsible for the result.
- An engineer designs the change, reviews every line the tool produced and is accountable for it
- No client code or data goes to AI tools that train on it; we use enterprise terms with no training on inputs
- If your contract restricts AI tools, we work within that restriction
- We tell you where AI was used, so your own due diligence can answer the same question
Who you work with
Small senior teams, one accountable lead
Every engagement has a named lead engineer who stays from kick-off to handover. You meet them before you sign.
Owns the outcome
Your single point of contact. Runs the review or the build, and signs off each handover.
Money and identity flows
Ledgers, payments, custody, KYC and the integrations between them.
Cloud, access, recovery
Infrastructure as code, access control, backups, monitoring and incident response.
The people
Who you would work with
Alex
Founder, lead engineerAna
Product design and deliveryEvgeny
Senior engineerFree 30-minute call
Tell us what has to work, and by when
You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.