Loading…
Client names are anonymised where we’re asked to. What isn’t anonymised is the architecture, the decisions and the outcome — the parts that tell you whether we can build yours.
Each engagement is written as: what was actually wrong, the decisive architectural choice, and what changed afterwards. No vanity metrics.
A product-led business needed a SaaS that could support multiple frontends, partner integrations, and future expansion without repeatedly reworking core logic.
A working platform that had outgrown its original architecture. Auth, data, and observability rebuilt without a service interruption — the customers never noticed.
Categorisation, summarisation, and triage automated across an operations team's daily workload. Graceful degradation when the model is unavailable — never hard-fail.
A documentation platform that reads code and emits prose a non-engineer can act on. Used internally on every Canarlo build.
A multi-merchant comparison engine indexed for relevance, not exact match. Built to survive a 5pm spike on launch day, and it did.
Starts with a Blueprint, so the build has no discovery in it.
Plain TypeScript, plain Postgres, plain Next.js — on your accounts.
Code, docs and keys in your name. No lock-in, ever.
Forge keeps shipping — fortnightly, cancel anytime.
Tell us the shape of the problem. If one of these engagements rhymes with yours, we’ll say what we’d do differently second time round.