Platform
What gets built, and what it inherits.
One page per promise. Everything here applies to every application we run — you do not ask for it, and you do not pay extra for it.
What we build
A sentence goes in. Working software comes out.
Applications, AI agents and the connections between them — described in plain English, delivered running on the internet with real logins and real data.
What we build- Delivery A live web application on your own domain, with TLS
- Accounts Email + password, magic link, Google and Microsoft SSO
- Permissions Roles, per-record access rules, admin view
- Data Managed relational database, daily backups, full export on request
- Environments Production and staging, with separate data
- Email Transactional sending on an authenticated domain (SPF, DKIM, DMARC)
Help centre
Your customers find out what you built.
You ship a feature and nobody uses it, because nobody knew it existed. The documentation, the announcement and the answer to the support question all come from one place — generated from the application itself.
Help centre- Help site Public site on your own subdomain, with TLS and your branding
- Content source Generated from the application; you review before anything publishes
- Search Instant full-text search across every article
- Discoverability Sitemaps and structured data, so search engines and AI assistants can cite it
- Release notes Per release, categorised as new / improved / fixed, permanently linkable
- In-app A what's-new panel showing changes since that user last looked
Enterprise-grade, from the first line
The five guarantees
Every application inherits all five. An application without them is not one we would put our name on — which is why none of them is an upgrade.
Secure
Locked down by default
The defaults are the secure ones. There is no hardening step you have to remember to ask for.
ReadCompliant
Evidence before it is asked for
The evidence exists before you need it, because assembling it afterwards is how deals slip a quarter.
ReadReliable
Up, and someone is watching
When your application breaks at two in the morning, you are not the monitoring system.
ReadScalable
Ten users or ten thousand
The day you get written about is the day the application has to hold. It is built for that day from the start.
ReadEfficient
You pay for what you use
A cost that tracks your actual usage, and no fixed headcount underneath it.
Read