Principles
Ten lines we hold ourselves to.
Warpbeam is meant to hold every identity the way a warp beam holds the warp: in one place and under the same rules. A manifesto is worth exactly the decisions it forces. So under each line is what follows from it.
One product, not a stack.
Running identities securely today means running five to ten products. Warpbeam aims to take on what is spread across many products today, in one fabric: every function the market knows for an identity job, with a way out of each product category it replaces.
Simple is a security property.
What nobody understands gets misconfigured. Every function has to work for a small team without weeks of consulting.
Every identity counts.
People, machines, services and AI agents are threads of the same warp. An AI agent always has a human who answers for it, and never more access than that human.
Do it ourselves, connect openly.
Our principle: Warpbeam does every identity task itself, with an engine of its own: from the sign-in service and sessions on servers to security event analysis and the AI. Only basic building blocks come from outside, such as the operating system, database, libraries and open standards. Existing systems can be connected on top; none of them is a prerequisite. Today Warpbeam still needs your existing directory; the way there is on the roadmap.
Identity sovereignty: the threads stay in your hands.
Authority over identities, access and sign-in belongs to the organisation, not to a vendor, and not to us either. So every way in comes with a way out.
The AI acts only as far as people allow.
Per kind of task, across six levels, bounded by principles that can't be switched off.
Every decision leaves evidence.
Who allowed what and when, human or AI, stays provable. Auditors should be able to ask, not dig.
Organisation is part of the product.
A function is done when it ships with its process, roles, policy and metric. Technology alone isn't identity management.
We're regulated too.
Warpbeam falls under the rules for AI, for products with digital elements and for data protection. We treat that as a design input, not an afterthought.
We never call it finished before it is.
Every capability carries its maturity level from 0 to 4, measured against the code, not against our wishes. On this page and everywhere else.