Products and source
Resources
Products we run, our public source and the blog.
Products
Products we run
Two of our own products, with write-ups of how we built them.
ButlerCRM
Read the case studyA real-time CRM on Elixir/Phoenix, so a whole team sees the same customer live.
Business systemsPolyHuntr
Read the case studyTurns a fast prediction market into rankings and plain-language analysis.
Finance
Reading
More to read
Technology stack
ReadThe models, agent tooling and cloud patterns we build with.
StackPublic source code
Public source for portfolio systems including JarvisNano, Verrow and Kintunnel.
Source GitHubBlog
Articles from the studio.
Blog Visit the blog
How we work
How a change reaches production
The same five gates for our own products and for yours. Nothing reaches your customers on the strength of a demo.
- 01 · Isolate
Its own branch and workspace
Every change starts in a separate copy of the code, so work in progress never touches what is live.
git worktree add .worktrees/your-change - 02 · Build
Engineers with AI agents
Agents write and test code beside us. They hold no passwords: every call they make goes through our gateway, which checks it and logs it.
agent → gateway → policy · audit · call - 03 · Prove
Evidence, then review
Tests, before-and-after screenshots of the running app, then independent reviewers. It does not move on until no serious finding is left.
review: 0 high · 0 medium → pass - 04 · Ship
Deployed and checked live
The pipeline builds and deploys. Then we check the running service itself, not just a green build.
replicas 1/1 · image sha matches · health 200 - 05 · Watch
Checked every night
Each integration we run is tested against its provider every night, so a changed API is caught before your team notices.
nightly: each integration vs its provider