Foundry embeds senior engineers inside your team to design, build and harden the systems your product runs on. We carry the pager for them from week two, and we leave on a date written into the first contract — with your people running it.
Carrying the pager for payments networks, health records, freight and public services — never more than eight clients at once.
What we do
Every engagement draws on the same six principals — engineers who have run these systems in production at three in the morning, not just drawn them on a whiteboard at three in the afternoon.
Platform engineering
Pipelines, environments and service templates your teams choose to use. Canaries promote themselves; rollbacks take one command and under two minutes.
2 days → 40 minmedian lead time, Halvard Pay
Reliability
Data infrastructure
At four of our last six clients, over half the scheduled jobs fed tables nothing had read in ninety days.
On call from week two
We carry primary while we build. Your engineers shadow, then swap, then hold it alone. By week eleven the pager is yours and we are the second line.
Security
14 → 0standing admin credentials, Pellucid Health
Handovers
31of 33
landed on the date in the first contract. The two that moved slipped nine and sixteen days — both agreed in writing a month ahead.
The assessment
assessments end with us recommending you change nothing — or hire a different firm.
What you own afterwards
Every engagement ends with the system on one sheet: what runs, what it talks to, and who owns each box. This is Halvard Pay's, with the dates each part moved to their team.
Engagements
Dual-writing throughout, with a reconciliation job that would halt the cutover on a single cent of drift. It never fired in anger.
Scanners buffered writes and the database assumed they had not. We event-sourced the stock position and made the warehouse the source of truth.
Eighteen months moving a citizen-facing service off a system that could not be turned off, with the router as the only place either side could be wrong.
From the people who took the pager back
−85%pages in the first quarter after handover
They left our team stronger than they found it. A year later we still run the platform they built, and we have never once needed to call them about it.
The assessment said our rewrite was the wrong project. It cost us six weeks and saved us a year.
Their principal took primary on-call in week two and wrote every runbook as if she would not be there to explain it. By March she was not, and we did not notice.
0reconciliation breaks across the cutover
We switched the old ledger off on a Tuesday afternoon. Finance found out from the newsletter.
They wrote down the thing our own team had been trying to say for two years, and then they put their name on it.
Our auditor asked who could reach production data. For the first time the answer fitted on one page, and it was true.
No framework of theirs left behind. Just boring software we already knew, set up better than we would have.
Start with the assessment
Thirty minutes with a principal — not a salesperson — to work out whether we are the right shape of help. If we are not, we will say so and suggest who is.
Next assessment starts
11 JanTwo engineers · 4 weeks1 left 1 FebTwo engineers · 6 weeks2 left 1 MarTwo engineers · 4 weeksTaken