tiun.Auth, billing, and payments for AI builders
Promoted
Avocado Studio
AI website ops for Next.js + Astro, in your own components
90 followers
AI website ops for Next.js + Astro, in your own components
90 followers
Hand your website's weekly work to an agent: copy, images, new pages, SEO metadata, translations, site health checks. It works in your own Next.js components, not your CMS database or your code, shows every change on the real page, then publishes a field-level diff to your CMS. Runs on your own Anthropic, OpenAI or Gemini keys. Astro too.
Try the live demo, or run npm create avocado-site@latest. Apache-2.0 on npm. A public research preview: we're looking for early adopters with real sites.
This is the 2nd launch from Avocado Studio . View more
Avocado Studio
Launching today
Not for vibe-coding a new site: Avocado is for running the one you have. An agent handles the weekly work (copy, images, new pages, SEO metadata, translations, site health) in your own Next.js components, never your CMS database or your code. See every change on the real page, then publish a field-level diff to your CMS. Runs on your own AI keys. Astro too.
Try the live demo or npm create avocado-site@latest. Apache-2.0 on npm. Public research preview; early adopters with real sites wanted.
Free
Launch Team
Avocado Studio
Hi Product Hunt — Yury here 👋
We were here in June. This is the version I wish I had shipped then.
Building a Next.js site with AI coding tools is increasingly the solved part.
Changing that site every week for marketers and site owners is not.
The new headline. The hero image. The translated page. The CTA that tested badly.
Those changes still end up in a developer’s ticket queue — or get handed to a coding agent and turn into a code change, review, and deploy.
Avocado Studio points the same kind of AI at your website instead of your code.
Describe the change in chat, or click a heading directly on the live page.
The agent translates your request into typed operations against the components your developers have explicitly exposed. You see every change on the real site in preview before publishing.
Avocado doesn’t change your source code. It works through the editable properties your developers register, keeps changes in a draft layer, and publishes only the approved content changes.
That boundary is intentional.
“Why not just point Claude at my CMS through MCP?”
That’s useful — but it solves a different problem.
A CMS MCP server gives an agent access to your content model: documents, fields, and APIs. The agent works directly against that backend.
Avocado gives the agent a representation of your website.
- Your components.
- Your actual page.
- Your editable fields.
- Your draft.
Changes are previewed on the real site, remain undoable, and are published as field-level updates only when you approve them.
If your developers want to bulk-edit content from Claude Code, a CMS MCP can be great.
Avocado is for the moment when the person making the change **isn’t a developer**.
And they can work together: Avocado also exposes its own MCP server.
Bring your own model:
Avocado runs on your own LLM API keys:
→ Anthropic
→ OpenAI
→ Gemini
Requests go from your server directly to your provider.
Nothing routes through us. We don’t resell tokens. There’s no per-seat AI licence.
A typical chat edit costs a cent or two with Sonnet. Clicking a field, editing manually, undoing, and publishing use no model at all.
Two ways to try it — no sign-up
1. Live demo - the easiest way to get a first impression
https://avocado-editor.vercel.app
It’s a nine-page site.
Try:
“Make the hero headline more playful.”
or
“Use a stock photo of a beach for the hero image.”
2. Run it locally in about a minute
`npm create avocado-site@latest my-site`
`cd my-site && npm run dev`
You get the site, visual editor, and AI layer in one Next.js app.
No API key is required to explore it. Add your own key when you want to use chat.
What changed since our June launch:
In June, Avocado was basically “clone the monorepo and figure it out.”
Now:
→ One-command demo setup < 30 seconds
→ Every package is published on npm
→ Next.js 15 and 16 support
→ Astro integration (still early)
→ Field-level multilingual editing
→ MCP server
→ Much clearer developer-defined editing boundaries
Honest scope
This is still a public research preview.
- Next.js 15 and 16 with the App Router is the most tested path.
- Astro has its own integration.
- Other frameworks can use the core primitives, but they’re less battle-tested today.
- The packages are Apache-2.0 and available on npm. The GitHub repository itself isn’t public yet.
What I’m looking for now
Early adopters who want to help shape this.
Especially:
→ Next.js or Astro teams where marketers still wait on developers for site changes
→ Agencies managing client websites
→ Marketing teams that want to edit the real site without turning every change into a development task
Bring a real site.
You’ll get a direct line to me — and a real say in what gets built next.
Reply here or email hello@avocadostudio.dev
Try it. Push it. Tell me what breaks.