Deterministic steps
core/contracts/flow.py
Declare the workflow sequence so an agent cannot invent a step that was never approved.
Rylvo for AI agencies
Bring the next client. Build their agent in Rylvo.
One Pro workspace gives your agency room for up to 25 client agents, 50 deployment channels, and the full control stack — without rebuilding the operating layer for every client. Bring your own model key; Rylvo adds zero markup.
74 seconds
One operating stack. Every client agent.
See the agency workflow: brief, reviewable build plan, approval, client-facing deployment, trace evidence, guardrail testing, and usage by end user.
25
bots
Separate client agents in one Pro workspace.
50
deployment channels
Room to launch across client-facing surfaces.
500K
backend bot calls / month
Included Pro platform capacity before overage.
$0
Rylvo token markup
Your provider key, your provider bill.
The agency loop
Reuse the operating layer. Keep the client work distinct.
Each client still gets their own configuration and evidence. Your agency stops reassembling the same builder, channel setup, safety controls, test harness, and observability stack every time.
- 01
Turn the client brief into a reviewable plan
Describe the outcome in Architect, inspect the proposed resources and actions, then approve only what should be created.
- 02
Configure the client-facing experience
Give each bot its own prompts, knowledge, guardrails, widget identity, accent, greeting, and verified deployment channel.
- 03
Prove the risky paths before launch
Run test cases and red-team scenarios, restrict tools by step, and require human approval where the workflow can affect a customer.
- 04
Operate from evidence, not screenshots
Replay each recorded turn with model, tokens, estimated cost, latency, guardrail outcomes, and end-user usage in one place.
Live control proof
Try to push an invalid action past the boundary.
This console uses the same enforcement path that protects a production turn. Send one of the hostile instructions, then define a rule for a tool from your own client workflow and see whether it holds.
Adversary console
- 1 Attack
- 2 Your rule
- 3 Done
You are the hostile caller. Pick something a real customer might send to a client-facing agent, and watch the same proposed tool call resolve in two lanes.
Forbidden action
The caller talks the agent into an action the policy forbids.
Missing field
The caller pressures the agent to act without required data.
Out of order
The caller pushes the agent to skip a step in the workflow.
Pick a message above to dispatch it through both lanes.
Production controls
The agent proposes. The runtime decides.
Prompt instructions are still text inside the model's context. Rylvo puts critical policy between a proposed action and the tool, then records the decision for replay and review.
Per-step tool restrictions
core/contracts/flow.py → tools_allowed()
Declare which tools are legal at each step and reject a call made outside its allowed boundary.
Approvals
apps/api/routes/approvals.py
Pause nominated actions for a real operator decision before execution continues.
Human takeover
apps/web/src/domains/mission-control/types.ts
Let an operator take over a live conversation while the agent is silenced.
Trace replay
apps/api/routes/observability.py
Reconstruct the input, decisions, tool calls, guardrail outcomes, cost, and latency for every recorded turn.
Version rollback
apps/api/routes/releases.py
Return a released configuration to a prior version and record the rollback in the audit log.
Pricing
A subscription for the platform. Your key for the intelligence.
There is no agency deposit or paid launch gate. Start free, use Pro as a solo operator, or choose Team when more people need access to the workspace.
Pro
For a solo agency operator running multiple client agents.
$80first month
then $100/month · $80/month billed annually
- Up to 25 bots
- 1 workspace member included
- 50 deployment channels
- BYOK with zero model-token markup
- Architect, tests, guardrails, traces, and Mission Control
Team
For an agency team sharing operations, administration, and support.
$350first month
then $400/month · $320/month billed annually
- Up to 25 bots
- 3 workspace members included
- 50 deployment channels
- BYOK with zero model-token markup
- Architect, tests, guardrails, traces, and Mission Control
Fit
Built for agencies that want to operate the agents they sell.
Rylvo is the workspace and runtime for the client agents you build in Rylvo. It is not a monitoring overlay for unrelated bots hosted entirely somewhere else.
Build once, adapt per client
Reuse templates, skills, integrations, test patterns, and operating practices while keeping each client agent's behavior explicit.
Put controls outside the prompt
Use tool restrictions, approvals, takeover, tests, and rollback where a client workflow can affect customers, records, or money.
Show clients what happened
Trace individual turns and roll usage up by end user so reviews start with evidence instead of reconstructed anecdotes.
Questions
The commercial model, plainly.
Is there an application fee, setup fee, or deposit?
No. Rylvo is subscription software. Start on Free, then move to Pro or Team when you need more capacity. There is no paid sprint, application gate, or deposit attached to the agency plan.
Which plan should an agency use?
Pro is the strongest fit for a solo operator: up to 25 bots and the full product suite in one workspace. Team is for agencies that need multiple operators, shared administration, roles, and support. The live pricing page is the source of truth for current plan limits and prices.
Does Rylvo charge for model tokens?
No. Connect your own provider key and pay that provider directly. Bot chat and Rylvo's AI features use your key, and Rylvo adds zero markup to model usage.
Can each client have its own agent and channel?
Yes. Each client can have a separate bot configuration, prompts, knowledge sources, guardrails, deployment channels, traces, and usage records inside the workspace limits of your plan.
Is Rylvo fully white-label?
Rylvo lets you configure the customer-facing widget identity, greeting, and accent for a client deployment. It is not presented as a complete reseller or fully rebrandable admin suite.
Does Rylvo control bots running on other platforms?
No. Rylvo cannot automatically govern an unrelated bot running entirely on another platform. The workflow must run through Rylvo for its runtime controls, approvals, traces, and guardrails to apply.
Can I cancel or change plans?
Yes. Upgrades take effect immediately and are prorated. Downgrades apply at the next billing cycle, and you can cancel without a long-term platform commitment.
What does the 30-case benchmark prove?
It proves one narrow thing: invalid proposed tool calls were blocked before execution in the published deterministic test. It does not invoke a model, score answer quality, or claim that Rylvo makes a model smarter.
Bring the next client
Stop rebuilding the stack. Build the next agent.
Start free. Upgrade when the client work needs Pro or Team capacity. No application, no deposit, and no separate agency contract required.