Plugboard docs
Run your whole ICT desk from one tab
Tickets, people and devices in one desk, with each device’s loans and repairs, connected to the device management, student information and identity systems your school already runs. These pages cover installing it, setting it up and running it day to day.
Search the docs
Start from a job
Find your way in
First time here
Start with what Plugboard is, then the words that appear on every screen.
Evaluating it
How the two deployments differ, how the licence is priced, and what we process. A demo comes first, then a 30-day trial on your own school’s data.
Deploying it
Install it on your own server or let us host it, then work through the checklist from first sign-in to a working desk.
Running it day to day
Every screen a technician touches, in the order a job moves through them.
The parts of the product
- The technician consoleTickets, loans, devices, people, stock, costs, reports and settings. This is where the desk works.
- Self-service portalsA kiosk students tap into, repair tracking for anyone with the link, an induction kiosk, a parent portal, a help centre and a public status page.
- ConnectorsDevice management, student information, directory, email and SMS, warranty, network, printing and AI, each with its own setup page.
- The API and MCP serverA public REST API, signed outbound webhooks, a realtime event stream, and an MCP endpoint for AI clients.
- ReferenceEvery environment variable, permission, module, capability, event and email template, in one place.
Two ways to run it
Plugboard is the same software whether you host it or we do. What changes is who patches it, where the database lives, and who holds the encryption key.
| What differs | You host it | We host it |
|---|---|---|
| Where it runs | Your server, your network | A server we run for your school alone, in the region you chose |
| Who updates it | You, when you decide | Us, on a ring schedule you can move within |
| Encryption key | Yours, and only yours | Held per deployment, escrowed by us |
| Private systems | Reached directly | Reached through a connector agent |
| Application data | Wherever your server is | In the region you chose |
| Offsite backups | Wherever you send them | Encrypted copies by a location hint: Oceania, best effort, for Australian schools |
See choosing a deployment for the decision in full, including the questions a procurement office usually asks.