Modulify
Dashboard

Welcome to Modulify

Describe a site in chat, watch it get built, and publish it to a real address.

Modulify builds a website from a description. You type what you want into chat, the AI writes the site, and a live preview sits next to the conversation so you see every change as it lands.

What comes out is a real codebase, not a page of template blocks. Each project can carry its own SQL database, its own file storage, scheduled jobs, outgoing webhooks, deploy hooks and custom domains, and it is served on a free .modulify.website address until you point your own domain at it.

If you would rather work from your own editor, the MCP docs cover connecting Claude Code, Claude Desktop or Cursor to Modulify, and every tool a connected client can call.

Getting started

If this is your first time, work through Getting started in order. It takes about ten minutes and ends with a site anyone can visit.

Build with AI

Chat is where the work happens. There is one continuous conversation per project, so context you have already given carries forward.

  • Site chat covers the conversation itself and how a run behaves.
  • Plan and Build modes explains when to approve a plan before files change.
  • How work is sized covers how Modulify sizes each message and what a turn costs.
  • Writing prompts is how to phrase a request so you get what you meant.
  • Attachments and context gives chat images, files and on-page references.
  • Images covers real photography, generated artwork and your own pictures.
  • Skills attaches reusable instruction sets so builds match your standards.
  • Connectors lets the agent read and act in Notion, Slack, Stripe and more.
  • Message queue lines up your next requests while a run is still going.

The editor

Opening a project puts you in the editor. Chat runs down the left, and the rest of the window switches between tabs.

  • Tabs and visibility maps the tab strip and the twelve tabs behind More.
  • Use the preview covers pages, viewports and reading the working copy.
  • Select an element points chat at a specific thing on the page.
  • Inspect a page reads the fonts, colors, spacing and images of anything on the page, and copies them.
  • Comments pins feedback to a spot on the page and threads the discussion, with your team or, if you allow it, anyone holding the read-only link.
  • Backups is the automatic code snapshot history and restoring one, plus the storage archives you can browse, restore and download, and the database archives you can download.
  • Files and code reads the source and exports it as a zip.
  • Logs covers the five log streams and what lands in each.
  • Project settings is the name, region, badge switch and Danger zone.

Projects

A project is one site. Projects belong to a workspace, not to you personally.

  • Projects explains what a project holds and what the card menu does.
  • Create a project starts one from a prompt, a template or an existing site.
  • Templates browses the gallery and clones one into your workspace.
  • Folders groups projects and moves them between folders and workspaces.
  • Archive projects puts projects out of sight without deleting them, and brings them back.
  • Search and filters finds a project across every folder and in the Archive.
  • Sharing and cloning covers read-only links, comments from viewers, clone permission and duplicating.
  • Transfer a project hands a project to another person or workspace.
  • Delete a project covers what deleting removes and who may do it.

Data

Sites that do something usually need somewhere to keep it. Both the database and the storage bucket are per project.

  • Site databases is the real SQL database the AI creates and shapes.
  • The CMS browses collections and edits rows without writing SQL.
  • Column types lists every column type the CMS understands.
  • Storage is per project file storage served from a CDN link.
  • Storage HTTP API is the nine endpoints your site calls at runtime.
  • Clearing and exporting gets your data out, or wipes it.
  • Multiple languages covers how a site gains a second language and how you switch.
  • Secrets stores API keys and configuration your site reads at runtime.

Publish and host

Nothing you change reaches your web address until you publish. The preview and the published site are two different things, and a read-only link is how you show someone the preview.

Automations

Four things connect the site to the rest of your tools.

  • Scheduled jobs calls one of your own URLs on a schedule and records the response.
  • Webhooks sends an HTTP call to your endpoint every time the site publishes.
  • Deploy hooks gives the site a secret URL that starts a publish when something calls it.
  • Emails lets the site send transactional email from its own address.
  • Email HTTP API is the four endpoints your site calls to send email, read a sent email back, list its history and check its allowance.

Grow

Plans and credits

A plan and a credit balance belong to a workspace, so everyone in it draws from the same pool.

  • Plans covers what Free, Starter, Pro and Enterprise each include.
  • Credits explains what spends them and when they come back.
  • Buy credits tops up a workspace with a one-off pack.
  • Manage your subscription upgrades, cancels, resumes and finds invoices.
  • Limits and quotas puts every plan gate and hard limit in one table.
  • Share and Earn pays credits for every person you invite, and more the first time they pay.
  • Affiliates is the affiliate program, your code and what earns a commission.
  • Referrals and payouts reads both affiliate tabs and follows a payout through.

Reference