The AI Website Builder Agencies Run in the Browser.
One tab, a real IDE, an agent in every repo: Zyan Build is the AI website builder for web design agencies — a browser IDE where your team and a Claude Code agent work the same client repo, with a file tree, editor, live preview, and a real terminal in one window. Clone, branch, commit, push, open the pull request. Nothing to install on anyone’s laptop.
Avid Auto Detailing · Derry, NH · auto detailing1
Every Change Lands as a Commit You Can Read.
Ask the agent for a change and it comes back as a diff, not a mystery. Read it, commit it, push the branch, open the pull request — and the whole run, prompt included, lands in the activity ledger your agency shares.
- Diffs before commits — nothing reaches the branch unread
- Branch-aware git in-window: clone, branch, push, PR, check status
- Prompt runs, commits, and comments in one ledger
Everything the Job Needs, Inside One Window.
Editor, preview, git, assets, prompts, and the terminal sit in the same workspace — so nobody exports a zip, and nothing about the project lives only on one person’s laptop.
A real terminal, with the agent in it
Not a toy console. Run the dev server, install a package, run the tests — or hand the same shell to a Claude Code agent that reads the repo and writes the files while the preview reloads beside it. Real Linux machines, so there is no local toolchain to babysit.
Live preview beside the code
The site renders next to the editor and repaints on save. Check it at desktop, tablet, and phone width without leaving the window.
desktop · tablet · phoneReal git, end to end
Clone the client repo, branch, commit, push, open the pull request, and watch its status land — the workspace speaks git, not exports.
clone · branch · push · pr statusA component library to pull from
Drop in ready-made blocks as real, editable source — fork them into your system, or publish your agency’s own kit and reuse it on every build.
shared blocks · your kitA prompt library the team shares
Save the prompts that worked. The next project starts from your agency’s brief instead of someone re-typing it from memory.
saved per workspaceProject images in the same window
Search licensed imagery, generate what is missing, and drop it into the repo with its source and license attached.
licensed · attributedClick the preview, say what you want
Pin a note on the live draft and the agent turns it into a bounded edit — scoped to the element you touched, diffable, and gated like everything else. See how it is bounded →
pin → bounded json ops → reviewShip it, then tear it down
Push the built site to the client’s host over FTP straight from the workspace, or hand the repo to their pipeline. Each terminal session runs in its own sandbox and is torn down when you close it.
ftp deploy · per-session sandboxHundreds of Sections. One Click in the Terminal.
Hero sections, feature grids, pricing tables, blog templates, call-to-action blocks — hundreds of page sections tuned for the layouts that actually convert on client sites. Drop one in from the terminal and it lands as editable source, already wearing the project’s brand.
Pick the section
Browse by what the page is missing — a hero, a feature grid, a pricing table, a blog index, a closing call to action.
Drop it in
One click from the terminal writes it into the page as real, editable source — never a locked block you have to fight.
Make it theirs
It arrives on the project’s colors and type. Hand the tedious half to the agent and watch the diff while it works.
The SEO Command Center Opens in the Same Window.
Audit the site you are editing, research keywords against live search data, and rewrite titles and metadata on the page in front of you — then let Autopilot keep shipping fixes as pull requests long after launch.
- Audits with prioritized fixes, on the branch you are on
- Keyword research on live search data, budgeted per project
- White-label reports the client opens in their own portal
Same Repo. Same Feed. Same Picture.
Presence, prompt runs, commits, comments, and merges land in one feed the whole agency can read — so nobody screenshots a diff into chat or asks which branch that was on.
Pre-Built. Or Bring Your Own.
Start from the shared library — hundreds of components, all editable source — fork them into your agency’s system, or publish your team’s private kit and pull it into every build.
Fork it, do not fight it
Every component ships as editable source. Fork one into your agency system and it stops being somebody else’s abstraction.
Publish your own kit
Push the components your team keeps rebuilding into a private kit, then pull that kit into every client project you start.
It lands as real files
Inserting from the library writes to the branch you are on — reviewable in the same diff as everything else your team shipped.
The Same Studio Works as a Classroom.
Templates hand every student a real site on day one — no install night, no laptop left behind. Seats and permissions keep cohorts organized, and the activity feed shows instructors the actual work: every edit, prompt, and commit.
The Terminal That Ships Sites Runs the Agency Too.
Zyan Build is one surface of the same runtime. The Claude Code session that writes a booking page is the one that opens your SEO fixes and drafts your ad changes.
Next for Zyan Build: live co-editing, richer deploy targets beyond FTP, and a shared registry for agency starters.
Follow the changelog →