Quarry runs Orrin without its code leaving its cloud. A database company with customers' data in its test fixtures needed sandboxes in its own AWS account, and passed security review in three weeks.
- 0
- lines of source code sent outside Quarry's account
- 3 weeks
- from the security questionnaire to the first run
- 1,240
- runs in the first quarter
Quarry
An analytics database, written in Go
- Based in
- Berlin
- Engineers
- 60
- Plan
- Enterprise
- Since
- April 2026
The requirement
Quarry builds a column-store database that its customers run on their own data. Its integration tests use anonymised extracts of that data, and its contracts say those extracts never leave Quarry's AWS account. Any agent that wanted to run the tests had to run there too.
“It tells you what it didn't check. My engineers trust it because it admits that.”
The review
Quarry's security team sent its standard review of 140 questions. Orrin's runner answered most of them by design: one outbound connection, one microVM per run, and model calls through Quarry's own Bedrock endpoint in Frankfurt.
The open questions were about the control plane, and were closed with the SOC 2 report and a call with Orrin's head of security. The first run was three weeks after the questionnaire arrived.
In production
Orrin now takes flaky tests and the query planner regressions that follow Go upgrades, the work Quarry's engineers called the tax on shipping. It ran 1,240 times in its first quarter, and Jonas Becker's team reviews its pull requests in the same queue as everyone else's.