Enterprise

Scale Octelium to meet your organization's needs

Whether you're a startup, a service provider, or a global enterprise, we can help you run Octelium at scale with a centralized web console, real-time visibility, compliance-ready features, and a commercial license.

Enterprise package09
  • Centralized web-based control dashboard
  • Authentication and Audit Logs
  • OpenTelemetry integration with SIEM providers
  • User and Group provisioning via SCIM 2.0
  • Just-in-Time access with reviews and expiry
  • Encrypted Secret management
  • Automatic public DNS and TLS certificates
  • Multi-region Clusters and managed upgrades
  • Premium support and commercial licensing
The console

Centralized web-based control dashboard

A unified web console for Cluster administrators to manage all the Cluster resources at scale and have a real-time visibility.

console.acme.com
Services
Every resource the Cluster fronts, whatever protocol it speaks
9 of 148

Services

Every resource the Cluster fronts, whatever protocol it speaks

  • api.prod, mode HTTP, upstream 10.0.4.11:8080, healthy.
  • bastion.infra, mode SSH, upstream 10.0.2.4:22, healthy.
  • prod-k8s.infra, mode KUBERNETES, upstream kube-api:6443, healthy.
  • analytics.data, mode POSTGRES, upstream pg-prod.rds:5432, healthy.
  • tools.ai, mode MCP, upstream managed container, healthy.
  • openai.ai, mode LLM, upstream api.openai.com, healthy.
  • reports.data, mode MYSQL, upstream mysql-ro.rds:3306, healthy.
  • grafana.prod, mode HTTP, upstream managed container, healthy.
  • resolver.infra, mode DNS, upstream 10.0.0.2:53, healthy.

Policy Tester

Ask whether a request would be authorized, before anyone makes it

  • Downstream: User jane@acme.com, groups sre and oncall, CLIENT session at AAL2 on macOS.
  • Upstream: Service prod-k8s.infra in KUBERNETES mode, governed by the k8s-prod and baseline Policies.
  • verb=list resource=pods namespace=production is authorized by Policy k8s-prod, rule allow-read-sre.
  • verb=delete resource=pods namespace=production is not authorized, denied by Policy k8s-prod, rule deny-destructive.

Access Requests

Time-bound elevation with the approvals your process requires

  • noah@acme.com requests analytics.data for 2 hours, high urgency, reason incident-4821.
  • Step 1: any of 3 reviewers in Group sre-leads. Approved by dana@acme.com.
  • Step 2: all of 2 reviewers in Group security. Approved by omar@acme.com.
  • Access granted until 16:20, then removed automatically.

Cluster Upgrades

Version the Cluster from the console and let it roll itself out

  • Core package v0.34.2 upgrading to v0.35.0.
  • Enterprise package v0.34.2 upgrading to v0.35.0.
  • Cordium package v0.35.0 is current.
  • The upgrade rolls out across every Region with no access interruption.

Access Logs

Every request, with the identity, the device and the decision behind it

  • 14:02:11 ALLOW jane@acme.com to prod-k8s: verb=list resource=pods ns=production.
  • 14:02:09 ALLOW linus@acme.com to analytics: select id, email from users limit 50.
  • 14:02:07 DENY agent-07 to tools: tools/call name=transfer_funds.
  • 14:02:04 ALLOW ci-runner to api: POST /v1/deployments.
  • 14:02:01 ALLOW noah@acme.com to bastion: session recorded, upstream user=deploy.
  • 14:01:58 ALLOW agent-07 to openai: model=gpt-5-mini tokens=1284.

Metrics

Cluster and per-Service metrics, queryable and exportable

  • 1,284 requests per second, 8.4 ms p99 latency, 37 requests denied today.
  • Top Services by request rate: analytics.data at 412 per second, api.prod at 388, prod-k8s.infra at 214.
  • Metrics and logs are exported to Datadog, Splunk and Grafana over OpenTelemetry.
Visibility

Authentication and Audit Logs

Monitor authentication in real time. Audit every resource change in the Cluster. Replay SSH sessions

  • Dedicated structured Authentication logs for every authentication event, carrying the identity provider, the credential, the authenticator and the assurance level behind it.
  • Audit logs recording every resource modification in the Cluster, with the API method that made it and the User, Session and Device behind it.
  • Replay SSH sessions in the web console.
How visibility and logs work
console.acme.com
Authentication logs
Every authentication event, with the credential behind it.
Live

Authentication logs

Every authentication event, with the credential behind it.

  • jane.doe: Identity Provider, AAL2, okta-prod · jane.doe@acme.com, from 198.51.100.24, 12s ago.
  • marco.silva: Authenticator, AAL3, FIDO2 · hardware security key, from 203.0.113.51, 48s ago.
  • amara.osei: Identity Provider, AAL2, entra-id · amara.osei@acme.com, from 192.0.2.77, 2m ago.
  • ling.wei: Authenticator, AAL2, TOTP · authenticator app, from 198.51.100.9, 4m ago.
  • ci-deployer: Credential, AAL1, deploy-token · token 01J8T4KQ, from 203.0.113.9, 6m ago.
  • sonia.reyes: Identity Provider, AAL2, keycloak · sonia.reyes@acme.com, from 192.0.2.14, 9m ago.

Audit logs

Every change made to the Cluster, and who made it.

  • jane.doe called PolicyService/UpdatePolicy on the Policy deny-destructive, 20s ago.
  • marco.silva called ServiceService/UpdateService on the Service bastion, 3m ago.
  • amara.osei called UserService/CreateUser on the User contractor-42, 11m ago.
  • jane.doe called DeviceService/DeleteDevice on the Device laptop-mx-9, 24m ago.
  • ci-deployer called ServiceService/CreateService on the Service analytics, 38m ago.
  • marco.silva called ConfigService/UpdateConfig on the ClusterConfig cluster-config, 52m ago.

SSH session recording

Replayed beside the access log entry that authorized it.

  • jane.doe@bastion:~$ systemctl status payments
  • ● payments.service - Payments API
  • Active: active (running) since 14:02:11
  • jane.doe@bastion:~$ journalctl -u payments -n2
  • 14:31:02 payments[912]: upstream timeout
  • 14:31:04 payments[912]: recovered, 2 tries
  • jane.doe@bastion:~$ ss -tnp | head -3
  • State Recv-Q Local Address:Port
  • ESTAB 0 10.0.4.9:22
  • ESTAB 0 10.0.4.9:5432
  • jane.doe@bastion:~$ exit
  • logout
Telemetry

OpenTelemetry integration with SIEM providers

Scalable OpenTelemetry collectors that concurrently export Access, Authentication, and Audit Logs plus metrics to Datadog, Splunk, Grafana, Elastic, and others in real time.

  • Integrate your SIEM providers such as Datadog, Splunk, Logz.io, Elastic, Grafana, and many others, and export logs and metrics in real time.
  • Horizontally scalable collectors with multiple pipelines to different providers.

The Cluster runs OpenTelemetry collectors that export access logs, authentication logs, audit logs, component logs, metrics in real time.

  • Datadog: Logs, metrics
  • Splunk: Logs
  • Elastic: Logs
  • Grafana: Metrics
  • ClickHouse: Logs
  • Kafka: Logs, metrics
  • InfluxDB
  • Prometheus
  • Azure Monitor
  • Azure Data Explorer
  • Logz.io
  • Any OTLP endpoint
Access

Just-in-Time access

Seamless JIT access to Octelium Cluster Services with self-service access requests, reviews, and time-bound approvals, all from a dedicated access web portal.

  • Catalogs of Services or Namespaces that can be requested directly by Users.
  • Policies whose rule decide whether a request is denied, approved automatically or sent for review.
  • Multi-step reviews with time-bound approvals.
portal.acme.com
New request
Access to a Service or a whole Catalog, with a reason and a duration.
Portal

New request

Access to a Service or a whole Catalog, with a reason and a duration.

  • jane.doe requests access for herself.
  • Catalogs available: prod-databases (4 Services), payments-prod (7 Services), k8s-prod (3 Services).
  • Urgency High, duration 2 hours.
  • Justification: Investigating elevated 5xx on payments-api. INC-2841.

Review queue

Reviewers named per step, each with its own requirement and timeout.

  • prod-databases requested by jane.doe, urgency High, duration 2 hours.
  • Step 1: sre-leads, 2 approvals required, 30m timeout, reviewers marco.silva and amara.osei.
  • Step 2: security, Any approval, 1h timeout, reviewers ling.wei.
  • Access granted until 16:20 UTC, then removed automatically.
Identity

User and Group provisioning via SCIM 2.0

Synchronize Users and Groups from one or more directory providers, such as Microsoft Entra ID and Okta, simultaneously.

  • Users and Groups pushed to the Cluster over SCIM 2.0 by Microsoft Entra ID, Okta or any other SCIM 2.0 provider.
  • Google Workspace and Keycloak directories polled on an interval you set, alongside the OIDC and SAML 2.0 single sign-on every Cluster already has.
How Policies read identity
Directory providers
More than one directory, synchronized into the same Cluster.
Synchronized

Directory providers

More than one directory, synchronized into the same Cluster.

  • Microsoft Entra ID: SCIM 2.0.
  • Okta: SCIM 2.0.
  • Auth0: SCIM 2.0.
  • JumpCloud: SCIM 2.0.
  • Google Workspace: Polled.
  • Keycloak: Polled.
  • User amara.osei from entra-id.
  • Group sre-leads from okta-prod.
  • User marco.silva from workspace.
  • Group security from entra-id.
  • User ling.wei from keycloak.
  • User dan.kovac from workspace.
  • User contractor-42 from okta-prod.
Secrets

Encrypted Secret management

Automatic, scalable Secret encryption at rest with integrations for major cloud vault and KMS providers.

  • A dedicated Secret manager for Secret encryption at rest with integrations for AWS KMS, Google Cloud KMS, Azure Key Vault, and HashiCorp Vault.
How Secrets work
Secret encryption at rest
Automatic and scalable, with the provider you already run.
Automatic

Secret encryption at rest

Automatic and scalable, with the provider you already run.

  • AWS KMS.
  • Google Cloud KMS.
  • Azure Key Vault.
  • HashiCorp Vault.
  • Kubernetes.
  • Additional providers on demand.
  • Secret db-prod-password is encrypted at rest.
  • Secret github-app-key is encrypted at rest.
  • Secret datadog-api-key is encrypted at rest.
  • Secret smtp-password is encrypted at rest.
Networking

Automatic public DNS and TLS certificates

Automatic public DNS management and automatic issuance and rotation of TLS certificates via Let's Encrypt.

  • Automatic public DNS management for Cloudflare, AWS Route 53, Google Cloud DNS, Azure DNS, DigitalOcean, Linode and OVH.
  • Automatic TLS Certificate issuance and rotation via Let's Encrypt DNS-01 ACME challenge.
Public DNS and TLS certificates
Issued and rotated by the Cluster, not by a runbook.
Automatic

Public DNS and TLS certificates

Issued and rotated by the Cluster, not by a runbook.

  • Service api is published at api.acme.com, certificate issued, renews in 62 days.
  • Service grafana is published at grafana.acme.com, certificate issued, renews in 62 days.
  • Service portal is published at portal.acme.com, certificate issued, renews in 71 days.
  • Service docs is published at docs.acme.com, certificate issued, renews in 88 days.
  • Cloudflare.
  • AWS Route 53.
  • Google Cloud DNS.
  • Azure DNS.
  • DigitalOcean.
  • Linode.
  • OVH.
  • Let's Encrypt.
What you get

Enterprise features and premium support

The sections above cover what most organizations evaluate on. This is the rest of it, for the reader who is checking a specific box.

Management

06
  • Centralized web-based control dashboard

    A unified web console for Cluster administrators to manage and monitor the Cluster's resources in real-time at scale.

  • Policy builder

    UI-based policy builder to easily create complex CEL rules from a catalogue of pre-defined conditions.

  • Policy tester

    Test your policies in a safe environment on a specific User, Session, Service and Namespace before deploying them.

  • MCP and LLM playgrounds

    Send a request to an MCP or LLM Service from inside the console and watch how the Policies that govern it treat that exact call.

  • Managed upgrades

    Seamlessly upgrade the Cluster packages from within the web console.

  • Multi-Region Clusters

    Scalable Octelium Clusters spanning multiple Kubernetes clusters across regions and clouds.

Visibility

06
  • Authentication and Audit Logs

    Dedicated structured Authentication logs for every authentication event and Audit logs recording every resource modification in the Cluster.

  • OpenTelemetry integration with SIEM providers

    Scalable OpenTelemetry collectors that export logs and metrics to major SIEM providers like Datadog, Splunk, Grafana, Elastic, and others in real time.

  • SSH session recording

    Recorded SSH sessions, replayable in the console beside the Access Log entry that authorized them.

  • Metrics and dashboards

    Cluster and per-Service metrics queried in the console, broken down by User, Session, Service and Policy, with summaries and top-N views.

  • Log storage and query

    Logs and metrics are stored and indexed inside the Cluster, so the console can list, filter and aggregate them without a second system.

  • Real-time visibility

    Live Sessions, Devices and Services across every Region in one view, so the state of the whole Cluster is visible without querying it resource by resource.

Identity and devices

03
  • User and Group provisioning via SCIM 2.0

    Synchronize Users and Groups from one or more directory providers (Microsoft Entra ID, Okta, and others) simultaneously.

  • Directory synchronization

    Google Workspace and Keycloak directories polled on an interval you set, alongside the OIDC and SAML 2.0 single sign-on every Cluster already has.

  • Device posture integration with EDR providers

    Soon

    Device posture management integrated with CrowdStrike and additional EDR vendors on demand.

Just-in-Time access

04
  • Access Catalogs

    The set of Services and Namespaces that can be requested, so a request is a selection from a list rather than a description of what somebody wants.

  • Self-service access requests

    Requests made from the access portal with a reason, an urgency and a duration, evaluated by rules that deny, auto-approve or send them for review.

  • Multi-step reviews

    Reviewers named individually or by Group, per step, with any-of, all-of or a required count, a timeout, and a defined outcome when the timeout is reached.

  • Time-bound approvals

    An approved request carries both the Policies it grants and a maximum duration, so elevation is scoped as well as temporary and it ends without anyone remembering to revoke it.

Infrastructure

04
  • Encrypted Secret management

    Automatic, scalable Secret encryption at rest with integrations for AWS KMS, Google Cloud KMS, Azure Key Vault, HashiCorp Vault, and additional providers on demand.

  • Automatic public DNS for Services

    Automatic public DNS management for BeyondCorp-exposed Services via Cloudflare, AWS Route 53, and custom providers on demand.

  • Automatic TLS certificate management

    Automatic issuance and rotation of TLS certificates for all Services via Let's Encrypt and other public CAs on demand.

  • Component scaling

    Replica counts for the horizontally scalable components set as configuration, so capacity is part of the Cluster definition rather than a manual operation.

Support and licensing

02
  • Premium support

    Direct premium support with a dedicated private Slack channel. Help installing and running Octelium Clusters at scale on cloud-based or on-prem Kubernetes, meeting compliance regulations and standards. Influence the roadmap for upcoming features.

  • Commercial alternative license

    Octelium Cluster components are dual licensed under a copyleft license and a commercial license. We offer an alternative commercial license for businesses that need to use Octelium without the copyleft obligations.

All of it runs inside the same self-hosted Cluster, on your own Kubernetes, in your cloud or on-prem.

Let's talk

Ready to bring zero trust to your organization?

Tell us about your infrastructure and compliance requirements. We'll help you scope a deployment that fits.

  • Free to use, forever, for personal and evaluation use.
  • Nothing about your existing Cluster, Policies or identity setup changes.