Four products. One record underneath.
Most companies run IT, support, and HR on separate systems that each keep their own copy of the same employee, and every copy drifts. OhKube refuses to duplicate the table. One directory sync, one person record, and four products that join against it.
That is the whole argument, and it is worth being concrete about. On a four-vendor stack, “when a device is marked lost, open an incident, notify the owner's manager, and suspend their AI keys” is a quarter of roadmap. Here it is one rule, because the conditions and the actions read the same data.
What every product shares
One identity
Connect Entra ID, Google Workspace, or Okta once. Your people, teams, and groups sync in, and every product reads the same directory. There is no second user list to keep current.
One person record
The employee in People is the device owner in MDM, the requester in Desk, and the key holder in Swift. Not four copies kept in step by integrations, but one row that every product joins against.
One permission model
Roles and scopes are defined once and enforced on every API route in every product. Someone who changes teams changes access everywhere at the same moment.
One rule engine
Device compliance, ticket routing, and onboarding workflows are the same machine. Learn the builder once, and write rules whose conditions and actions cross products.
One audit trail
Every administrative action across the suite lands in one exportable trail, so answering “who changed what, and when” is a single query instead of four exports and a spreadsheet.
One console, one bill
Users, permissions, and billing in a single admin experience. No vendor portals to juggle, no reconciling four renewal dates.
The four products on top of it
Each one is a complete product in its own right. Teams adopt tools, not architectures.
The questions people actually ask
Do I have to buy all four?
No. Every product stands alone. Turn on Desk without MDM, run MDM without People. The platform is underneath, not in the way, and it is the reason adding the second product costs you a toggle rather than a project.
What happens to my existing identity provider?
It stays where it is. OhKube syncs from Entra ID, Google Workspace, or Okta rather than replacing them. Your directory remains the source of truth.
Is this a suite or a bundle?
A bundle is four products sold together with an integration tax. The test is whether a single rule can read one product's data and act in another without anybody building a connector. Here it can.
Start with one product. Feel the platform on the second.
You notice it the first time a ticket auto-links to the device it is about, and you stop noticing the seams entirely somewhere around week three.