Core concepts

Five words carry most of the meaning in Modulify. Everything else in these pages is built on them, and they nest: a workspace holds projects, a project holds one chat and two versions of a site, and the chat spends the workspace's credits.

Workspace

A workspace owns projects, folders, credits, billing and people. It is the boundary for who can see what, and every project belongs to exactly one of them.

Your first workspace is created for you when you sign up, named after you and marked as your default. Your free plan lives in the default one, which is why it cannot be deleted or transferred away. You can own up to five in total.

Switching workspace in the sidebar switches the entire dashboard: a different set of projects, a different plan, a different credit balance and a different member list. Nothing is shared between them except you.

The plan sits on the workspace rather than on you, so upgrading one workspace does nothing for another. Only the owner can change the plan or buy credits, and the workspace owner's plan is what everyone in it works under. Workspaces and Members and roles go further.

Project

A project is one site. It holds the pages and the code, and it also holds everything that site needs at runtime: its Postgres database, its file storage, its secrets, its scheduled jobs, its outgoing webhooks and its domains.

That is worth stressing, because it is where Modulify differs from a page builder. What a project contains is a real codebase, not a tree of blocks, which is why the editor can offer you a file explorer and a database browser at all.

Each project has its own address on the dashboard, /dashboard/projects/<project>, and its own free web address for the published site. Opening one puts you in the editor, where chat runs down the left and the rest of the window switches between tabs. Tabs and visibility maps them.

Preview and published

These are two different copies of your site, and mixing them up is the most common early mistake.

The preview is your working copy, running on a machine of its own that boots when you open the project. It reloads as chat changes files, it is where inline edits, element selection and comments happen, and it is private to people with access to the project.

The published site is the deployment the public sees. It is built and pushed by the Publish button, it serves on your free .modulify.website address and any custom domain you connect, and it changes only when you publish.

The consequence is that you can rework a site all week without touching what visitors get. It also means an edit is not live because it looks right in the preview. Publishing is the step that moves it.

Running out of credits stops you building. It does not take the published site down.

Chat

Chat is the primary way you work. You describe what you want, files change, and the preview reloads against them.

There is exactly one conversation per project and it runs continuously. There is no new chat button and no session switcher, and that is deliberate: what you said earlier stays available, so "make that section wider" resolves against a section you named twenty messages ago. A very long conversation is compacted automatically, with a marker in the transcript where it happened.

Chat is shared with everyone in the project, so a teammate sees your messages and you see theirs. A turn that changes files also takes a version snapshot, so going back is always possible. Site chat covers a run in detail, and Versions covers going back.

Credits

Credits are the unit AI work is metered in. A chat turn that builds or edits is charged on the tokens it actually used, and generating an image is charged per image. Nothing else costs anything: reading, browsing, previewing, publishing, hosting, inviting members and connecting a domain are all free.

A balance is two pools added together. Subscription credits are your plan's monthly allowance, and top up credits are packs bought outright. Spending drains the top up pool first and falls through to the allowance only when it is empty.

Credits belong to the workspace, never to a person, so everyone in it draws from the same balance and switching workspace switches which one you are spending. Credits has the rates, and Plans has what each plan includes.

How they fit together

You sign in as a person. You work inside a workspace, which holds your projects and pays for the AI. You open a project, which is one site. You talk to its chat, which spends the workspace's credits and changes the preview. When the preview is right, you publish, and only then does the public see it.

Next

• Site chat is where the day to day work happens.
• Projects covers the project list and everything a card can do.
• Publish a site turns a preview into a live site.