Solutions as platform building blocks
Platform6 solutions are pre-defined, documented Apple platform states. Each solution specifies the target state, technical enforcement (identity/ABM/MDM/baselines), and operating rules (lifecycle, updates, support, ownership) — so the state remains explainable and sustainable in daily operations.
Horizontal: platform governance as the base
The state that ties everything together: identity as the control plane, ABM-driven lifecycle, clear baselines, update mechanics and operating rules. This is the base that makes any workload stable.
Vertical: operating reality per context
Workloads differ not by “features” but by dependencies: maintenance windows, support boundaries, offline constraints, data flows, accountability. Vertical solutions make this reality explicit and operable.
Current solutions
Every solution is described as a state: target, technical enforcement, operating rules and ownership. This makes it repeatable — and explainable internally.
indigo — iOS for Government
A certified MDM is a prerequisite for classified and NATO RESTRICTED use, and on its own it is not enough. The operational environment around the certified server sits outside the certification boundary: enrollment pipeline, identity model, SCEP/EST certificate infrastructure, governance documentation. That is where approval projects stall.
- VS-NfD / NATO-RESTRICTED deployments
- BlackBerry UEM as certified MDM base (PP-0116, EAL4+)
- Brightsite and Darksite OE design
Apple Platform NIS-2 Readiness Accelerator
A defined Apple platform state for time-constrained execution pressure: linking identity coupling, baselines, operating rules and evidence so security can show effectiveness and operations can sustain it.
- Identity + access: Platform SSO/access logic tied to device state.
- Baselines: macOS/iOS/iPadOS target states, measurable, with documented exceptions.
- Operations: update/patch mechanics, ownership & escalation, handover to ops.
TAPS · The Apple Practice Standard
A defined operating state for tomedo practices running Mac and iPad: Platform6 runs the platform and releases every combination of macOS, tomedo and drivers; IT partners sell, install and support on site. Patient data stays in the practice.
- Release per device role: client, server, HZV separately, tested in the lab and in pilot practices.
- Sees what the MDM cannot: connector, card expiry, GDT, DICOM, backup; reported directly in tomedo.
- Evidence: monthly report per practice on the KBV IT security directive.
Sovereign Apple workplace
A governance-strong platform state for regulated organizations: role model, ownership architecture, controls as technical states, and evidence via configuration and operational artifacts.
- Governance: accountability, decision rights, escalation paths.
- Controls as states: technical controls as an explainable target state.
- Evidence: traceable via status, configuration, runbooks, handover.
BSI MDM-TS certification map
Which MDM products are certified for classified environments, which still run under a transition period, and which architectures are structurally out of scope. One page, kept current.
How solutions fit the model
Landing zone / transformation
This is where non-negotiable platform decisions are set: identity coupling, enrollment path, baselines, update mechanics, support guardrails and ownership.
Workload-specific operating rules
Vertical solutions make dependencies explicit: maintenance windows, remote support scope, runbooks, exception rationale and handover into operations.
Contact
Send 5 lines of context. You’ll get a clear mapping.