Bring AI-native editing, content operations, and agentic workflows to your existing Next.js stack — without replacing your CMS, DAM, or design system. Self-hostable. BYO AI models. Live demo: https://avocado-editor.vercel.app/
Most AI-native content tools are bundled inside expensive DXPs, proprietary CMSs, or website builders.
Avocado takes a different approach. Instead of replacing your stack, it adds an AI content layer on top of your existing website.
With Avocado you can:
✅ Edit website content using natural language ✅ Manage pages, metadata, and structured content ✅ Work with real design-system components and content models ✅ Preview AI-generated changes instantly ✅ AI-powered content creation and updates ✅ Connect Contentful, Sanity, Strapi, or custom CMSs ✅ Bring your own OpenAI, Anthropic, or Gemini models ✅ Self-host and keep full control of your data
Think of it as an AI orchestration layer for content operations—not another CMS or website builder. Avocado works with structured content and real website components, enabling AI to understand and modify pages the same way your content and development teams do.
I built Avocado because I believe AI-native content management should be available to every team, not just enterprises with six-figure DXP budgets.
What content workflows would you automate with AI?
Thanks for checking out Avocado Studio 🥑 !
Note: The GitHub repository isn't public yet. I'm using this launch to validate the product direction and gather feedback before open-sourcing Avocado Studio under the Apache 2.0 license. If you'd like early access or want to contribute, let me know in the comments.
content ops for Next.js sites is a sweet spot because the same team is usually shipping marketing pages and product copy from the same repo. curious how Avocado handles the boundary between AI generated drafts and the existing review workflow. does it open a PR like a teammate would, or does it write straight to a CMS layer that the team then approves?
Adding an AI content layer on top of an existing Next stack feels way more sane than replacing the whole CMS. BYO models is a nice trust point.
Congrats! Curious how does Avocado handle content model differences when connecting to multiple CMSs like Contentful and Sanity at the same time?
About Avocado on Product Hunt
“AI-native content operations for any Next.js website”
Avocado launched on Product Hunt on June 16th, 2026 and earned 85 upvotes and 6 comments, placing #20 on the daily leaderboard. Bring AI-native editing, content operations, and agentic workflows to your existing Next.js stack — without replacing your CMS, DAM, or design system. Self-hostable. BYO AI models. Live demo: https://avocado-editor.vercel.app/
Avocado was featured in Website Builder (9.5k followers), Marketing automation (4k followers) and Vercel Day (19 followers) on Product Hunt. Together, these topics include over 5.6k products, making this a competitive space to launch in.
Who hunted Avocado?
Avocado was hunted by Yury H.. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Avocado stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Yury H.
Hi Product Hunt 👋
Avocado is an AI content operations platform and framework for Next.js websites.
🚀 Live Demo: https://avocado-editor.vercel.app/
🧩 Component catalogue used on the demo site: https://avocado-site.vercel.app/catalogue
Most AI-native content tools are bundled inside expensive DXPs, proprietary CMSs, or website builders.
Avocado takes a different approach. Instead of replacing your stack, it adds an AI content layer on top of your existing website.
With Avocado you can:
✅ Edit website content using natural language
✅ Manage pages, metadata, and structured content
✅ Work with real design-system components and content models
✅ Preview AI-generated changes instantly
✅ AI-powered content creation and updates
✅ Connect Contentful, Sanity, Strapi, or custom CMSs
✅ Bring your own OpenAI, Anthropic, or Gemini models
✅ Self-host and keep full control of your data
Think of it as an AI orchestration layer for content operations—not another CMS or website builder. Avocado works with structured content and real website components, enabling AI to understand and modify pages the same way your content and development teams do.
I built Avocado because I believe AI-native content management should be available to every team, not just enterprises with six-figure DXP budgets.
I'd love feedback from:
• Next.js developers
• Content teams
• Agencies
• Headless CMS users
• Composable architecture enthusiasts
What content workflows would you automate with AI?
Thanks for checking out Avocado Studio 🥑 !
Note: The GitHub repository isn't public yet. I'm using this launch to validate the product direction and gather feedback before open-sourcing Avocado Studio under the Apache 2.0 license. If you'd like early access or want to contribute, let me know in the comments.