Agencies
Stop being the bottleneck on copy tweaks
Client wants a headline shortened on a Friday afternoon. Today that is a ticket, a context switch and a deploy. With Lexi they ask, they approve, and you read the pull request on Monday.
For agencies, studios and freelance builders
Give clients a chat box, not your codebase.Every change still arrives as a pull request.
Your clients ask for copy and image changes in their own words. A coding agent makes the change, they check the preview and publish it themselves. You are not in the loop: the rules you set once decide what that agent can ever touch, and every change lands in your repository as a commit you can read or revert.
Runs onThe rails are the same everywhere. The model is a budget you pick per change.
Who it’s for
Built for the people who maintain other people’s websites.
Freelance builders
Keep the retainer without keeping the inbox
Small edits are the work you least want and can least justify billing for. Hand them over without handing over repository access, and keep the site exactly as you built it.
Studios shipping fast
Ship a site without inheriting it forever
A static site with no CMS is faster to build and cheaper to host, right up to the first content request. This is the missing piece: content editing that leaves your stack alone.
How it works
Three steps. Your client runs all three.
What you get
The chat box is the easy part.
Every change is a pull request
What the agent changed, on a branch, with the client who asked for it. Revert it any time.
A preview before it's live
Your host builds a Deploy Preview first. Your client looks before they publish.
Guardrails the agent can't cross
A policy file you own sets the paths and size the agent may ever touch.
One-press Undo
Publishing merges a pull request. Undo reverts that merge.
No database to babysit
GitHub is the record, your host serves it. Nothing new to back up.
Self-hosted, always
Run it on your own infrastructure, forever, for nothing. AGPL 3.0.
Under the hood
Real infrastructure, explained plainly.
Cost you control
Each request carries a budget, not a model name, and the agent runs on a model that matches it. A wording tweak does not need the power a new section does, so most client edits cost pennies. Included in the plan price, with no usage bill arriving separately.
Work happens in a sealed room
The agent works in a fresh, locked room that is destroyed the moment it finishes. It holds a copy of the files and nothing else: no credentials, no tokens, no route to the client's live site. It cannot publish, and it cannot reach your other clients.
Rules you set, checked every time
You set which paths may ever be edited and how large a change may be, per website, in a file your clients cannot see. Lexi reads what the agent produced and checks it against those rules before anything is committed. Work that breaks one is thrown away and reported to you.
Setup takes a day, not a minute
We connect each client repository and host by hand so it is right the first time. Expect to be handing sites over within one business day of signing up. Running it on your own infrastructure instead is instant and free.
Pricing
Priced per site, like the hours it replaces.
Priced per client website. Drag the slider to the number you look after. Every plan ships changes as reviewable pull requests, with a preview first. Cancel any time; annual plans are billed upfront.
Most popular
Studio
$39/mo
billed monthly
For a freelance builder looking after a handful of client sites.
- 1 change running at a time
- Client editor on a lexi.app subdomain
- Every change lands as a pull request
- Email support
Agency
$153/mo
billed monthly
For a studio or agency shipping client work every day.
- 3 changes running at once
- Client editor on a domain you control
- Per-client access and audit trail
- Priority support
Custom
Let’s talk
priced per engagement
20+ websites
For more client sites than the sliders go, or a stack that is not GitHub and Netlify.
- More than 20 client websites
- Pinned models, your own keys or hosting
- White-labelling and self-hosting with support
- Invoicing and a signed agreement
Prefer to run it yourself? Lexi is open source. Run it on your own machines ↗.
FAQ
Questions, answered plainly.
Who actually makes the change?
An AI coding agent. It reads the repository, edits the files and finishes the job on its own, the way a developer would on a branch. Lexi is what stands around it: the rules it must obey, the preview before anything ships, and the record of what it did.
Do my clients need to understand any of this?
No. They see a chat box and a publish button. No repository, no branches, no build logs, and nothing to install. They write what they want changed the way they would say it to you, and the agent does the rest.
How long does setup take?
Usually one business day per website. We connect the repository and the host by hand rather than making you work through a wizard, so it is right the first time. You get an email when it is ready.
What do you need from me to get started?
The GitHub repository and the Netlify site for each website, and the email addresses of the clients allowed to request changes on each one. One short form after checkout covers it.
What is OpenRouter, and do I need an account?
OpenRouter is the service that routes each request to whichever model the agent runs on. On a paid plan there is nothing for you to set up: it is included in the price, with no separate bill and no key to manage. Only self-hosters bring their own.
Which model does the agent run on, and can I pin one?
Each request carries a budget rather than a model name, and we map budgets to models: free for a wording tweak, stronger for a new section. If your client work needs a specific model or provider, we can pin it on a custom plan.
Does the client site change address?
No. Your client keeps their domain and their host. Lexi only edits the repository behind it. The editor your client signs in to is a separate address: a lexi.app subdomain on Studio, or a domain you control on Agency. Choosing a domain per site inside Lexi is on the roadmap.
Can I brand the editor as my agency?
On Agency, yes: the editor runs on your own domain, so a client never sees a third-party product in the address bar. Deeper white-labelling, including your own mark and palette, is a custom plan.
Who can request a change, and can I see who asked?
Only the addresses you name, per website. Everyone signs in with a code sent to their email, and every request is recorded against the person who made it, so there is an audit trail when a client asks why something changed.
How much control do I keep over what they can touch?
All of it, and you set it once rather than approving each change. A policy file in the repository fixes which paths may ever be edited and how large a change may be. Your clients cannot see it or change it, and work that breaks a rule is blocked before anything is committed.
What if a change is wrong?
Nothing publishes on its own. Your client sees a preview first and decides; if they do not publish, nothing happens. A published change was a merged pull request, so Undo reverts the merge, and you can revert it yourself from Git like any other commit.
Does this replace my CMS, or my deploy pipeline?
Neither. Lexi edits the repository you already have and waits for the preview your host already builds. Your stack, your branch protection and your review process stay exactly as they are.
What if I take on more client sites?
Move the slider and your subscription follows, because you are billed per website. Studio covers 3 to 8 websites, Agency 9 to 20. Past that, or for a setup we do not list, talk to us about a custom plan.
Can I cancel?
Any time, from the billing portal linked in the footer. Client repositories and sites are untouched: cancelling stops Lexi editing them and removes nothing.
Can I run Lexi on my own infrastructure?
Yes. Lexi is open source under AGPL 3.0. Run it on your own machines, for any number of client sites, at no cost, forever. You supply your own OpenRouter key and do your own setup and updates.
Ready to hand the small stuff back to your clients?
Run it on your own infrastructure for nothing, or let Lexi host it for you.
Get started