Questions, answered.

Security for identities that act on their own and for the people who decide what they may do. It covers people, service accounts and AI agents, and uses automation to investigate and respond to identity threats while your team keeps authority over what changes.

IT, security, identity and compliance teams in regulated organizations.

Human, non-human and AI-agent identities: the people in your directory, service accounts and app registrations, and AI agents.

Identity threat detection and response (ITDR) tools focus on finding identity threats. Orbitra is an identity risk remediation platform: it detects a risk, adds the context around the identity, remediates within rules your team sets, verifies that the change took effect and helps harden against a repeat, with people keeping authority throughout.

Yes. Orbitra connects to Microsoft Entra ID and Azure as an application that your administrators approve.

It starts with read-only access, so it can investigate without changing anything. Permissions that can change your environment are separate and narrowly scoped, and they’re added only when your team chooses to add them. Before you connect, we walk your team through each permission, why it’s needed and how to remove it.

Orbitra connects to Microsoft Entra ID and Azure today. Okta and Google Workspace are on our roadmap. Tell us what you use and we’ll share timing.

Remove Orbitra’s connection and revoke its application consent in your tenant. Access that was already granted can stay valid for a short time, depending on your identity provider’s settings.

Only actions your policy allows to run automatically, within limits you’ve approved in advance. Anything outside those limits, or without enough evidence, goes to a person to decide.

No. A recommendation can’t authorize itself. Authority comes from a defined policy and, where required, an authorized human decision, never from a model’s answer.

After a change, Orbitra checks that it actually took effect, so a requested action is never mistaken for a completed one.

Each action records who or what authorized it, so your team can see why every change was made.

Where customer data is processed depends on your deployment, and your agreement sets it out. We confirm the regions with you before you connect.

Not yet. We’re working toward SOC 2. During your evaluation, we share our security documentation and answer your security questionnaire.

Book a walkthrough. We’ll show Orbitra on your scenarios, review the permissions with your team and agree on the next step.