Get a Demo
Get a Demo
Enterprise Grade Security
Complete data sovereignty.
Zero data egress.
Alterion's platform was architected to run inside your infrastructure. Your cloud, your data center, fully air-gapped. Your data stays yours, governed by your rules and policies. Nothing crosses your perimeter.
Architecture
Security is the first priority.
A control plane that watches every agent action is the most sensitive system in an enterprise's estate. So Alterion never routes that data to external destinations.
Runs in the enterprise environment
Self-hosted in your VPC, your data center, on-prem or fully air-gapped, with zero data egress. Alterion is deployed as infrastructure you own and operate. We have no production access to it and no copy of what flows through it.
Air-gapped by design
Every detection layer runs locally: rules, transformer classifiers, and LLM analysis. Alterion operates with zero outbound network egress, validated for classified and fully disconnected networks.
Training stays in the enterprise estate
Our specialized small language models run inside your infrastructure and learn your environment over time. Nothing reaches an external provider or returns to Alterion for model training.
Least privilege, fully audited
SAML SSO and SCIM, role-based access down to the Boundary, scoped API credentials, IP allow-listing, and an append-only audit log of every policy change and every operator action.
Enterprise frameworks, enforced
Govern your AI workloads against the frameworks you answer to. SOC 2, ISO 42001, NIST AI RMF, the EU AI Act, or your own policy becomes runtime controls that block violations before they execute.
Independently validated
Our deployment model, our platform, and our business are built and independently assessed against industry recognized standards, with our customers' requirements in mind. Reports available.
Deployment
Three postures. One control plane.
Pick the boundary your security team is comfortable defending. The product is identical in each.
Customer VPC
Deployed into your cloud account on AWS, Azure, or Google Cloud via Terraform. You hold the keys and the network.
- Your KMS, your keys
- Private-link only
- Telemetry opt-in
On-premises
Runs on your own Kubernetes in your data center. No cloud dependency, no managed service in the path.
- Bring-your-own registry
- Local model serving
- No phone-home
Air-gapped
Fully disconnected installs for regulated, classified, and sovereign environments. Updates ship as signed offline bundles.
- Zero egress, enforced
- Signed offline updates
- Offline license
Common questions
What security teams ask us first.
In a customer-hosted deployment, Alterion the company sees nothing. The control plane inspects agent traffic inside the customer environment: prompts, tool calls, responses, and the spans between them. Every artifact it produces stays in customer-owned storage.
Optional product telemetry is off by default, is limited to aggregate health metrics with no payload content, and can be disabled permanently at install time.
Yes. Air-gapped installs are a first-class deployment model, not an exception path. Detection runs on locally served models, policy packs are imported as signed bundles, and licensing is validated offline. Outbound egress is blocked and verified at deploy time.
The customer's own deployment does, and nothing else. Our intelligence layer is built as a network of specialized small language models that reason together and draw on persistent enterprise memory, so the system learns the environment over time. That is the product working as designed. A control plane that cannot learn the baseline cannot tell normal from anomalous.
Sovereignty is part of that architecture, not a setting layered on top. The models, the memory, and the enterprise context all stay inside the security boundary they exist to protect. Nothing is returned to Alterion, pooled across customers, or used to improve what we ship.
Binding in our Enterprise Terms: no customer input, output, or captured span is ever used to train, fine-tune, or evaluate any third-party model or any model Alterion distributes out of the box.
Access is role-based and scoped to a Boundary, so a team only sees the agents and sessions inside its own scope. Authentication is via the customer IdP over SAML with SCIM provisioning. Every privileged action writes to an append-only audit log that can be streamed to a SIEM.
TLS 1.2+ in transit and AES-256 at rest, with envelope encryption keyed by the customer's own KMS. Retention is customer-configured per Boundary, defaults to 90 days, and supports immediate hard deletion on request.
No. There are no SDKs to embed, no code changes, and no agent rewrites. Alterion sits between agents and enterprise infrastructure at the network layer, which is also why it catches shadow AI that was never registered.
Lower runtime risk.
Govern without friction.
Run at agent speed.
See the full control set, request current reports, or walk the architecture with our team.
