Pay for output, not headcount
Your bill tracks published configs, scheduled jobs, and headless runners — the things doing the work. Add a teammate to the account without adding a line item.
Enterprise · the AI productEnterprise is a fleet
Enterprise is a fleet
you size yourself.
No per-seat tax, no “contact sales” wall. Size a cloud fleet by the work you run — configs, schedulers, and headless runners — or take the whole platform on-prem in your own infrastructure. One OpenEng account, either way. Launching Q4 2026.
Per-fleet, not per-seat On-prem · full suite Headless + self-heal Launching Q4 2026
Two ways to buy
Size a cloud fleet, or take it all on-prem.
Two ways to run Enterprise: a cloud-coordinated fleet you size yourself — configs, schedulers, headless runners, sandboxes, and seats — or the entire platform on-prem inside your own infrastructure. Launching Q4 2026; pricing announced at launch.
Launching Q4 2026
Enterprise — per-fleet, not per-seat
Two ways to run it: size a cloud-coordinated fleet — configs, schedulers, headless runners, sandboxes and seats — or take the whole platform on-prem in your own infrastructure. Pricing is announced at launch.
Launching Q4 2026
Enterprise pricing — both the custom cloud fleet and the On-Prem suite — is announced at launch (Q4 2026). This page covers the OpenEng AI product only; the engineering apps (Terminal, Kubernetes, Git, Data, Chat) are free on their own site.
Why per-fleet
Per-seat pricing taxes the wrong thing.
An agent platform's value is the work it runs unattended, not the number of humans logged in. So we price the fleet — and the humans come along for free.
Scale up without renegotiating
Need 40 more nightly jobs next quarter? Drag a slider. The fleet flexes with your roadmap instead of triggering a procurement cycle.
Transparent by design
Pricing is per-fleet and broken out line by line — no hidden seat minimums, no opaque “platform fee.” The full breakdown is published at launch.
The ceiling
One account. A fleet up to 100 / 100 / 1,000.
A single OpenEng account governs the whole estate: up to a hundred published configs, a hundred scheduled jobs, and a thousand headless runners — all resolving the same versioned configs, all under one identity.
100Published configs
100Scheduled jobs
1,000Headless runners
1OpenEng account
Within the fleet, there is no per-resource cap on what you compose: any number of configs, schedulers, and headless runs can be authored, versioned, and pulled by every machine you sign in to.
Identity & trust
One OpenEng account. The same guarantees, at fleet scale.
Sign in once and every machine — laptop, build agent, or scheduled box — resolves your published configs by name. The privacy model that protects a single developer protects the whole fleet, unchanged.
one identity
Author once, run everywhere you sign in
A published config is an immutable id@version. Every machine that signs in pulls the exact same setup — no drift, no per-box configuration to keep in sync. A config is visible only to its owner unless explicitly shared, and revocation takes effect on the next pull.
On-device inference
Source never transits a third-party API unless you configure an external model.
No telemetry
The only network surface is sign-in, your config fetch, and the release check.
Sealed channel
A fresh key seals every frame, end-to-end — even on your own machine.
Placeholder secrets
Configs carry ${ENV} names only; real values resolve from the machine env.
The fleet runtime
Headless leases that heal themselves.
The work runs without a browser or a babysitter. A headless box either starts whole or refuses with a precise reason — it never limps along half-configured at 2 a.m.
Unattended run — Pro & Enterprise
OPENENG_KEY=oe_… openeng headless -c jobs.yamlleased
Headless fleet leases
Each runner takes a lease against your account and reports in. Scheduler ownership is claimed by one instance per config, so cron-validated jobs fire once across the fleet — not once per box.
self-heal
Self-healing runners
A stalled or expired lease is reaped and reclaimed; a runner that drops out is replaced on its next cycle. The fleet converges back to your declared config without manual intervention.
declared once
Schedulers in the config
Recurring work is part of your Console-published config: define it once and every machine that loads the config knows about it. Cron expressions are validated up front, before anything runs.
Governance
Humans get one session. Servers get keys.
Two auth models, on purpose: interactive sign-ins are single-session with explicit takeover, while API keys are concurrent by design — so a fleet scales without fighting your own login.
interactive
One active session per account
A second sign-in is answered with
HTTP 409 and a device-label prompt before taking over — so a forgotten or hijacked session is visible, and takeover is always explicit, never silent.servers
Concurrent, revocable API keys
API keys are multi-machine by design — run a thousand runners on one key.
OPENENG_KEY is validated per call and never written to disk; keys are stored hashed server-side and revocable without touching a single machine.auditable
Append-only headless logs
Unattended output lands in an append-only log file — a tamper-evident record of what the fleet did, on the box that did it.
integrity
Checksum-verified updates
Updates from releases.openeng.ai are checksum-verified and applied as an atomic swap with re-exec at boot — a tampered or truncated binary never runs anywhere in the fleet.
Size your fleet, then talk to us.
Tell us about your fleet — write to hello@openeng.ai and we’ll walk through headless, keys, and rollout. Paid plans and the free trial are launching q4 2026 — run the engine free on one box today.