From the first support request to the next campus-wide project. Connect your people, assets, facilities and systems in one workspace built for education.
30-minute walkthrough · Live demo with no sign-up
Now in beta. Try it free, with onboarding included.
A request is only the start. Plugboard connects the people, equipment and follow-through behind it.
Give staff, students and families a clear way in. Route requests to the right service desk, with the person, location and device already in view.
Bring a facilities request into a project. Reserve a resource, track a repair or prepare a purchase. Each team sees the work it needs, with access you control.
Let the assistant find context and prepare supported actions. Review what will change before approving it, and keep the outcome connected to the work.
Set up shared laptops, check the room equipment and coordinate the furniture move.
A shared project. Clear ownership.
The assistant prepares the action. You decide whether it goes ahead.
Permissions apply to every supported action.
Start with the workflows your team needs. Add modules as you grow, and keep each campus, team and role focused on the work they do.
Give people a simple way to ask for help. Give your team the context, ownership and tools to see it through.
Department desks and service forms keep requests organised, with role-based access.
Track response and resolution targets, automate routine steps and escalate work that needs attention.
Connect the knowledge base with student, staff and parent self-service portals.
View full sizeBring its owner, location and service history together. Follow equipment through everyday use, repairs, loans and retirement.
See fleet inventory and management context alongside the people and places that use it.
Manage loan pools, repair progress and collection workflows from the same workspace.
Track stock, warranty information and retirement records to support lifecycle decisions.
View full sizeA room refresh, a new starter, the next school year. Turn the moving parts into connected work with clear owners and shared context.
Bring projects, work items, resource bookings and equipment lending into view.
Coordinate inspections, recurring maintenance and replacement planning for registered resources.
Connect shared approvals and purchasing with the work that needs them.
View full sizeAsk the assistant to look things up and prepare supported actions. Keep your team in control of what changes and where model context goes.
Find people, devices and knowledge through the tools your role is allowed to use.
Action reviews show what is about to happen, with an explicit approval or cancellation.
Choose a local or configured model, alongside identity, device, finance, API and MCP integrations.
View full sizeAuto-numbered loans with MDM serial autocomplete, bulk pull from a device group, holder history and policy links.
The full repair lifecycle: configurable coverage, repair types, vendor sync, ready-for-collection, costs and outcomes.
Use the ticket system that comes with the desk, or connect Zendesk, Salesforce and more. Statuses and types map across and stay in sync.
A request is filed against the service it concerns, then sorted, prioritised and routed as it lands, the way ITIL asks for.
Response and resolution targets per priority, with automatic escalation and alerts when a ticket is heading for a breach.
When-this-then-that rules handle the routine: auto-assign, notify, change status, escalate or fire a webhook, with no scripting.
Put the actions your desk actually takes on the ticket itself, pressed by hand or fired by a rule, and bounded so a button can never reach past the permissions of whoever presses it. A ticket that names a service links to its monitor, and the article that resolved it is recorded on it.
Break costs down by repair type, coverage, month or your own terms, schedule reports to email out, and export to CSV.
Track consumables and assets from purchase to retirement, with stocktake, charges, budget codes and per-client purchase records.
Hand out and collect school-issued devices each year, with reusable programs, custom fields, photo check-in and on-the-spot swaps.
One record per device, assembled from everything that reports it: the MDM, the warranty vendor, Apple School Manager and the asset tag on the lid. Where two systems disagree the page shows both rather than quietly picking one, and a field nobody reports says so instead of reading as zero.
Retire a device with the evidence attached: who wiped it, when, by what method, and where it went. The certificate lives with the asset.
A remote wipe and a local administrator password are off until two different permissions switch them on. Both require fresh verification, typed serial confirmation and a written reason. Wipes also use a cooling-off period and, by default, a second approver, and the audit row is written before the command leaves rather than when it comes back.
Charge a family for a cracked screen and keep the record of who approved it, when and for how much. Parents see it in their own portal.
A self-service knowledge base for the common fixes, plus satisfaction surveys that tell you how each job landed.
Read live Entra and Google identity information beside the person record. SCIM provisions technician accounts; LDAP sign-in is separate from the legacy directory demonstration workflow.
Account state, registered MFA methods, Conditional Access and recent sign-ins, read live from Entra and shown next to the same person’s tickets, loans and devices. A sign-in from Jakarta reads differently there. None of it is stored, and the licences sitting on disabled accounts are counted on the same page.
Entra supports MFA reset, account state changes, session revocation, licence changes and password reset. Google supports account state changes and session revocation. Each one needs its own permission, a second factor there and then, and the person’s name typed by hand and checked against what the provider reports now.
Watch the print fleet from the same console, with toner levels, status and alerts pulled live.
Meraki, UniFi and SNMP switching merged into a single view instead of one vendor at a time: access points, switches, gateways and uplink loss, grouped by campus. A device that drops raises an alert on the monitor board you already run, and a ticket saying the senior school wifi is down finds the device it means.
Watch the services your desk depends on from a live status board, with HTTP, TCP, TLS and ping checks, certificate expiry and a public status page.
Ask it to find a student, look up a serial or lodge a repair, and it uses the same permissioned tools your technicians do. Container deployments can include a local model sidecar. Native/source installs need a separately configured model; without one the built-in command engine remains available. External AI connectors send context to their configured provider.
Run an Ollama model on your infrastructure or use Anthropic or an OpenAI-compatible endpoint on your own key. Managed plans with hosted AI use DigitalOcean Gradient AI; review the selected connector and provider terms.
Let us host Plugboard and still reach systems that never touch the internet. A small agent runs on your network and dials out, so there is no inbound rule and no open port to ask for. Credentials stay on your machine.
A documented REST API with scoped keys, outbound webhooks, and a built-in MCP server, so the systems and AI tools you use can work with the desk directly.
A live view of the day: stats, activity and who is doing what, with audit records for covered operations and configurable retention.
Choose modern or classic, light or dark, and navigation along the top or either side. Keep school defaults or save your own arrangement and dashboard.
Modules and limits vary by plan. Compare plans and pricing →
IT, Facilities and the school office each have their own work to do. Give them a desk that fits, with the context to work together.
Explore department desksPeople, devices and support requests, connected in the same workflow.
Location-aware service forms and recurring maintenance for the places you look after.
Dedicated desks, controlled membership and ticket transfers when another team needs to take over.
Connect the longer view to the everyday work. Projects, people and shared resources, alongside your service desk.
Link school-year projects to work items, resource bookings and shared approvals. Review purchasing through supported Xero or MYOB workflows.
Plan starter and leaver work from synced rosters. Capture stocktake serials offline, then review conflicts when you reconnect.
Monitor Q-SYS Cores, PJLink projectors and displays, Crestron XiO Cloud equipment and Zoom Rooms from the same campus view. Read supported status and faults alongside service alerts and ticket signals. Explore AV monitoring; validate your hardware and vendor account in a pilot before rollout.
Let the native assistant prepare supported actions for your review and approval.
These optional modules require explicit activation and entitlement. Confirm your plan includes them before enabling them.
A running copy of Plugboard, loaded with fictional students, devices and repairs. Lodge a job, issue a loan, run the assistant. Nothing to install and no sign-up.
Fictional data No sign-up Explore at your own pace
Some actions are disabled in the public sandbox (backups, connector credentials, API keys). Book a walkthrough to see those on your own data.
Keep the systems your school relies on. Plugboard connects your SIS, device management and identity tools, bringing the information your service desk needs into one workspace.
Managing a district? Plugboard 0.14.0 adds named connections for separate Jamf, Entra and Google Workspace instances, with shared or selected-campus coverage. Check your deployment version and read the district setup guide for supported workflows and rollout requirements.
The 0.14.1 interface update aligns buttons and form controls across the desk, including loan actions and readable tables on phones. Version 0.14.2 puts core identity, device and student systems first in Admin connector setup. Read the patch notes and check availability in your deployment.
AV adapters and TeamViewer status need a hardware or account pilot before production rollout. Extron and Teams Rooms integrations are planned. Calendar and chat workflows extend the Entra or Google directory connection; sign-in providers are configured separately. Finance exports require provider authorization, agreed mappings and approval. Review setup and supported operations.
Each portal is configured per institution. You choose what each audience sees, in your branding and your wording.
Access is scoped to schools, roles and campuses, with database protections that depend on the deployment. The detail a procurement questionnaire asks for is published in full: the security model, tenant isolation, what we process and who our sub-processors are, audit and retention, secrets and keys, and how incidents are handled.
Use managed hosting in your chosen region, or run Plugboard on your own infrastructure. Australian hosting is available today.
Assign roles by campus and require additional verification for sensitive actions. Keep access appropriate to each person’s work.
Trace covered actions in the audit log, set retention policies and export records. Review current audit coverage.
Run a configured local model on your own infrastructure, or choose an external AI provider. You control the connection and where its data goes.
A local model sidecar is available for container deployments, keeping inference on your infrastructure. Native/source installs need a separately configured model. Local inference needs no external AI provider. You can choose Anthropic or an OpenAI-compatible endpoint on your own key; managed plans that include hosted AI use DigitalOcean Gradient AI. The configured provider and data flows belong in your privacy assessment.
Connector secrets are encrypted in the vault and decrypted for the integration that needs them. The application redacts secret fields in normal responses and logs. Sensitive credential-retrieval actions have separate permissions, step-up and auditing.
Every record belongs to a single school, and nothing reaches across that line. On our hosting you get a server of your own — your own database, disk and backups, with no other school’s deployment on the machine.
Start from the built-in roles or write your own, and give somebody a role on a single site rather than across the group. Staff sign in with Entra, Google, custom OIDC or SAML providers, and you can require two-factor across the whole team.
Staff can sign in with a passkey, or use one as the second factor on a sensitive action. You decide whether passkeys are off, offered or required, and whether the one built into a shared staffroom laptop counts. Students tapping cards and parents following links are untouched.
Wiping a device, reading a local administrator password or resetting somebody’s MFA requires recent additional verification using a supported account factor. The audit row goes in before the command is sent, so an action that times out on the way home still left a trace.
The audit log records covered operations; authentication and some configuration changes have gaps. The normal interface does not offer audit editing. Retention and authorised erasure remove records according to policy; database operators retain administrative control. You can export audit records and manage retention.
Managed ingress uses HTTPS and edge protections. Public endpoints also apply request validation and rate limits; self-hosted operators configure their TLS and network controls.
Choose your hosting region and we put the residency statement in writing. Your application database lives in that region. Connector, email, external AI and edge processing have separate locations. Or run the application on your own infrastructure and choose its external connections. We can cover most regions to meet your school’s hosting needs.
Backups can run on a schedule and are encrypted. Export your own school whenever you want, and verify restores as part of your deployment runbook.
A configured local emergency account can provide access during an identity-provider outage, where your sign-in policy allows local authentication.
Choose your hosting region, or keep everything on your own hardware. Your data exports in full, so you can move between the two later.
Have something specific in mind? Talk us through your setup.
Plugboard connects to your student information system and device management tools. They remain the source systems; your team uses Plugboard to bring their information into service-desk workflows.
Optional department desks are included in Plugboard 0.12.0. They share ticket history, service forms and recurring work while applying department membership and existing role permissions. They are not a dedicated HR, finance or building-management system. Check the guide and prerequisites. We will confirm deployment availability and entitlement during your walkthrough.
Yes. Use Plugboard’s built-in ticketing or connect a supported external platform. We’ll review your ticketing system and the workflows you want to keep during the walkthrough.
Managed plans start at AUD 4,000 per year excluding applicable taxes, with SIS sync, student and parent portals, reporting, SSO and automation included from Core. Self-hosted pricing is 85% of the managed rate. See plan inclusions and pricing.
Three months free when self-hosted, or one month on managed hosting, with enabled modules confirmed during setup. Standard onboarding, a standard data import and one custom connector scoped with you are included. No credit card is required.
Run it on your own infrastructure and the first three months are free. On our hosting, the first month is free. Both include onboarding and migration, and neither asks for a credit card.
Beta trial offer
The platform is available to trial. Features vary by enabled module, connector and release; the documentation identifies demonstration workflows and unreleased changes.
Beta institutions get a direct say in what we build next. Ask for a connector or a workflow change and it goes to the top of the list.
You are early, so you may hit the occasional rough edge. In exchange the product is free while you trial it, and we fix what you find quickly.
When your trial is up, continue on normal pricing, stay on your own infrastructure, or walk away with a full export.