Your devices, enrolled, patched, and under control.

Jamf suits Apple-first estates that need deep management for Mac, iPhone, iPad, and Apple TV. Fleet suits teams that want one control plane across macOS, Windows, Linux, ChromeOS, iOS, iPadOS, and Android, or that need a self-hosted option. We check device mix, identity, application, hosting, and security requirements before we recommend either platform.

Yes, after an access and configuration review. We inventory enrollment methods, policies, groups, scripts, application packages, integrations, administrative roles, certificates, and open exceptions. The takeover plan identifies what Cloudnovi can retain, what needs repair, and which changes need customer approval before ongoing management starts.

We can plan and run a staged migration when the source platform, device ownership, supported operating-system versions, and enrollment method allow it. We start with a pilot, document user actions, protect recovery material, and define rollback or support steps before moving the wider estate. The assessment determines the migration path and expected user impact.

Jamf and Fleet support forms of bring-your-own-device enrollment, but available controls depend on the platform, operating system, ownership model, and selected subscription. We define the work-data boundary, employee communication, enrollment method, and offboarding procedure before any personal device joins the service.

Fleet supports self-hosted deployments, which lets the customer choose the infrastructure and data location. The final design still needs a supported database, cache, TLS, backup, monitoring, upgrades, and a confirmed Fleet commercial model. We cover those decisions during the assessment rather than treating self-hosting as a single checkbox.

We use device count and operating-system mix, the current management state, rollout or migration work, required controls, support hours, and hosting needs to define the service. The proposal separates onboarding, Cloudnovi management, software subscriptions, and optional security, identity, hosting, or support work so you can see what each part covers.

A supported platform can issue lock or wipe commands to enrolled devices. Cloudnovi sends a destructive command only after an authorized customer contact approves it through the agreed process. We document device identity, the request, the approver, and the outcome. Platform, enrollment, connectivity, and device state can affect command delivery.

The managed service covers the device-management platform, policy, approved changes, posture review, and remediation defined in the service schedule. General employee help desk, hardware repair, procurement, on-site work, and support outside agreed hours sit outside the base scope unless the proposal includes them.