Skip to main content
Fabricate helps you build web apps by describing what you want in plain language. Work in the chat, try the result in the preview, and publish the version you are ready to share. You can inspect the generated code and keep improving the app as your needs change.

Start here

Build your first app

Go from your first prompt to a preview and a published address.

Understand your project

Learn how chat, preview, code, data, and publishing fit together.

Write a clear brief

Define the users, records, rules, and first useful workflow.

Plans and credits

Understand usage and check the current features for your plan.

What you can work on

Start with a focused web workflow: a request portal, a tracker, a dashboard, a booking interface, or a small business tool. Describe the information it saves and who should be allowed to use it. Add integrations and more complex behavior after the core journey works. The generated result needs review. Test its data, permissions, and external connections before inviting people to rely on it. A working preview is useful evidence, but it is not a complete product acceptance test.

Core concepts

  • Project: one app with its conversation, code, preview, and settings.
  • Chat: where you ask questions and request changes. Questions use credits too; say explicitly when you want an explanation without edits.
  • Preview: the version you interact with while building.
  • Published app: the version at a live address after you choose to publish.
  • App users: people signing in to the app you build, separate from your Fabricate builder account.
See the glossary for more terms.

Follow the full workflow

1

Plan one outcome

Write a project brief with a main action, the records it saves, and access rules.
2

Build and iterate

Work in the chat, try the preview, and request focused changes.
3

Check the behavior

Test the app: save a record, refresh, reopen, and check access with separate accounts.
4

Publish when ready

Use the launch checklist, then publish. Check the live address separately.
Preview and published apps have separate databases. Preview records are not copied when you publish. Preview changes do not automatically update your published app.

Explore by task

For current plan limits, use pricing. For product questions, contact support@fabricate.build.