1:1
client isolation
One independently owned workspace for every client.
Rylvo for AI agencies
Build in Rylvo.
One agency portfolio. A separate, client-owned workspace for every business you serve. Build, launch, and operate their agents with exactly the access they approve.
Pro from $80 first month+$40/seatZero token markup
Agency portfolio
Interactive exampleClient workspace
Northstar Health
Care concierge
Production agent
Web widget
Deployment channel
2 delegates · explicit, revocable access
Data, billing, and ownership stay with the client.
01Brief02Build03Approve04Live
Explore an example portfolio. Select a client to switch context.
Client-owned workspaces
Permissions by approval
Your keys. Zero token markup.
74 seconds · the product film
Build it. Run it. Make it better.
See how Rylvo brings building, business knowledge, connected tools, safety, testing, customer channels, and continuous improvement into one operating system for your AI agents.
The Rylvo film 01:14
Owner
approval authority
Nothing is granted until the client owner approves.
RBAC
delegated access
Exact people, exact roles, revocable at any time.
$0
Rylvo token markup
Your provider key, your provider bill.
The agency loop
Reuse the operating layer. Keep the client distinct.
Each client gets their own workspace, configuration, ownership, and evidence. Your agency stops rebuilding the same safety and operations stack every time.
- 01
Brief
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
Shape
Configure the client-facing experience
Give each bot its own prompts, knowledge, guardrails, widget identity, accent, greeting, and verified deployment channel.
- 03
Prove
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
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
Don't take our word for it. Try to break it.
Pick a hostile instruction, send it through the real production gate, then create a rule for a tool from your own client workflow.
Production primitive connected
No signup · no simulationAdversary 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.
Critical policy sits between a proposed action and the tool—not buried inside prompt text—then records the decision for replay and review.
Runtime decision
Refund workflow · turn 047
Agent
proposes
Policy
decides
Tool
never runs
policy.result → blocked_before_executionRequired approval_id was not supplied.
01
Deterministic steps
Declare the workflow sequence so an agent cannot invent a step that was never approved.
02
Per-step tool restrictions
Declare which tools are legal at each step and reject a call made outside its allowed boundary.
03
Approvals
Pause nominated actions for a real operator decision before execution continues.
04
Human takeover
Let an operator take over a live conversation while the agent is silenced.
Trace replay
Reconstruct the input, decisions, tool calls, guardrail outcomes, cost, and latency for every recorded turn.
Version rollback
Return a released configuration to a prior version and record the rollback in the audit log.
Simple economics
Pay for the platform. Own the intelligence.
There is no agency deposit or paid launch gate. Build and evaluate on Free; managed workspace linking activates once both sides are on Pro or Enterprise.
Pro
Required on both sides for isolated, owner-approved managed access. Add teammates one seat at a time—no bigger plan required.
$80first month
then $100/month · $80/month billed annually · +$40/seat/month
Up to 25 bots
1 seat included
50 deployment channels
Add teammates for $40/month
BYOK with zero model-token markup
Agency & Client Workspaces included
Start with ProNo deposit · cancel anytime
Built for operators
Sell the outcome. Keep control of the system.
Rylvo is the portfolio, isolated client-workspace layer, and runtime for the agents you build here—not a monitoring skin for unrelated bots.
01
Build once, adapt per client
Reuse templates, skills, integrations, test patterns, and operating practices while keeping every client agent explicit.
02
Put controls outside the prompt
Use restrictions, approvals, takeover, tests, and rollback where a client workflow can affect customers, records, or money.
03
Show clients what happened
Every lead reaches your client's inbox the moment it's captured — in their name, Reply goes to the customer — or their CRM via Zapier, Make or n8n. On the 1st of each month they get a results report in their own name.
See a sample reportQuestions
The commercial model, plainly.
01Is there an application fee, setup fee, or deposit?
No. Rylvo is subscription software. You can build and evaluate on Free, then move both the agency workspace and each managed client workspace to Pro or Enterprise before linking them. There is no paid sprint, application gate, or deposit.
02Which plan should an agency use?
Agency & Client Workspaces is a Pro/Enterprise capability. The agency workspace needs Pro or Enterprise to send a request, and the client workspace needs Pro or Enterprise before its owner can approve it. Delegates are your own people: they work on your agency's seats, so a client workspace never pays for them and you never negotiate a plan change to add one. Free and Lite clients can still inspect and decline requests; every plan can end or revoke a relationship.
03Does 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.
04Can each client have its own agent and channel?
Yes. Each client stays in a separate, client-owned workspace with its own bots, prompts, knowledge, guardrails, channels, traces, usage, plan, and billing. Your agency sees only the workspaces and roles each client owner explicitly approves.
05What happens when a client or agency ends the relationship?
Rylvo revokes only the memberships and API keys granted by that partnership. The client's owner, billing, configuration, history, and data remain in the client workspace. Removing an employee from the agency also revokes that person's linked-client access automatically.
06Is 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.
07Does 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.
08Can I cancel or change plans?
Yes. Upgrades take effect immediately and are prorated. Before voluntarily moving below Team, end active or pending agency/client partnerships so the handoff is deliberate. Forced expiry or a founder override safely ends the relationship, revokes only delegated memberships and API keys, and leaves the client's data, direct team, ownership, and billing untouched.
09What 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.
Build the first agent free. Move both workspaces to Pro or Enterprise before linking a real client; their owner approves the exact people and roles.