In service
Representative deployment profiles — the shapes we run, anonymised. No named clients, no invented testimonials: just the spec sheet for what's actually live and how each one keeps shipping.
Every card, the same three beats
Each entry in the register shows the same loop, named up front, so the spec sheet below reads at a glance.
- 01Build
CustomLabs
The first version, designed and built by the consultancy that also runs it.
- 02Iterate
CodeHerder
A concrete briefed change: an agent opens a pull request, and it ships through the same pipeline.
- 03Run
CustomHosted
What keeps it live day to day — compute, edge, backups, patching.
Build → Iterate → Run
Five shapes, one loop
A static site, a dedicated API with a database, a full-stack SaaS, a worker fleet nobody watches, and a migrated legacy app — not just the two standard boxes.
- DEP-01MediaStatic
Independent publisher's digital edition
Static build, headless content, no server to patch
- TTFB32 ms
- Uptime99.99%
- Live in1 day
- Build
- CustomLabs rebuilt the flagship site as a static build, pulling content from a headless CMS instead of a server that had to be kept patched.
- Iterate
- Briefed: swap the homepage hero for a seasonal campaign. CodeHerder's agent opened a PR against the templates, and it was live the same day.
- Run
- CustomHosted serves it from the global edge network with a rebuild on every content change and TLS renewed automatically.
OutcomeShips new campaign pages most weeks with no developer on payroll.
- DEP-02LogisticsDedicated
Regional logistics dashboard
API and operations dashboard on dedicated compute, with a managed database
- TTFB58 ms
- Uptime99.98%
- Iterations shipped41
- Build
- CustomLabs built the dispatch API and the operations dashboard that sits on top of it.
- Iterate
- Briefed: add a driver-idle-time report to the dashboard. The agent wrote the query and the chart, opened a PR, and it shipped within the day.
- Run
- CustomHosted runs the API and database on dedicated compute behind a hardened proxy, with nightly backups and security patching.
Outcome41 agent-shipped changes since launch, all human-reviewed, none needing an on-call page.
- DEP-03FintechCustom
Series-A analytics SaaS
Full-stack app, background workers, a queue, and a managed database
- Uptime99.97%
- Iterations shipped63
- Live in9 days
- Build
- CustomLabs designed and built the product end to end ahead of a funding-round demo.
- Iterate
- Briefed: add usage-based billing tiers. One PR touched the pricing model, the worker that meters usage, and the billing screen together.
- Run
- CustomHosted runs the app, the workers, the queue, and the database as one fixed-rate stack, monitored and backed up nightly.
OutcomeShips feature work most weeks with a two-person team and no dedicated operations hire.
- DEP-04RetailCustom
National retailer's overnight pricing engine
Scheduled jobs and queue workers, no user-facing frontend
- Uptime99.99%
- Jobs / night1.2M
- Iterations shipped27
- Build
- CustomLabs built the pricing-recalculation pipeline that runs across the catalogue after close each night.
- Iterate
- Briefed: add a per-region discount override ahead of a seasonal sale. The agent shipped the rule change and a dry-run report the same afternoon.
- Run
- CustomHosted keeps the worker fleet and queue online with auto-restart on failure and an alert if a nightly run does not complete.
OutcomeNo missed nightly run since going live, and changes ship without waking anyone.
- DEP-05Public sectorDedicated
Public records portal, migrated off end-of-life hosting
Legacy app and database, moved as one unit, framework unchanged
- Downtime< 4 min
- Uptime since99.99%
- Live in6 days
- Build
- Originally built years earlier by an in-house team that had since moved on, on hosting nobody was maintaining.
- Iterate
- Briefed: patch a dependency flagged in a routine security scan. CodeHerder’s agent opened the upgrade PR and ran the test suite before anyone had to touch the code by hand.
- Run
- CustomHosted moved the app and its database off the end-of-life host with a rehearsed cutover, and now runs both on dedicated compute with nightly backups.
OutcomeFirst code change in over a year, shipped without hiring anyone.
Keep exploring
- Platform
How the edge network, storage, and dedicated compute fit together.
- The Loop
The Build → Iterate → Run loop this register shows in practice, told in full.
- Migrations
Already running somewhere else? Point us at it and we do the lift.
- Pricing
The full rate card — flat, predictable, and posted in the open.
Have a shape that isn't in the register?
Describe the workload and we'll design and quote it flat — the register only shows five of the shapes we run.