IN DEVELOPMENT. Mogul mode is not available yet. This page describes what we are building, not what you can use today.
Mogul mode
You already build things people pay for. Now deliver them.
Mogul turns a project you host on YOLO into something you hand to a client: their own login, their own inbox, a subscription they pay you for, and enough of the day-to-day to stop them asking. You stay the builder. They stop being a spectator.
How it works
Three steps, and none of them change how you build
1. Build it in YOLO
Nothing changes about how you work. Build the site or app in a workspace and ship it to YOLO Host exactly as you do today.
2. Attach a client
Add the client to the project by email. They get an invitation, redeem it, and that becomes their login. If they already have a YOLO account, it is the same account, never a second identity.
3. They get a portal
Your client signs in to the place they run their business from: their inbox, their bookings, their day-to-day. Not a developer console. Not your workspace.
The portal
Where your client deals with you
A status page is not worth signing in to. The portal is the place your client pays you, reaches you, and sees enough of the day-to-day to stop asking. You built the thing and you keep running it. This is where the relationship lives.
A line to you, and an inbox of their own
Every enquiry the site takes lands in their inbox, and the portal is where they reach you about it. A quote request, a contact form, a question about the site. No more forwarded email, and it is their inbox, not a copy of yours.
Their subscription, paid to you
What they pay you, what it covers, the invoices, the card on file. Handled in the same place they already sign in to, so getting paid stops being a monthly errand for either of you.
Enough of the day-to-day to be useful
Who is booked in on Thursday. The week ahead. Opening hours, prices, a service paused for the winter. You choose what the portal shows and what it lets them change. It is not an admin panel, and it is not trying to be one.
Two ways to deliver
Keep it, or hand it over
Managed
You keep the keys
You stay the owner and the operator of the BUILD. You deploy, you promote to production, you approve changes. The client runs the business the site exists for, and pays you for keeping it running.
You remain the only person who can deploy or promote
The client pays you, reaches you, and works their inbox without touching the build
They see their project and nothing else, including that your other clients exist
Hosting usage stays on your YOLO account
Full transfer
You hand it over
For the jobs that end. Transfer the hosted project to the client outright: the slug, the domains, the releases, the history. They own it from that moment.
Works whether or not they already have a YOLO account
The project keeps serving throughout, with no downtime window
Your source workspace stays yours unless you say otherwise
Billing
Your Stripe. Your customers. Your revenue.
You connect your own Stripe account. Your clients are your customers, their subscriptions live in your account, and the money goes to you. YOLO never sits in the middle of it and never holds your funds.
We never ask for your Stripe secret key. Connecting is an authorisation you can withdraw, and if you disconnect, your clients' subscriptions keep running. They are yours, and they always were.
Set your own plans
Care & hosting
$49 / mo
Care + monthly changes
$99 / mo
Unlimited changes
$199 / mo
Illustrative. You name the plans and set the prices. These are yours, not ours.
What your client sees
Their business, your build
A client can pay you, talk to you, and change the handful of things that are business decisions rather than engineering ones. They cannot reach your repository, your agents, or anyone else you work for. If a job needs a real admin panel, that is something you build into the app. The portal is not pretending to be one.
They can see
Their subscription, invoices and payment method
Their inbox, and the enquiries their site has taken
Enough of the day-to-day to be useful: bookings, schedule, orders
The project, its live URL, and whether it is up
Release history and recent activity
They cannot
Your workspace, repository or source code
Your agents and their sessions
Environment variables, secrets and credentials
Any of your other clients, or that they exist
Production stays yours. A client can watch a release go out; they cannot push one. Approving what goes live is the operator's job, and it stays with you.
The work was always the product.
Mogul is the part that turns it into a business: the login you give someone, the invoice that arrives every month, and the thing that stays up in between.
IN DEVELOPMENT / NOT YET AVAILABLE