What it takes to run Anchor for your school.
Anchor is self-hosted: your school runs its own backend in your own Azure tenant, and student devices talk only to that. This page is the IT summary — requirements, how it deploys, rollout, and the network shape. For the authoritative, step-by-step setup it hands you straight off to the GitHub docs, which are kept current with the code.
Requirements
Anchor is deliberately narrow: Edge-only enforcement on students' Windows laptops, one backend per school. It works on school-managed and bring-your-own laptops alike: managed laptops get it through Intune, and nothing depends on a laptop being managed. That focus is a design choice, not a roadmap gap — there is no Mac, Chromebook, or iPad student client, and no multi-tenant SaaS.
Student agent
Windows 10 version 1809 or later, or Windows 11. A native tray app that IT pushes through Intune, or that the student installs from a Setup.exe on their own laptop: it installs for that Windows user only, needs no admin rights, starts when they sign in to Windows, and updates itself. There is no Mac, Chromebook, or iPad agent.
Browser
Microsoft Edge (Chromium), with the Anchor extension. Edge-only by design: URL enforcement runs inside Edge, so other browsers are out of scope on the student device.
Teacher dashboard
Any modern browser. The dashboard is a web app — nothing to install on the teacher's side, on whatever device they already use.
Backend
Microsoft Azure, in the school's own subscription: an App Service on the Basic B1 plan (Always On), an Azure SQL Standard S0 database, and the teacher dashboard on a free-tier Static Web App. For a school of around 1,000 students that's about €24 a month (Azure list prices, Belgium Central, excluding VAT), or about €43 if the database needs Standard S1. Single-tenant by design.
How it's deployed
Self-hosted, single-tenant, in your own Azure
You run one Anchor backend for your school, in your school's Azure subscription. The student devices and the teacher dashboard talk only to that backend — your data stays in your Azure. Plink Labs operates no backend, receives no student data, and has no access to your deployment.
Sign-in reuses the school's existing Entra ID: teachers and students sign in with the Microsoft accounts they already have, against your own tenant. The deploy creates two single-tenant Entra app registrations (the API and the dashboard SPA); there are no separate Anchor passwords to manage and no third-party identity provider in the loop.
Rollout
Three pieces, in this order: you stand up the backend and publish an agent release, then the agent reaches the laptops, through Intune on school-managed ones or from a Setup.exe a student runs on their own laptop, and the extension follows. The GitHub docs carry the exact commands and settings — this is the shape of the work.
01
The backend
In your school's fork of the repository, stand up your Azure backend with scripts/setup.ps1 — one command provisions the resources, the Entra registrations, and the GitHub deploy wiring. A direct Bicep deploy and a portal walkthrough are documented as manual alternatives.
02
The agent
Push an agent release tag on your repository. The release workflow builds a Setup.exe with your backend's address and Entra IDs baked in and publishes it on your repository's GitHub Releases, together with an install script for Intune. On school-managed laptops, package the two as an Intune Win32 app that installs for the signed-in student and starts the agent right away; the Intune guide has the settings. After that, the agent updates itself, so there is nothing to push per release. On their own laptop, a student runs the Setup.exe themselves: no admin rights needed, though the installer isn't code-signed yet, so Windows SmartScreen asks them to confirm once.
03
The extension
On school-managed laptops, an Intune configuration profile force-installs the Anchor extension from the Edge Add-ons store; the agent finds that policy and asks the student nothing. On other laptops the agent offers to set the same Edge policy itself, with one Windows permission (UAC) prompt. If the student can't or won't approve it, the agent opens the store listing so they can add the extension in one click. Uninstalling the agent offers to remove the policy it set (another UAC prompt) and never touches one your Intune profile manages.
Network
Plain HTTPS outbound — no proxy surgery
Everything runs over HTTPS/TLS. Each student device makes outbound connections to your school's App Service (by default anchor-api-<suffix>.azurewebsites.net), which serves both the API and the realtime session channel. The realtime channel runs inside the API itself, so there is no separate SignalR service to allow — just make sure outbound HTTPS to that host permits WebSocket upgrades. Beyond that, devices sign in through Microsoft Entra ID (login.microsoftonline.com), and the agent checks your repository's GitHub Releases for updates.
Anchor needs no proxy certificate, no TLS interception, and no MITM on its connections. Because enforcement and reporting are device-resident and outbound-only, it is BYOD-friendly: it does not depend on devices sitting behind a particular network, so it works on school Wi-Fi and at home alike.
Read the authoritative docs
This page is a summary; the GitHub docs are the source of truth and track the code. Start with the setup guide and follow its links.
What Anchor is, the architecture diagram, the five components, and how to build and run each piece locally.
The authoritative end-to-end setup: Entra app registrations, the Bicep deploy, App Service settings, admin consent, and the GitHub secrets/variables — with a manual fallback for every step.
The deploy pipeline, how to cut an agent release, and the authoritative inventory of every secret and variable the workflows consume.
Rolling the agent out through Intune: packaging the Win32 app, the install command, detection rule and return codes, the Edge extension policy, updates, and uninstall.
The Azure infrastructure: the one-command bootstrap, the direct-Bicep deploy, the portal walkthrough, every template parameter, and the resources created.
Get started
Deploy the backend, then roll out the clients
Stand up your school's backend first, then publish an agent release from your repository. Push it through Intune to your managed laptops, together with the Edge extension policy, and share its Setup.exe with students on their own laptops. The setup guide walks the backend end to end, the release guide covers the agent release, and the Intune guide the rollout to managed laptops.