Let your clients edit their own website.

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.

Any site whose build can run a script, or that has a deploy hook: 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. You keep your codebase and your hosting, and add a small build step (or a deploy hook) so published content reaches the site. Vercel, Netlify, Cloudflare Pages, GitHub Pages, GitLab Pages, AWS Amplify, Render, Firebase, Azure Static Web Apps or your own server: tick your host on the belt above for its exact steps. Sites that need a login to view cannot be previewed.

Yes. Sites from Cursor, Claude Code, Lovable, v0 and Bolt are ordinary sites to Tusk. Add the Tusk MCP to the tool, log in once, ask it to connect the site, then invite the client. The prompt that built the site never needs to run again for a photo swap.

You tell it once, in your own HTML. Mark an element with data-tusk and Tusk finds it: short text, paragraphs, a photo, a download or a repeating list. In the dashboard you can also click anything on a preview of the site to make it editable, and a scan can suggest text you did not mark.

No. You keep the codebase and the hosting. Tusk holds the editable content, and a small build step (or a deploy hook) brings the published content into the site.

They change words, photos and downloads inside the design you built, and add or reorder items in the lists you marked; layout, styles and code are not editable. A much longer text or a very different photo can still change how a page looks, so History keeps the last 30 days of versions and restores any of them.

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 site: the fields you marked, its history, and the progress notes, files and invoices you share with them. Nothing of any other client.

The draft becomes the published content and Tusk calls your deploy hook, or your next build pulls it. It is live as soon as your host rebuilds; how long that takes depends on your deploy setup. You get the event in your dashboard.

With their Google or Microsoft account, or with an email and password. A password sign-in also asks for a code from an authenticator app on their phone, so a stolen password alone gets nobody in. The invitation link sets it up the first time.

You do, by live site, and only from Agency up. Your clients never pay. Free and Agency include one client login per site; Operator and Enterprise have no limit on client logins. The Free plan is free for as long as you like on one site, no card; the only difference is a small “Edited with Tusk” link on that site. A paid plan takes the link off and is billed from the day you choose it.

One small fixed pill in the corner of a site on the Free plan, written into the page by your build step: plain markup, no script, nothing loaded from Tusk when a visitor opens the page. It links to Tusk with your referral code, so a developer who signs up from your client’s site earns you a commission. Choose Agency or above and the next build removes it.

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.

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. You can still sign in, and export any site as a zip: its content, drafts, fields, files and the last 30 days of history.

A few minutes for a small site: add the Tusk MCP to your AI tool, log in once, and ask it to connect the site. Most of the wait is your host building the first time. A large site, or doing it by hand, takes longer.

Your code never leaves your repo. The token your AI tool uses is one you approve on a screen that names the site and the actions; it expires by itself after 30 days and you can revoke it sooner. With a deploy hook, the hook’s link is all Tusk holds of your host; if you ask Tusk to deploy for you, it holds the host API token you give it. Both, and every build token, are encrypted at rest. Full detail is on the security page.

Free is free for as long as you like with no card, so you only pay once it works for you. Cancel any time and you keep editing to the end of the period, then drop back to Free with one site. If something went wrong with a charge, email us and we will sort it out.