Multi-tenant architecture
Tenant separation designed in, not retrofitted.
SaaS
SaaS products with single sign-on and roles from release one
Multi-tenant platforms with role-based access, single sign-on and reporting from the first release. We build our own SaaS too.
31 Oct 2025End of the ISO 27001:2013 transition
1Credit a Sales OS run costs
40 minAbout that long per account before Sales OS
40+Developers on staff
What this is
Buyers ask for the security evidence before the demo
Enterprise customers ask for single sign-on, role-based access and a current security certificate before they sign. A SaaS product that adds those late spends its roadmap catching up.
Where we have proof
a self-hosted, multi-tenant IoT platform, and Sales OS, a product we built and run ourselves
Where we have not yet
We have no published SaaS case. We say so on the first call and show the closest work.
Services
What we build for SaaS teams
Single sign-on and roles
The features enterprise buyers ask for first.
Usage and billing reporting
Metering that matches the invoice.
APIs and integrations
Webhooks and connectors customers use.
Security evidence
The controls, logs and records an assessor asks to see.
AI features
Grounded in your data, with the evidence next to the answer.
Rules
What the ISO 27001 change means for a certificate
This comes from BSI, a certification body.
Transition ended 31 October 2025The transition to ISO/IEC 27001:2022 ended on 31 October 2025, and certificates issued to the 2013 version expired. Source: BSI.
Case study
Two platforms we built, one we run
Industrial IoT
IoT Core Engine
The client wanted off third-party IoT SaaS without losing the enterprise features their own customers expected. We built a self-hosted, white-labelled platform on an open-source base, with role-based access, single sign-on and reporting built in.
Self-hostedOn-premise, private cloud or hybrid
Internal product, Dev Station
Sales OS
Our sales team lost about forty minutes an account working out whether a prospect owns its inspection equipment. We built a product that takes a domain and returns a graded brief, from A+ down to D.
40 minPer account that it replaced
Who we build for
The teams who call us
SaaS founders
Teams that need a first version with enterprise features in it.
Product companies moving off a vendor
Where the licence cost has outgrown the value.
Scale-ups selling to enterprises
Teams losing deals to security questionnaires.
Software vendors adding AI
Companies putting grounded AI features inside an existing product.
Related reading: business software, telecom software and game software.
FAQs
What buyers ask first
Do you have a SaaS case?
Not yet published. We say so on the first call and show the closest work, which is a self-hosted multi-tenant platform, and our own Sales OS product.
Do you give advice on ISO 27001?
No. That advice comes from your security lead and your certification body. We build the controls and evidence they specify.
Can you take over a product another team built?
Yes. The first step is documenting what exists so you own it again. Rewriting waits until that is done.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Send us your roadmap
Thirty minutes with the engineers on what your product needs next and what enterprise buyers are asking for.