Technology
Built once. Built well. Used 22 ways.
Building 22 separate products would be impossible. So we built one shared core and assemble each product from modules on top of it.
Architecture
A shared core, and a thin layer that makes each product fit its trade.
Open a layer to see what it does. A new vertical product is mostly new modules in the middle; everything below is already there.
5Customer apps
What each business and its customers see: a booking page, a client portal, a tablet form.
4Integrations
Connections to the tools a trade already uses, added one by one as they are built.
3Vertical modules
The parts that make a product fit one trade: its records, its workflow, its paperwork.
2Shared core
What every product needs and nobody should build twice: accounts, billing, permissions, notifications, files.
1Infrastructure
Hosting, backups, monitoring and deployment, the same for every product.
The stack
We are documenting the stack for publication. In the meantime we walk through it live, with the code open, on every deep-dive.
Security
What is in place, and what is still in progress.
We list only what we can show evidence for. If something is not finished, it says so.
The published security notes are being prepared with evidence for each point. Ask us on a call and we will show you how data is protected, separated per customer and backed up.
Found a security problem? Tell us at info@apaone.co.uk. Our disclosure contact is also in security.txt.
Reliability
A public status page with uptime history will be linked here when it goes live.
What is automated, and what people still do
Billing, deployments and first-line support are built to run without manual work. People still talk to customers, review content and decide what gets built.
Spin-off readiness
Each product keeps its own data, its own billing records and its own module code. When a product grows up it can be separated from the studio and run as its own company.
For developers
API and integration notes are published here as each integration goes live. We only list integrations that exist.
Questions about data and security
Is my data safe?
We treat it as your data, not ours. You can export it at any time, and if you leave, it leaves with you. On our side, access is limited to the people who need it, and changes are logged. This page lists each security measure only once it is in place and can be shown, and we do not claim certifications we have not been awarded. If you need detail on a specific measure, ask us.
Where is my data hosted?
The hosting location is listed on this page. If it matters for your own contracts, ask us and we will confirm it in writing.
Can I get my data out?
Yes. You can export your data whenever you like, without asking us first, including before you cancel.
What happens to my data if a product is shut down?
You get notice before anything changes, and a full export of your data in a form you can use elsewhere.
Why does one studio build so many products?
Because they share one core. Accounts, permissions, billing, notifications and data export are built once and used by every product. Each product adds only the part that belongs to its trade.