01Fleet policy · config
Decide once what "healthy" means for your fleet. Minimum OS, how fast patches land, who gets admin. Spruce holds the line from there.
Illustrative controls. Slide and toggle them, then hit Set it.
02Spruce Data Engine
Your policy becomes one small object. The engine collects from the systems you already run, matches every device and person across them, and records which system said what, and when. It does what APIs and MCPs can only dream of: agree with each other.
Collected on a schedule. Changes still land through your own MDM.
03Requests
The engine catches everything. It only decides the safe things. Anything that could break a classroom or a payroll run becomes a request, and a real Apple-certified technician picks it up, fixes it, and confirms the fix landed.
APNs certificate expires in 6 days
Renewal needs the Apple Account that created the original push certificate. Renewing with a different one would cut your MDM off from all 312 devices and force re-enrollment, so this is gated for a human.
Dashboard
Set minimum OS, patch deadlines, account type and MFA once in the Spruce portal. Ask it a question in plain language and get back a filtered view of your fleet, built from real records.
Data engine
Spruce collects from Jamf Pro, Mosyle, Microsoft Entra ID and an optional lightweight macOS agent, matches each device and person across them, and records which system said what, and when.
AI automation
Drift is measured against your policy. Decisions already on file are applied by narrowly scoped automations. AI turns requests into checkable instructions and never acts on its own.
Human oversight
Anything that could disrupt a classroom or a payroll run waits for a person. A technician approves or makes the change in your own MDM, and it closes only once the result shows up in fleet data.
Questions the page doesn't answer? Ask us directly.
Save an insane amount of time and money. Set the policy once, let the engine hold it, and let people who do this all day handle the rest.