The name
Why Warpbeam?
On a loom, the warp beam holds every lengthwise thread in order and under tension; only then does cloth hold together. Warpbeam is the warp beam for your identities. With sound, the video explains the name in 43 seconds.
Narration of the video
Above, the video plays without sound. “Play with sound” starts it again from the beginning, with sound and English captions.
Read the narration
On a loom, the warp threads are wound onto a roller: the warp beam. It keeps them in order and under tension. The weft runs across them. That is how cloth is made. In Warpbeam, every warp thread is an identity: a person, a service account, a machine or an AI agent. The weft threads are your applications and access. The tension is your rules. The cloth is your identity fabric. A loose end is an orphaned account. A tear is an attack path. Warpbeam finds both, because every identity is held in one place. Warpbeam. The warp beam for your identities.
Picture and mapping
From loom to identity fabric.
The picture
Woven cloth is made of two sets of threads. The warp threads run lengthwise; before weaving they are wound onto the warp beam, the roller at the back of the loom. It keeps them in order, side by side and under even tension. The weft threads are passed across and, depending on the pattern, lie over or under the warp threads. At the front, the cloth beam takes up the finished cloth. Without a warp that holds, no cloth will hold either.
The mapping
Every identity is a warp thread: people, service accounts, machines and AI‑agents. Applications, systems and access to them are the weft threads that run across the warp. The cloth that results is the identity fabric.
Warpbeam is the warp beam: it holds every identity in one place, in order and under control, and every fabric starts from this warp. The tension is your rules: lifecycle, policies, tiers for administrators and access rights.
On the architecture page, the other parts of the loom stand for the building blocks of Warpbeam.
What it gives you
- One source of truth
- Every identity lives in one inventory instead of as a copy in every product; today Warpbeam brings together your existing directory and other sources for this.
- Even control
- The same rules apply to every identity, human or service account; roles, policies and time-limited rights are usable today.
- A loose end is a risk
- An account that nobody uses or answers for any more is an orphaned account that an attacker can use unnoticed; today Warpbeam finds accounts nobody has signed in to for a long time.
- A tear is an attack path
- Where rights interlock so that an ordinary account can reach admin rights, the fabric tears; today Warpbeam calculates such attack paths in your existing directory in part: from the weaknesses it finds; paths through sign-ins and local admin rights are still missing.
Three key points
What holds the warp beam.
-
One product instead of many
Accounts, access, sign-in, privileged access, detection and evidence are meant to sit in one fabric, with one interface and one truth.
Principles -
An engine of its own in every capability
Warpbeam is meant to deliver every capability with an engine of its own; other products can be connected, but none is meant to be a prerequisite. Today it still needs your existing directory.
Architecture -
Identity sovereignty
The threads, meaning your identities, stay in your hands: the goal is running in your own data centre, without anyone else's directory or sign-in service.
Identity sovereignty