Get a Demo
Get a Demo
<style>
/* ---------- Primary button ---------- */
.button_bg {
background-color: #a83018;
transition: background-color 0.3s cubic-bezier(0.4, 0, 0.2, 1);
}
.button:hover .button_bg,
.button:focus-visible .button_bg,
.submit-wrapper:hover .button_bg,
.submit-wrapper:focus-within .button_bg {
background-color: #d24a2f;
}
/* ---------- Secondary button ---------- */
.button_bg.secondary {
background-color: var(--neutral--900);
border: 1px solid var(--neutral--500);
transition:
background-color 0.3s cubic-bezier(0.4, 0, 0.2, 1),
border-color 0.3s cubic-bezier(0.4, 0, 0.2, 1);
}
.button:hover .button_bg.secondary,
.button:focus-visible .button_bg.secondary,
.submit-wrapper:hover .button_bg.secondary,
.submit-wrapper:focus-within .button_bg.secondary {
background-color: var(--neutral--700);
border-color: var(--neutral--300);
}
</style>[fs-list-field]:has(> *),
.tag-component {
transition: background-color 0.25s ease, border-color 0.25s ease;
}
.fs-list-active .tag-component,
.tag-component.fs-list-active {
background-color: #d24a2f;
border-color: #d24a2f;
}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.
Self-hosted in your VPC, your data center, or fully on-prem. Alterion is deployed as infrastructure you own and operate. We have no production access to it and no copy of what flows through it.
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.
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.
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.
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.
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.
Deployed into your cloud account on AWS, Azure, or Google Cloud via Terraform. You hold the keys and the network.
Runs on your own Kubernetes in your data center. No cloud dependency, no managed service in the path.
Fully disconnected installs for regulated, classified, and sovereign environments. Updates ship as signed offline bundles.
In a customer-hosted deployment, Alterion the company sees nothing. The control plane inspects agent traffic inside your environment: prompts, tool calls, responses, and the spans between them. Every artifact it produces stays in storage you own.
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.
Your 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 your environment over time. That is the product working as designed. A control plane that cannot learn your 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 your IdP over SAML with SCIM provisioning. Every privileged action writes to an append-only audit log you can stream to your SIEM.
TLS 1.2+ in transit and AES-256 at rest, with envelope encryption keyed by your 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 your agents and your infrastructure at the network layer, which is also why it catches shadow AI that nobody registered with you.