Mobile app coming to Google Play
Everything your technology team runs, on one server you own.
TechDash is an IT-operations platform for school districts. The help desk, the knowledge base, board policy, the asset register, network and infrastructure monitoring, door access and paging — one sign-in, one permission model, one audit trail. Delivered and operated as a managed service by Alextricity Technologies, LLC, on a server your district owns.
The problem
Seven systems, none of which answer your question.
A district's technology work is scattered across a help desk in one vendor's cloud, an asset spreadsheet, a switch vendor's controller, a door vendor's Windows PC, a paging system nobody can inventory, a policy PDF, and a shared drive of tribal knowledge.
Each answers its own question. None of them answers the district's: what is broken, who is affected, what did we do about it, and can I prove it?
TechDash puts those on one server the district owns — and puts the parts a technician needs while walking a building into their pocket.
How it fits together
Two halves, one system.
The dashboard
A web dashboard running on your organisation's own server — its own database, its own configuration, its own data. It is the technology team's daily working surface, and the place the business office gets its numbers from.
The app
One app for every organisation. It ships with no customer list and no server address inside it. A staff member types their work e-mail, the app asks that domain's own server whether it publishes a discovery document, shows the organisation's name and address, and asks the person to confirm before anything is saved.
What it does
Capabilities, stated precisely.
Every claim below describes behaviour that is built, enabled and running today.
Policy and knowledge that stay with the district
Board policy, searchable, on any device
Staff browse board policy by chapter and section, search the full text of every published policy with relevance-ranked results, and bookmark the sections they return to. Bookmarks follow the person across devices. Unpublished drafts stay invisible to everyone but an administrator.
A knowledge base with real revision history
Markdown articles in a category tree with tags and attachments, full revision history with one-click restore, related-article links, helpful and not-helpful votes, and view and search analytics for administrators.
The work, measured
Help desk reporting built for month-end and for invoices
Pick a date range and which date it applies to — created, updated or closed — then filter by status, priority, category, assignee or requester. You get ticket counts by each of those, plus resolution time as an average, a median and a 90th percentile, so a handful of long vendor waits cannot misrepresent the typical repair. Sortable detail table, one-click CSV export.
Carry-over that measures work, not timestamps
Optionally include tickets opened before the period that were genuinely worked inside it — measured by a reply written or the ticket closed in the window, not by a last-modified date. A ticket opened in one month and closed in the next appears in both months' reports. Each run returns up to 5,000 tickets and the page states plainly when the result set is larger.
The campus network, watched and put back
A live campus map with diagnostics in the page
A geographic map of every node in your monitored inventory with clustered status markers, a device list grouped by location or role with per-group fault badges, and ping, traceroute, DNS and port checks without leaving the page.
Bounded automatic recovery for virtual machines — opt-in, and off by default
A console showing per-node failure counts, eligibility, cooldowns and live hypervisor connectivity, with one-click Restart and Unlock and a timestamped log of every action and who or what triggered it. Every bound is real: it never acts on the server it runs on, it stops on a per-node cooldown and a daily action cap, it stands down during backup windows and maintenance mode, and it re-checks the hypervisor before acting so a network blip never restarts a healthy machine.
The physical campus
Vendor-agnostic door access control
Doors, door groups, unlock schedules, credential holders, access grants and campus-wide emergency modes are modelled once and driven to the hardware through swappable drivers. Desired door state is reconciled against the panels every minute, so a door that drifts is put back. Every driver declares exactly which features its hardware supports, and an action it cannot perform safely is refused with a reason rather than failing silently. Every command sent to a device lands in a queryable, exportable action log.
A paging coverage audit read from the handsets themselves
Reads multicast paging configuration directly out of the handsets and ceiling speakers and reports which endpoints actually hear which all-call group — the check against a page that provisioning believes was delivered and the phone never applied. It audits every endpoint it can reach and names the ones it cannot, and a value it could not observe reads as unknown, never as zero.
Why it is built this way
The parts a district's auditor asks about.
Sign-in fails closed
Interactive sign-in is Google Workspace SSO restricted to your domain, compared
as an exact equality test. A subdomain, a trailing dot, a look-alike suffix or a
second @ are all refused, and the gate runs before any account
record is created, so a refused address leaves nothing behind. If the domain
setting is blank, nobody gets in.
Files inherit their record's permission
The upload directory is denied wholesale at the web server, and every gated file is served by a route that re-applies the owning record's own rule. A file on an internal note stays hidden from the requester. An unguessable URL is never treated as protection.
Looking at usage data is itself audited
The usage dashboard requires an administrator and an identity named explicitly in configuration — an empty list means nobody, and there is no "all admins" setting. Every open, drilldown, export and denial is written to an audit table the module itself displays.
Your data
It stays on your server.
Alextricity Technologies operates the platform as a managed service. The district owns the data on its own server. The mobile app holds a session and cached screens on the device and nothing else; there is no third-party analytics, advertising or tracking in it.
The full detail — what the app stores, what leaves the device, how long things are kept and how to exercise a data right — is in the privacy policy.
Talk to us.
TechDash is delivered as a managed service: we stand up and operate the server, your district owns the data on it. If you would like to see it, get in touch.