Access enforced on the server
Sign up and sign in, organisations with members, and roles that decide who can do what. The boundary every multi-customer product needs, built first and tested first.
The part every product needs
Nobody enjoys rebuilding it, and nobody can afford to get it wrong.
Sign up and sign in.
Accounts with email login, password reset and invitations.
Organisations and members.
Customers work in teams, and members belong to an organisation.
Roles that decide.
Owner, member and viewer, or the roles your product needs.
How it works in three steps
Small, paid, provable. You own the repository and the data at every step.
One call to scope it
We map the roles and what each one is allowed to do.
Built and tested first
Access is the first thing we build and the first thing we test.
Run it, or take it
We host and maintain it, or hand over the repository and documentation.
What we hand over
Accounts, organisations and roles, as code you own.
Accounts
Sign up, sign in, password reset and invitations.
Teams
Organisations with members and owners.
Roles
Permissions per role, enforced on the server.
Sign in
Sign up, sign in, password reset and invitations.
Organisations
Organisations with members and owners.
Roles
Permissions per role, enforced on the server.
Tests
Access is the first thing we test.
Frequently asked questions
Access is scoped by organisation and enforced on the server, not in the browser. Every query is filtered by the customer it belongs to.
Yes. Owners invite members by email and choose their role.
Yes. Roles are built so adding or changing one later is a change, not a rebuild.
A fixed price, agreed after the scoping call. We quote one number for the first version rather than an hourly rate.
Yes. Organisations connect to plans and billing on your own Stripe, if you need it.
Get the foundation
right the first time
Tell us your plans and roles. In one call we will tell you what the first version takes and what it costs.