Elysium Compute Gateway (ECG)

One endpoint for AI workloads. Governed compute behind it.

Elysium Compute Gateway (ECG) connects AI applications, agents, and enterprise software to eDOS™ and your Private Compute Planes through a unified, policy-aware access layer.

Submit supported AI and compute requests through a single gateway. ECG authenticates access, applies tenant and Private Plane policy, translates requests into native eDOS™ workloads, and sends them to the Elysium Control Plane for intelligent placement across eligible compute resources.

Applications interact with the gateway. eDOS™ handles the infrastructure.

Connect once. Orchestrate everywhere.

Get API access Read the API docs Book enterprise demo

Unified AI Access

Connect AI agents, LLM applications, enterprise automation, and supported developer frameworks to a unified compute endpoint without exposing the underlying node fleet.

AI-Compatible Interfaces

Support OpenAI-compatible, Anthropic-compatible, and native Elysium compute APIs so supported applications integrate with fewer infrastructure changes.

Policy-Aware Routing

Bind workloads to Private Compute Planes, Node Pools, approved runtimes, security policies, trust requirements, and data-residency boundaries.

Smart Compute Placement

eDOS™ evaluates real-time node availability, resource pressure, runtime compatibility, trust, and policy to select the best eligible compute resources.

End-to-End Telemetry

Trace requests from gateway entry through scheduling, execution, verification, aggregation, and delivery using correlated request, trace, and job identities.

Enterprise Security

Control compute access with scoped credentials, tenant isolation, Private Plane boundaries, rate limits, workload policy, and security-aware routing.

Observability Integrations

Export approved infrastructure and AI telemetry to your existing monitoring platforms while retaining control over redaction, sampling, and external export.

Unified AI Infrastructure Access

Give AI applications a direct path to governed enterprise compute

AI teams should not need to manually submit jobs through an infrastructure dashboard every time they need compute. ECG gives applications a programmatic path into Elysium — without exposing the underlying node fleet.

AI Agent / Application
          ↓
Elysium Compute Gateway
          ↓
Policy + Identity
          ↓
eDOS™ Control Plane
          ↓
Smart Compute Placement
          ↓
Private Compute Plane
          ↓
Verified Result

ECG can support

AI agentsLLM applicationsInternal enterprise applicationsAutomation workflowsPython applicationsTypeScript and Node.js applicationsLangChain and LangGraph workflowsLlamaIndex applicationsMCP-connected toolingCustom enterprise software

OpenAI- and Anthropic-Compatible Access

Bring the applications your teams already build

ECG can expose compatible API surfaces for applications designed around common AI SDK patterns. Point a supported client to the ECG endpoint instead of building a custom job-submission workflow.

OpenAI-compatible

/v1/chat/completions
/v1/responses
/v1/embeddings
/v1/models

Anthropic-compatible

/v1/messages

Elysium Native Compute

/v1/jobs
/v1/compute

Existing AI Application
        ↓
ECG Endpoint
        ↓
Elysium Private Compute Plane

Intelligent Workload Translation

Turn application requests into orchestrated compute jobs

ECG is more than a request proxy. Supported incoming requests are translated into native eDOS™ jobs with the context required for secure workload execution. Applications request compute. eDOS™ decides how that compute is safely delivered.

Each request can be associated with

OrganizationTenantPrivate Compute PlaneRuntime PoolWorkload typeRuntime typeAI modelSecurity levelCrypto policyVerification policyPriorityScheduling policy

Private Plane Routing

Keep enterprise workloads inside the environment they belong to

Requests can be bound to a specific Private Plane so workloads are scheduled only to eligible nodes assigned to that environment. Route workloads by organization, security posture, location, runtime, and policy — not simply by available hardware.

Finance AI Agent          Research AI Agent
        ↓                         ↓
       ECG                       ECG
        ↓                         ↓
Finance Private Plane     Research Private Plane
        ↓                         ↓
Approved Finance Nodes    Research GPU Pool

Private Plane routing can enforce

Tenant isolationPlane isolationNode Pool restrictionsRuntime restrictionsGeographic policiesData residency requirementsTrust Score thresholdsSecurity policiesVerification requirements

Smart Compute Integration

Compute placement that responds to real resource conditions

ECG submits the workload. eDOS™ Smart Compute determines the best eligible execution resources — preferring idle or underutilized nodes, and selecting the best available eligible resources when the fleet is under heavy utilization. Use the best available compute without breaking enterprise policy.

The scheduler can evaluate

CPU pressureGPU pressureMemory availabilityActive task countNode availabilityNode Trust ScoreRuntime compatibilityPrivate Plane membershipNode Pool membershipThermal statePower stateUser activityNetwork quality

End-to-End Workload Visibility

Trace every compute request from gateway entry to verified result

Every ECG request can receive a correlated request and job identity. Administrators and authorized applications can follow a workload through its full lifecycle.

Gateway Request
      ↓
Authenticated
      ↓
Policy Evaluated
      ↓
Job Created
      ↓
Scheduled
      ↓
Dispatched
      ↓
Executing
      ↓
Verified
      ↓
Aggregated
      ↓
Result Delivered

Telemetry can include

Request IDTrace IDJob IDPrivate PlaneRuntime PoolRequest latencyQueue durationScheduling durationExecution durationVerification durationAggregation durationRetry countJob statusFailure reasonTime to result

Enterprise Authentication and Access Control

A controlled entry point into Elysium compute

Every request enters through an authenticated, policy-aware compute boundary.

Access methods

• Scoped API keys
• OAuth / OIDC
• Enterprise identity
• Service principals
• Workload identity
• Future mTLS client authentication

Scoped actions

jobs:create
jobs:read
jobs:cancel
compute:run
models:list
embeddings:create

Key bindings

• Tenant
• Private Compute Plane
• Runtime Pool
• Approved workload types
• Rate limits
• Expiration policies

Security and Privacy by Default

Observe the infrastructure without turning customer workloads into monitoring data

ECG provides infrastructure access without unnecessarily exposing customer workload content through operational telemetry. Elysium can monitor request and job metadata while excluding customer content by default.

Excluded from telemetry by default

• Prompt content
• Response content
• Workload payloads
• Customer files
• API keys
• Enrollment tokens
• Private cryptographic material
• Decrypted workload content

Customer-controlled observability

Administrators can define telemetry export and redaction policies through the Enterprise Console.

Telemetry categoriesMetadata-only modeField redactionSamplingExternal exportLocal-only observability

Bring Your Existing Observability Stack

Monitor Elysium where your infrastructure and AI teams already work

ECG telemetry can integrate with the Elysium Integrations Center. Route approved telemetry into the platforms your organization already uses, or export via standards-based OpenTelemetry to your own pipelines.

FiddlerDatadogSplunkGrafanaAzure MonitorOpenTelemetry

Supported and planned connectors are shown for reference; availability depends on the connectors shipped in your deployment.

Sovereign Compute Gateway

Keep the gateway inside the environment you control

For a sovereign deployment, the gateway can remain inside the customer's controlled environment. External compute bursting and external telemetry export can remain disabled. Customer-controlled certificates and local observability can be used, and the organization maintains policy control over where workloads are eligible to execute.

Government / Enterprise AI
           ↓
     Internal ECG
           ↓
  Private eDOS™ Control Plane
           ↓
 Sovereign Compute Plane
           ↓
 Organization-Owned Devices

Sovereign defaults

• External compute bursting disabled
• External telemetry export disabled
• Customer-controlled certificates
• Local observability only
• Organization-owned devices as eligible compute

Connect once. Govern every request. Orchestrate compute anywhere you're authorized to run it.

Get API access Book enterprise demo