Client editing for the sites you build.
Built by you.
Kept by them.
Tusk gives your clients a login to edit the text, photos and files on the site you built. They click, change, publish. Your code and hosting stay exactly as they are.
No card. Works with any site. Clients never pay.
A small studio.
A fresh perspective.
Thoughtful spaces, made for everyday life.
Meet the people behind the work.
Draft saved. Publish when you are ready.
- 1Your client clicks the text on their real page
- 2Types the change, saves a draft
- 3Presses Publish. Your deploy runs.
You know these emails.
Each one is twenty minutes you do not bill. Tusk makes them the client’s job, safely.
How it works
Three steps. Then it runs itself.
Add your site and mark what the client may edit. Text, photos, downloads. Nothing else.
They get an email with a link, choose a password, and they are in. No training call.
Every change is a draft until they press Publish. Then your deploy runs and you get the event.
The handover
“Can I make my own edits?”
Every handover ends with this question. The site is live, the invoice is paid, and next month the client wants to change one sentence without emailing you. Until now you had three answers.
Who it is for
A client editable website, whoever built it.
Tusk is the CMS for agencies and freelancers who build fast and keep clients on retainer. Let clients edit their website without breaking it, and keep the codebase to yourself.
You build an AI website in a day with Cursor, Claude Code or Lovable. Then the client wants a new headline and you are back in the prompt.
With TuskMark the fields once. The client edits words and photos on the live page and never sees a repo or a prompt.
The website is one line in a bigger package, and every small change lands on the account manager.
With TuskClients update their own copy, photos and brochures inside the brand you set. The design stays yours.
Ten retainers, ten inboxes of phone number changes and price list PDFs.
With TuskOne dashboard, every site. The client does the small changes and you bill for the real ones.
What you keep
Your code. Your hosting.
Your rules.
Nothing changes in your stack. Tusk sits beside it and holds the content your clients are allowed to touch.
- Any site you already build.Static or server-rendered. Connect it, keep it where it is.
- Publishes through your deploy.A deploy hook, or your next build pulls the content.
- Every change, every site, one view.What changed, who changed it, when it went live.
Connect a siteCheck adapterInvite client
Safe by design.
- Change any text you marked
- Swap and reorder photos
- Upload downloads and brochures
- Save drafts and publish
- Move or break the layout
- Change styles, fonts or colours
- Touch code, hosting or deploys
- See any other client’s site
Pricing
You pay. Your clients don’t.
Priced by live site, not by seat. Give every client and every colleague a login. Ten retainers on Agency is about US$15 a site a month.
USD, billed monthly. Fourteen days free, no card. Cancel any time; your websites keep running.
Questions.
The ones every developer asks first.
What is Tusk, in one line?
A client editor for the websites you build. Your client logs in, clicks the text or photo on their own site, changes it, publishes. You keep the code.
Does it work with my site?
Any static or server-rendered site: Next, Astro, Eleventy, plain HTML. You add one attribute to each thing the client may edit, data-tusk="home.headline", and Tusk scans the pages and builds the editor from them. Your hosting and deploy stay exactly as they are.
Does Tusk work with AI-built sites?
Yes. Sites from Cursor, Claude Code, Lovable, v0 and Bolt are ordinary sites to Tusk. Ask your AI tool to mark the editable elements, press Scan, invite the client. The prompt that built the site never needs to run again for a photo swap.
How does Tusk know what is editable?
You tell it once, in your own HTML. Mark an element with data-tusk and Tusk finds it: short text, paragraphs, a photo or a download. You can also set pages and fields by hand in the dashboard.
Do I have to move the site to Tusk?
No. Nothing moves. Tusk holds the editable content and hands it to your build. The site stays where it is.
Can a client break the layout?
No. They change words, photos and downloads inside the design you built. Layout, styles and code are yours only.
Do I have to give the client access to my code or my AI tools?
No. The client gets a login to Tusk, not to your repo, your hosting or your Claude, Cursor or Lovable account. They see their own page and the fields you marked. Nothing else.
What happens when they press Publish?
The draft becomes the live content and Tusk calls your deploy hook, or your next build pulls it. You get the event in your dashboard.
How do clients log in?
From the invitation link they choose a password. After that it is their email and password. Forgot it? A code by email sets a new one.
Who pays?
You do, by live site. Client seats are unlimited on every plan. Staging and preview sites are free. Fourteen days free to start, no card.
Will this replace my retainer?
It keeps it. The client takes the words, photos and downloads. You keep the code, the hosting, the deploy and every change that needs a developer. Fewer twenty-minute tickets, the same monthly invoice, more room for the bigger work.
What happens to the site if I stop paying?
Editing pauses. The site does not. Nothing of Tusk runs in the path between a visitor and your site, so the last published content keeps serving from your own hosting. Export everything as a zip whenever you like.
Fewer photo-swap emails.
Let clients handle the little changes themselves.