Request required
Commercial terms after verification
Runtime Governance for AI Agent OperationsGoverned Runtime for Autonomous Agent Teams
Activate the project. Then let the agents run.
Relayon gives high-autonomy agent teams one governed project runtime: activate once, then let agents run through one stable entrypoint with scoped access, budget gates, fallback, pause controls, and trace-linked evidence.
Software only. No stored funds, wallet balances, remittance, crypto services, or card services.
Relayon provides software infrastructure for governed AI agent operations.
Software access
No stored funds or wallet balanceTell us the team, workload, billing country, and target plan so review can start.
After submission, use the status page to track whether the request was received and queued.
Use Google or email, verify ownership, then keep project access tied to one identity.
After approval, Relayon activates the project runtime and shares the connection path.
Teams do not lack model access. They lack a safe runtime for agents.
Once agents move from occasional model calls to continuous execution, teams hit key sprawl, fragile fallback chains, budget overruns, unstable upstreams, manual recovery, weak pause controls, and poor execution evidence.


- ops.overview -> risk board and handoff live
- ops.supply -> provider posture and switch queue live
- ops.billing_activation -> review + retry closure live
- ops.settings -> approval-gated high-risk changes live
Put spend controls in place before agent traffic turns into operational debt.
Keep keys, agents, and runs inside one visible control surface.
Handle provider instability without operator babysitting.
See what failed and stop only the affected workload.
Activate the project, then run agents through one controlled boundary.
Relayon closes the loop from subscription activation to machine-usable execution: scoped entitlement, machine credentials, stable runtime entrypoint, budget gates, fallback, pause, and evidence.
Validate the runtime boundary with BYOK, or open an access-review conversation when the team needs a paid governed runtime tier.
Managed access is enabled after billing and account verification are completed for the target account.
Once verified, the project moves from BYOK-only posture into governed runtime access with policy, routing, fallback, pause, and support coverage.


The internal surface is already live, not just promised.
What you buy on the public site now matches the protected control plane already running behind Relayon.
Blocked projects, missing default keys, and handoff notes start in one board instead of scattered tools.
Move from affected entity into projects, keys, and recent orders without leaving the operator loop.
Keep billing posture and project linkage visible before commercial drift turns into support work.
Repair machine entrypoints and default keys before teams stall on access problems.
Internal operator login is required for direct access.
High-value operator work should look like one system, not many tools.
Read provider posture, disable reasons, and the switch queue in one view.
Keep billing status, activation retries, and operator closure inside one support loop.
Trace request failure reasons, action tickets, and actor-linked audit history without raw logs.
Push high-risk policy changes through an explicit approval path before anything executes.

Built first for teams already running agents continuously.
Solo builder
Needs a fast BYOK proving ground before involving a team.
Small team
Wants one shared runtime boundary before agent usage gets messy.
Production team
Needs stronger limits, more projects, and a cleaner managed-access path.
Enterprise buyer
Needs procurement, security review, and custom commercial handling.
Project-scoped runtime control
Give teams one runtime boundary for many keys, agents, and runs before usage turns into operational debt.
Trustable activation path
Managed access follows billing and account verification, so activation stays legible to finance, ops, and procurement.
Lower operator burden
Reduce key sprawl, manual recovery, and ad hoc fallback notes without hiding what the team is actually running.
Front-side packaging is runtime capacity, not cheap quota resale.
Public prices describe governed runtime tiers: paid project access, active-run capacity bands, included budget/fallback/pause controls, and digital activation after review. Currency: USD. Taxes may apply.
Public prices describe software runtime tiers, not prepaid quota, stored funds, or crypto services.
Currency: USD. Taxes may apply.
Model-provider costs are not included unless separately agreed during managed-access review.
Free plans are BYOK only; customers pay provider costs directly.
Managed access is enabled only after billing and account verification are completed.
Relayon is software infrastructure, not a bank, wallet, money transmitter, investment service, crypto service, or card issuer.
Developer Runtime
For solo builders validating a project runtime boundary
$0
Starter Runtime
For small teams activating their first governed project runtime
$49/mo
Team Runtime
For teams already running agents continuously
$149/mo
Scale Runtime
For production teams with multiple workflows and higher active-run demand
$399/mo
Enterprise Runtime
For larger organizations with custom runtime limits and support
Custom
Keep company identity, billing posture, and review contacts easy to verify.
Procurement, payment review, and finance teams move faster when legal identity, billing details, and contact routes stay visible.

Answer the buying questions before procurement and payment review stall.
How should I read the runtime tiers?
Public prices describe governed runtime capacity for paid projects, not prepaid quota, stored value, or cheap access resale. Commercial terms are finalized during billing and account review.
What does billing verification mean?
Managed access is enabled only after billing and account verification are completed for the account that will operate the project.
Can I start with my own provider key?
Yes. The free Developer plan is BYOK-only by design, so teams can validate the runtime boundary before moving into managed access.
Is Relayon a financial service?
No. Relayon is software infrastructure for project-scoped AI access, managed routing, and operator controls, not a bank, wallet, money transmitter, investment service, crypto service, or card issuer.
Start with an activated project boundary, then let agents run.
Create an account for BYOK validation, or request managed access when the team needs a governed runtime tier.