Orbital for Enterprise

Coordinate specialized agents. Control how they run.

Orbital coordinates agent tasks with signed policies, scoped permissions, and budget controls. Inspect execution through a tamper-evident audit trail.

Book a call
  • Signed policies
  • Scoped permissions
  • Tamper-evident audit trail
  • SOC 2 Type II scoped, auditor engaged

Scope your first workflow

Describe one workflow. Include the systems it touches and the decisions your team must approve.

We'll reply by email about your workflow. By submitting, you agree to our Terms and Privacy Policy.

Platform pillars

Bring coordination and controls into the same workflow.

Orbital unifies agent execution, automates handoffs, enforces governance, and optimizes costs.

01Orchestrate

Multi-agent orchestrationOne orchestrator, every agent runtime

Turn a goal into assigned agent tasks with one orchestrator.

  • The orchestrator breaks the goal into assigned tasks.
  • Task-to-goal links keep delegated work tied to the requested outcome.
02Govern

Policy & governanceAgents act, people stay in charge

Bound agent authority with signed policies and scoped permissions.

  • Signed policies define permitted actions; scoped permissions restrict access.
  • A tamper-evident audit trail records execution for inspection.
03Optimize

Token optimizationSame results, a smaller bill

Manage inference spending through model routing and budget controls.

  • Model routing directs requests to configured models.
  • Budget controls set spending boundaries for configured workloads.

Enterprise-grade from the first agent.

Review access boundaries, execution records, and support terms with your teams.

Talk to our teamSecurity overview

Audit logging

A tamper-evident audit trail records agent execution for review.

Permissions and control

SSO, SCIM, and owner, admin, and member roles, plus per-session credential grants and approval gates for consequential actions.

Usage monitoring

See cost, runtime, and output by agent, team, and goal, and set spend limits so budgets are enforced, not just reported.

SOC 2 Type IIIn progress

Our SOC 2 Type II audit is in progress.

Data protection

Orbital uses TLS in transit and encryption at rest for data in its managed storage.

Enterprise support and SLAs

Set response targets and escalation responsibilities in your enterprise agreement.

Deployment

Choose where Orbital runs.

Compare hosting, network access, and update responsibility across the three options.

Cloud

Available now
Control plane
Hosted by Orbital
Network
Connects to Orbital Cloud
Updates
Managed by Orbital

Self-hosted

Enterprise plan
Control plane
Your VPC or data center
Network
Egress set by your team
Updates
You apply versioned releases

Air-gapped

On request
Control plane
Your isolated network
Network
No outbound access
Updates
Offline release bundles
Confirm model, connector, and log data flows with our team
Onboarding

Start with one workflow and clear acceptance checks.

Bring your team into the pilot. Agree on the output, access boundaries, and spending limits before the first run.

Step 1

Define the work

  • Choose one workflow, such as a billing-system change.
  • Name the reviewer and define the required change package.
  • List the systems, data, and approvals the workflow needs.

Step 2

Set the boundaries

  • Define signed policies, permission scopes, and human review points.
  • Choose the deployment and inspect its data flows.
  • Set model routes, budget limits, and acceptance checks.

Step 3

Run, inspect, and decide

  • Review the change package against the agreed requirements.
  • Inspect an allowed action, a denied action, and the audit evidence.
  • Test the budget limit and decide whether to expand.
Questions

Frequently asked

How is agent access controlled?
Signed policies define permitted actions, and scoped permissions restrict access. Credential storage, revocation, and enforcement coverage need confirmation for your selected connectors. Test an allowed request and a denied request before expanding access.
What happens when a run reaches its budget?
Orbital provides model routing and budget controls. The exact limit-trigger behavior needs confirmation for your configuration, including concurrent runs and your own provider keys. Include a limit-triggered run in the pilot; do not assume an immediate hard stop.
Does self-hosting keep all data inside our network?
Self-hosting places the control plane in your infrastructure. That placement alone does not establish zero egress. Review model requests, connector traffic, logs, and updates. Air-gapped deployment is available on request; confirm its network boundary and supported components with the team.
Why evaluate Orbital alongside our internal agent framework?
Orbital combines multi-agent orchestration with signed policies, scoped permissions, an audit trail, and model routing with budget controls. Compare the same workflow in both environments. Identify who maintains coordination, permission enforcement, execution records, and spending controls.
What is Orbital's SOC 2 status?
A SOC 2 Type II examination has been scoped with an engaged auditor. The observation window has not yet begun, and no attestation report exists today. Ask for the current status and which control documents are available for your security review.
What should we inspect before approving a pilot?
Start with a workflow run, its permission scopes, policy decisions, audit evidence, and spending record. Request the data-flow map for the proposed deployment.
Next steps

Get AI coworkers into production

Bring the workflow, required systems, and security constraints. Work with our FDE team to define the pilot scope and acceptance checks.

Talk to our FDE teamExplore Orbital