Ship website updates faster.
Make changes to your existing Next.js, Astro, or Vite site from the page you can see. Frontman edits source files in a supported development environment. Your developers still review, test, and deploy.
Frontman is a source-available AI editor for existing framework websites. A developer installs it in a running supported project with permitted workspace access. Sign in to Frontman, arrange service access, and connect your own supported AI provider. Provider costs are separate. Relevant context passes through the Frontman server to your selected provider.
Choose your path
What kind of site do you maintain?
Frontman keeps one promise across both workflows: update the site you already have from the page you can see.
WordPress site owners
Edit WordPress beside your live site
Update posts, pages, Gutenberg blocks, Elementor layouts, menus, media, settings, and WooCommerce data without hunting through wp-admin.
Install WordPress plugin →Marketing and design teams
Turn site requests into reviewable changes
Use Frontman on Next.js, Astro, and Vite sites so marketers and designers can click the page, request changes, and hand developers a normal diff.
Get developer setup →Install for your supported stack
For Next.js, Astro, or Vite, a developer needs a running supported project and permitted workspace access. For WordPress, an administrator installs the plugin through wp-admin. Start on staging and keep backups. Sign in to Frontman, arrange service access, and connect your own AI provider. Provider access and costs are separate. See current pricing and provider setup.
Add to your project
Run one command in your project folder
npx @frontman-ai/nextjs installOpen Frontman
Visit localhost/frontman in your browser
http://localhost:3000/frontmanConnect your AI
Sign in to Frontman and connect a supported AI provider
What is Frontman?
Frontman is an AI website editor for existing sites. It runs inside WordPress or your framework dev server, reads the live page plus CMS or source context, then turns visual requests into reviewable website updates.
Why it works better than tickets
Website requests usually start with screenshots and vague descriptions. Frontman starts from the page itself: selected elements, computed styles, source mappings, routes, logs, and live preview feedback. That context helps the agent change the right thing with less back-and-forth.
Click any element. Tell it what you want.
Select a component directly in your browser — a button, a card, an entire section. Describe the change in plain English. No file hunting, no line numbers, no IDE.
Pro tip: use the up and down arrows to move between components and divs
Watch your code change in real time.
Frontman edits your source files in the connected development workspace. Inspect the hot-reloaded page, then have your team review the diff, run tests, and commit and deploy through its normal Git workflow.
And that's just the beginning.
Everything you need to build faster, smarter, and with more confidence.
Inspects the rendered DOM, computed CSS, and component boundaries to add visual context to source edits.
Switch between device presets — iPhone, iPad, desktop — and see how your changes look at every breakpoint.
Reads build output, console warnings, and stack traces to help diagnose errors. Review the result and run your project checks.
Source-available with BYOK model support. The browser client and JavaScript integrations are Apache-2.0, the WordPress plugin is GPL-2.0-or-later, and the server is AGPL-3.0-only with AI Supplementary Terms. Connect a supported provider account or save a supported API key. Provider costs are separate.
Reads agents.md, claude.md, or custom rule files at session start. Review source changes for compliance with your conventions.
Works with Next.js, Astro, Vite, and WordPress. Modern apps or CMS sites — your stack, your rules.
Works with your stack
Framework middleware for modern apps. Plugin-native editing for WordPress sites.
Comparing AI tools for UI work? Read the frontend coding agent guide for Cursor, GitHub Copilot, Claude Code, v0, Bolt.new, Kombai, Stagewise, and Frontman.
FAQ
Frequently asked questions
Setup, source output, and publication boundaries.
What do I need before my first framework edit?
A developer installs Frontman in a running supported Next.js, Astro, or Vite environment with permitted workspace access. Sign in to Frontman, arrange service access, and connect a supported AI provider. Provider access and costs are separate.
How do changes reach production?
Frontman edits source files in the connected development workspace. Your team reviews the diff, runs tests, and deploys through its normal Git workflow. Check integration guards, built artifacts, and deployed routes when Frontman must be absent from production.
Can I use Frontman with WordPress instead?
Yes. Use the WordPress plugin path at frontman.sh and open Frontman from the admin menu. WordPress writes persist to the connected installation; published content on a live site can change immediately. Start with staging and backups.
Move from request to source change.
Start with one update in your development environment. Inspect the page, review the source diff, and test and deploy through your team’s normal workflow.