Skip to content
Webrack Platform

How it is delivered

One product, three ways to run it.

The same Webrack application, deployed to match your data-control and operations requirements: on your own servers, on a dedicated instance we manage, or on our shared cloud. This is the technical overview for the people who have to sign off on it.

The shape of it

How a request flows, at every tier.

Audio is synthesised in the browser on the student’s device. The server stores accounts, classes, and saved patches, and serves the application — it is not in the audio path. What changes between tiers is where that server lives and who runs it.

Classroom device browser audio TLS / HTTPS reverse proxy Application accounts · classes Data store patches · roster
Audio is computed on the device. The application server handles accounts, classes, and saved patches, behind TLS. The same architecture ships in all three tiers; only the hosting boundary moves.

Compare

Self-hosted, dedicated, or cloud.

Self-hosted Dedicated Cloud
Where it runs Your own servers A single-tenant instance we operate Our shared multi-tenant service
Data location On your premises A region you choose (incl. Canada, non-US) Our cloud region
Isolation model Your organisation only Dedicated instance, isolated for you Per-tenant logical isolation
Who operates it Your IT team We do We do
Time to first class Hours–days (IT setup) Days Minutes
Air-gapped / offline Supported No No
Updates You apply on your schedule We apply, coordinated with you We apply continuously
Data residency answer Strongest Strong Standard
Billing Per-site licence Managed plan Per-seat

Not sure which fits?

Tell us your data-residency rules, device fleet, and timeline. We will recommend a tier and scope a pilot.

FAQ

Common delivery questions.

Can we move between tiers later?

Yes. The application is the same across all three tiers — only where it runs and who operates it differ. Many schools pilot on cloud for speed and later move to a dedicated or self-hosted deployment as procurement and IT review complete. Patches and class data come with you.

Is there any Cloudflare or vendor lock-in?

No. The application is designed to be self-hostable on ordinary infrastructure via a Docker bundle, so it is portable across hosts. (This marketing site happens to use Cloudflare Pages, but the app itself does not depend on it.)

Which tier is right for us?

If you must keep data on premises or run air-gapped, choose self-hosted. If you want isolation and a specific data region without running infrastructure, choose dedicated. If you want the fastest start with isolation and minimisation built in, choose cloud. If you are unsure, request a pilot and we will scope it with you.