Grydor documentation

Grydor is a unified endpoint management service for small and medium-sized IT teams. This documentation explains what administrators need to decide, what devices will do, and which evidence Grydor records.

Start with a controlled rollout

1. Create an enrollment policy for the platform you are introducing.
2. Enroll a small pilot group that represents your real hardware and network conditions.
3. Confirm inventory, compliance, software, and management-channel health.
4. Publish policies to the pilot ring before expanding to broad deployment.

Management channels

Grydor keeps native MDM and the Grydor Agent as separate identities and execution channels. Apple MDM and Windows OMA-DM apply operating-system policy and device actions. The Agent handles inventory, scripts, Win32 or macOS software, and the supervised osquery sidecar. A successful Agent connection does not imply that MDM is healthy, and the Console reports both states independently.

Administrator roles

Owner and Administrator can change organization-wide configuration. Help Desk can inspect devices and perform approved operational work. Auditor is read-only. High-risk actions retain the actor, reason, target, result, and trace identifier in the audit trail.