Client editing for Astro and Next.js sites

You build marketing sites in Astro or Next.js, often with Claude Code or Cursor. The site is faster and cheaper than a platform site. Then the client asks to change a headline, and you are the content team again.

The problem

  • Every word change is a ticket

    A ten-second edit costs an email, a commit, a deploy and a reply. Multiply by every client.

  • A CMS means modelling first

    Headless CMSs want schemas, editable regions or annotations before anyone can change a line. That is a day of work per site, and a bill every month.

  • Giving them the repo is not an option

    Clients should never see code, environment variables or deploy settings.

Worked example

An eight-studio holiday rental site in Astro

Three Anchor Heart is a short-stay site built in Astro, with its copy in code. Tova read the repo and found 79% of the text and all 55 photos ready to edit, with no changes to the code.

The owner opens the live site in Tova, clicks the studio description, fixes the bed count and publishes. The commit shows up in the repo under their name, and the site redeploys as it always does.

What you get

  • Every change is a commit

    Edits land in the repo as normal commits, by the person who made them. Your build and host stay exactly as they are.

  • Clients can only touch content

    Text, photos, links and list items. Never code, settings, deploys or the database. Anything else goes to you as a request.

  • Restore any version

    History shows every publish. Restoring a version is one click and one more commit.

One site is free. $9 a month per site, or $90 a year, adds AI edits for text that lives deeper in the code, review before publish and history. Unlimited editors on every plan.

Questions

Do I need to change my code?
No. Tova builds a private copy of the site with source tags and works out what each piece of text came from. Your repo is not touched until someone publishes a change.
What if some text can't be edited?
Text that comes through props, arrays or translations is marked as locked for the client, and AI edits on the Site plan can change it. The site's report shows the share that is ready before anyone invites a client.
Does it work with my host?
Yes. Tova commits to the repo; Cloudflare, Vercel, Netlify or any host that deploys from Git picks the change up as usual.

Hand over the site, keep the repo.

Connect one repository and see what your client could edit, in about a minute.

One site free. No card needed.