Loading…
Custom internal tools that live in your codebase, share your auth, and query your database directly — no per-editor licence, no vendor-side outage that takes ops offline.
What you get
Custom data views built around your data model, not a generic table generator.
Day-to-day workflows for support, ops and finance — designed for them, not the engineer who built it.
Impersonation, refunds, account fixes — with a confirmation step and an audit trail.
Field-level permissions enforced at the database via row-level security, not just hidden in the UI.
How it runs
The same stages run every engagement. The service decides the scale, not the method.
01Blueprint
The screens ops actually needs, the actions that currently require a database console. Written down.
02Blueprint
Role matrix and access boundary named on the page. You sign off before a line is written.
03Forge
Weekly preview URL — ops can click around and flag what's missing before launch.
04Forge
Deployed to your cloud, roles configured, handover doc names every permission and every cron.
Pricing
Ops console
A focused ops console with one role and a clean audit trail.
From £18,000
Multi-role support surface
Multi-role, customer search, refunds, impersonation — the full support surface.
Example: £35,000
Platform
Workflow tools, custom views, a year of headroom for the next ops hire.
Example: £60,000
Proof in production
AI Automation · Case study
Categorisation, summarisation, and triage automated across an operations team's daily workload. Graceful degradation when the model is…
AI Platform · Case study
A documentation platform that reads code and emits prose a non-engineer can act on. Used internally on every Canarlo build.
how-to13 min
When a small business actually needs a custom internal tool instead of a spreadsheet or email chain — the…
Read guidehow-to11 min
Should you fix a messy process first, or automate it as-is? The honest answer, a 5-minute consistency audit,…
Read guideQuestions
Retool is right until the seat fees eclipse the value, or a customer asks where their data lives. Custom internal tools live in your codebase, share your auth, query your database directly. No per-editor licence.
Yes. New table, new column, new dashboard, new bulk action — added in a normal pull request. The pattern is the same one every screen already uses, so a new view is hours, not a Retool snowflake.
Non-tech staff first. Support, ops, finance, customer success. Search that handles typos, bulk actions with a confirmation, an audit log so a mistake can be traced.
Role-based, per-collection, enforced at the database via row-level security. Two-factor on every admin login. The boundary holds even if the UI has a bug.
You. Your repo, your Supabase, your domain, your keys. No per-seat licence, no vendor lock-in, no annual renewal. Sack us tomorrow and ops keeps running.
Talk to us
Scoped and priced before anything is built.