Identity
Sign-in that lives on your infrastructure.
Every client gets its own Kuartal ID instance, running on a VPS we provide or on infrastructure we build for you. Credentials never sit in a shared, public directory.
Why it matters.
Your staff sign in to the Cortex that runs your workflows. That sign-in, and every credential behind it, should be stored where your data is: inside your walls, not in someone else's cloud.
How it works.
-
01
One instance per client
Your Kuartal ID is separate from the public one used by consumer products, with its own users and its own keys.
-
02
Hosted where you choose
It runs on a VPS Kuartal provides for you, or on servers and architecture we build inside your organisation.
-
03
Connected to your Cortex
The same sign-in opens your Bedrock consoles and platforms, so access rules are set once.
-
04
Your rules for access
You decide who gets in and what each role can see; the audit trail stays on your side.
Where identity sits.
Consumer products use the public Kuartal ID at id.kuartal.id. Client instances are set up as part of a deployment.