Sarghaby Araghatta
Request a free assessment →
Home / Enterprise controls

Choose where Sargha runs and who can act, and keep one view.

Pick the isolation model, sign-in and response path that fit your risk, without losing one view across your whole estate.

Enterprise SaaS
  • Run by Araghatta
  • AWS us-east-1
  • Logical isolation per tenant
Dedicated tenant
  • Run by Araghatta
  • Dedicated compute, database and key
  • Scoped with you today
Your cloud account
  • Your VPC and your keys
  • Your data stays in your boundary
  • You run the boundary

Planned, not available todayRoadmap regional data planesRoadmap customer-managed keys

The boundary moves outward. The workflow does not.

Identity-native

SAML and OIDC single sign-on, SCIM provisioning, multi-factor sign-in, role mapping, and a break-glass path for vendor access and enforcement release.

Isolated by design

Every model uses tenant-scoped identity, encryption and audit controls. Regulated environments can add infrastructure, network and key isolation.

Response is separate

Discovery stays observation-focused. Actions take an approved control path, with its own audit trail.

Procurement-ready

Architecture, data processing addendum, data map, security assessment summary and operating policies, ready for your review board.

Honest about the roadmap

Planned, not available today: Roadmap regional data planes, Roadmap customer-managed keys, Roadmap private connectivity and Roadmap an air-gapped package. A dedicated tenant is custom work today.

How it works

Step by step.

  1. Choose a model

    Enterprise SaaS, a dedicated managed tenant, or your own cloud account.

  2. Connect your identity provider

    Single sign-on and provisioning come from the system you already run.

  3. Review with your board

    Use the architecture, data map and assessment summary in your own review.

Questions

Common questions.

Where does it run today?
Managed tenants run in AWS us-east-1. Customer-cloud deployments keep telemetry in your own account and region.
Can we hold our own keys?
In a customer-cloud deployment your own network and keys apply. Customer-managed keys on managed tenants are planned.
Is discovery separate from response?
Yes. Discovery stays observation-focused. Actions take an approved control path with its own audit trail, and servers, production and unknown machines are never isolated automatically.
Is there a packaged dedicated tenant?
A dedicated managed tenant and an air-gapped package are scoped with you as custom work today. Packaged versions of both are planned.
What do we get for procurement?
The architecture, the data processing addendum, a data map, the security assessment summary and operating policies.
Which sign-in controls are included?
Single sign-on with SAML or OIDC, SCIM provisioning, multi-factor sign-in and role mapping.
What you need
  • Your identity provider for sign-in and provisioning.
  • A decision on the isolation model, scoped with you.
For your technical team

The isolation models in detail, the observe and act trust paths, and change, support and evidence terms are in the technical pack, shared with your team under NDA.

Request the demo and technical pack
Get started

See the AI on your fleet in about a week.

Run the sensor across your estate and receive an AI risk report and an AI Bill of Materials. The assessment is free and carries no commitment.

Request a free assessment → Book a 30-minute call