Every Mac.
Every Classroom.
Under Control.

Stēre is designed and optimised for school-managed environments. However, because Stēre features kernel-level self-defence architecture, it delivers absolute, un-bypassable enforcement across both school-owned and BYOD (personally-owned) devices.

Once installed, the application cannot be removed, disabled, or bypassed by the user — even if the student has local administrator privileges on their personal machine. While we still recommend deploying Stēre via your school's central IT infrastructure for streamlined fleet management, the application guarantees the exact same strict compliance and exam lockdown security on any supported device it runs on.

Stēre features ironclad, active tamper protection that completely prevents unauthorised removal. It cannot be uninstalled, dragged to the Trash, renamed, or modified by a student.

Furthermore, Stēre's defences protect it against advanced removal attempts; it will actively block termination or deletion even if a user attempts to use high-level administrative overrides or terminal commands. Any unauthorised attempt to tamper with Stēre's files or processes is instantly rejected by the operating system. Authorised removal is strictly restricted to a secure, cryptographically authenticated administrative workflow that can only be triggered by your school's verified IT team.

Yes. All policy enforcement — app blocking, time rules, device control — runs entirely locally. The device licence is cached and validated cryptographically without any network call. Stēre performs a daily check-in with the licence server when connectivity is available and includes a 7-day grace period for full licences to handle extended offline scenarios like camp trips or exam rooms with no internet.

Any MDM that can deploy a .pkg installer and push a configuration profile. This includes Jamf Pro, Jamf School, Mosyle, Kandji, Microsoft Intune, Meraki Systems Manager, and others. Stēre is not tied to any specific MDM vendor — it uses standard macOS managed preferences that every MDM platform supports.

Yes. You can push different policy profiles to different device groups via your MDM. Year 12 exam rooms, Year 7 labs, and staff devices can each have their own tailored rule set — managed independently using your MDM's existing scoping and group assignment features. Each device runs the profile assigned to its group.

The Emergency Bypass system lets an admin issue a signed unlock token from the Stēre dashboard. The token is delivered to the device within seconds via the next polling cycle — no need to walk across campus, physically touch the machine, or push an MDM profile change. Bypass can be scoped to network-only or full access, set for a fixed duration, and revoked remotely at any time.

Stēre requires macOS 15 Sequoia or later, and runs natively on both Apple Silicon (M-series) and Intel Macs.

Billing is based on the number of activated device seats in your Stēre account — the number of unique hardware devices that have successfully activated against your OrgToken. You can see this count in real time in the admin dashboard. Devices that are decommissioned can be released to free up a seat.