What managed hosting is
Managed hosting means we run your deployment on a server of its own. No other school is placed on it. Your database, your secrets and your uploaded files are on that machine’s disk. Backups are described under regions and data residency. A group with several campuses shares one deployment, with the campuses separated inside the database.
So the answer to “is our data segregated from other schools” is “we have our own server, in the region we chose, and here is its backup”.
What that gets you
Section titled “What that gets you”Your own server. One customer per machine, in the region you named. Nothing another school does can consume the memory, disk or processor your desk is running on, because no other school is on it.
Your own database, rather than a share of somebody else’s.
Your own upgrade moment. One school can sit on the previous release while another takes the new one. Nothing forces every customer through the same change on the same night.
A named region. Chosen during the sale, recorded on your deployment, and shown back to you during onboarding to confirm. See regions and data residency.
Backups from the first night. From its first boot your deployment backs itself up every night at 03:00 and keeps each backup for 90 days, with an encrypted copy offsite. See backups in the app.
Certificates and renewal. Yours to name, ours to issue and keep current.
Updates handled for you. Every version runs on our own instance before it reaches any customer, and you are told before anything that changes the database. See updates.
What is still yours
Section titled “What is still yours”The configuration. Modules, workflow, roles, connectors, email templates.
Your identity provider. SSO and SCIM connect to your Entra or Google tenant. We cannot configure that from our side.
Connector credentials. You paste them in, and they are encrypted with your deployment’s own key before they touch the database. See what we hold on managed hosting.
A connector agent, if you want private systems connected. Active Directory, a local SIS database, PaperCut and printers on SNMP live inside your network. A managed deployment reaches them through an agent you install. It dials out only, so there is no inbound firewall rule to ask for. See connector agents.
Deciding who has access. Roles and accounts are yours, and so is support access: off until you grant it, for a set time and with a reason.
What leaves your region
Section titled “What leaves your region”Counts, versions and billing records. No names, no records, no ticket content in readable form. Offsite backup copies are encrypted with your deployment’s key and may be stored outside your region; see regions and data residency.
Your deployment reports count-only telemetry: Technical and Business seats, managed devices, students active in your student system, enabled modules and the version. The student count sits beside your licensed count for the anniversary re-count, and is never billed on.
Licensing, and what happens if billing goes wrong
Section titled “Licensing, and what happens if billing goes wrong”Entitlement lives in the signed licence your deployment already holds, not in the billing system. A school’s service desk keeps working through a billing outage, an expired card or a failed webhook.
Nothing in the billing path revokes anything. A failed payment starts a conversation; revocation is always a deliberate act.
Annual billing is the default, with automatic collection off, because most schools pay by transfer against a purchase order. Monthly billing is available on the terms in your order; see plans. A hosted payment page is available for anyone who would rather use a card or direct debit.
Overage accrues on the licence and is trued up at renewal as a single line, rather than raising a small invoice every month that finance has to process against a fresh purchase order.
Getting your data out
Section titled “Getting your data out”Settings, Backups exports a portable copy of your school at any time, without asking us.
- Onboarding for what happens between signing and your first login.
- Regions and data residency for the procurement answer.
- Your own domain for getting off
yourschool.plugboard.app.