Live in days, not quarters
Connect the directory you already run, turn on the products you need, and bring your existing data with you. OhKube is modular by design, and everything is pre-integrated from the first day.
Connect your directory
One OIDC connection to the identity provider you already run.
- ✓Entra ID connected via OIDC
- ✓412 people, 28 teams synced
- ✓Groups mapped to OhKube roles
- ✓Admins invited
Four steps, none of them a project
Connect your directory
Link Entra ID, Google Workspace, or Okta over OIDC. People, teams, and groups sync in, and your identity provider stays the source of truth. There is no second user list to maintain and nothing to import by hand.
Turn on the products you need
Enable MDM, Desk, Swift, or People per team. Each one inherits the users and permissions you just synced, so the second product costs you a toggle rather than another onboarding project.
Bring your existing data across
Migration tooling imports devices from your previous MDM, tickets and their history from your old service desk, and reconciles asset records rather than leaving you two sources of truth.
Go live and let the rules work
Sensible defaults mean the console is useful on day one. Automation rules take over the routine: routing tickets, enforcing compliance, provisioning on a start date, revoking on a leave date.
You are not starting from an empty console
The reason migrations stall is rarely the new tool. It is the years of history in the old one. That comes across.
Devices, profiles, and smart groups, without a re-enrolment walk-up.
Tickets, history, queues, and SLA definitions.
Point one base_url at the gateway and the inventory builds itself.
What week one actually looks like
Directory connected, admins invited, first product enabled.
Enrolment profile out to a pilot group. Smart groups built from your real team structure.
Migration import runs. You reconcile anything the de-duplication flagged.
Automation rules ported and tested against the pilot group.
Rollout widens. Self-service portal published to everyone.
Questions we get before the demo
What if we only want one product?
That is the common case and it is fully supported. Every product stands alone. The platform underneath is what makes adding a second one cheap later, but nothing obliges you to.
Do we have to replace our identity provider?
No. OhKube syncs from Entra ID, Google Workspace, or Okta rather than replacing them. If you change something in your directory, it lands here.
What happens to the tickets and devices in our current tool?
They come with you. Migration tooling imports device records, ticket history, and asset data, and flags duplicates for you to resolve rather than silently merging them.
How much of our time does this take?
Most of the first week is pilot-group work rather than console configuration. The guided setup covers the defaults; you spend your time deciding policy, not filling in forms.