Hosting · Cloud
We host it. You sign up and go.
Our shared, multi-tenant service with your own subdomain and per-seat pricing. The fastest way to start — with the same per-tenant isolation and data minimisation built in as the other tiers.
Architecture
A shared service, isolated per tenant.
We run a managed multi-tenant platform. Each school is its own tenant with a dedicated subdomain, and tenant data is logically isolated so no school can reach another’s. You operate nothing.
Why cloud
The shortest path to a first class.
Start in minutes
Nothing to provision or install. We create your tenant and subdomain; you make a class and share a code.
Per-tenant isolation
Each school’s classes, rosters, and patches are isolated from every other school’s on the shared platform.
Zero operations
Updates, scaling, monitoring, and backups are all ours. There is no infrastructure on your side at all.
Minimised by default
Students join with a code and a display name. No student email, no telemetry by default, no secondary use.
Per-seat pricing
Pay for the seats you use, billed by purchase order or invoice for education. Suspend a student to free a seat.
Upgrade when ready
Move to a dedicated instance or self-hosting later if your isolation or residency needs grow. Same app, same data.
At a glance
The operational details.
| Tenancy | Multi-tenant: a shared, managed platform with logical per-tenant isolation and your own subdomain. |
| Operated by | Us — provisioning, updates, scaling, monitoring, and backups. Nothing to run on your side. |
| Time to start | Minutes. Create a class, share a join code, and students are building racks. |
| Access | Your subdomain. Students join by code and display name; staff use standard accounts. |
| Privacy | Data-minimisation defaults; no telemetry by default; no profiling, ads, or model training on student work. |
| Billing | Per seat, by purchase order or invoice for education. First pilots are free or discounted. |
Data & compliance
Fast to start, still careful with data.
- Per-tenant logical isolation between schools
- Student join needs only a code and display name — no email
- No telemetry by default; opt-in only
- No advertising, profiling, selling data, or training models on student work
- Retention limits and deletion-on-request built into the schema
- Signable DPA and a plain-language privacy fact sheet included
The same minimisation, hosted
Choosing the fastest tier does not loosen the privacy stance. The defaults that protect minors are identical across cloud, dedicated, and self-hosted.
Pilot regions
Cloud pilots run in the United States and Canada, ready for California (SOPIPA / AB-1584) and British Columbia (FIPPA) with the right paperwork.
Be making sound this week.
Request a cloud pilot — the first pilots are free — and we will set up your tenant and a class.
FAQ
Questions about cloud.
How are different schools kept apart on a shared service?
Every school is a separate tenant with its own subdomain, and each tenant’s data is logically isolated from every other tenant’s. A user in one school cannot see or reach another school’s classes, rosters, or patches.
How fast can we start?
Minutes. There is nothing to provision or install — we create your tenant and subdomain, you create a class and share a join code, and students are building racks immediately.
Is student data still minimised on cloud?
Yes. The same data-minimisation defaults apply: students join with a code and a display name, with no email or personal information required. There is no telemetry by default, and no profiling, advertising, or model training on student work.
What if we later need stronger isolation or a specific region?
You can move to a dedicated single-tenant instance or to self-hosting at any time. It is the same application, so your classes and patches come with you.