Base44 · Setup guide
How to set up Base44
Describe an app, website, or agent in the Base44 workspace, review the generated result, then tighten branding, domains, and integrations before treating anything as production.
The “Open Base44” link goes to the vendor site. It is not an affiliate-tracked link on this page — no commission is claimed for that click. Affiliate disclosure.
Before you begin
- A Base44 account and a modern browser.
- A concrete brief covering pages, data, auth, and whether you need agents or payments.
- A custom domain only after the preview matches your acceptance criteria.
Authentication
Base44 account sign-in
Account: Base44 account
Superagents and third-party integrations expand the data boundary — review connected tools before production use.
Install or open it
1. Get the harness ready
These steps are written for beginners. On Mac, Terminal is the black/white text window where you type commands. On Windows, use PowerShell or Terminal. Use the OS tabs to hide steps that are not for your computer, then copy one command at a time.
- 01
Open Base44 in your browser
Go to base44.com, create an account, and start from the workspace home. You do not need a local toolchain for the standard builder workflow.
Base44 homepage - 02
Pick apps, websites, or Superagents
Choose app/website building or the separately presented Superagents product. Check each product's access, billing and connected-tool permissions; do not assume identical hosting or credit allowances.
Base44 homepage - 03
Review generated structure before publishing
Use the in-workspace preview and design controls to check layout, copy, and flows. Treat the first generation as a draft — tighten scope before adding auth, payments, or external integrations.
Base44 homepage - 04
Connect integrations deliberately
Base44 advertises one-click integrations, analytics, and custom domains on paid tiers. Add only the integrations your brief requires and confirm billing/credit usage on the live pricing page.
Base44 pricing
Repository or project
2. Start in the right place
Keep the first repository small, clean, and easy to roll back while you learn the harness’s permissions and context model.
- 01
Start with a narrow acceptance checklist
Describe one workflow, the pages it needs, and what should remain out of scope for v1.
Base44 homepage - 02
Use in-app code edits only after the preview is right
Starter includes in-app code edits. Builder and above add backend functions, GitHub integration and model selection; model availability can roll out by account. Discuss uses its own model rather than the selected build model.
Base44 homepage
First run
Prototype a read-only marketing page
Use this task to test the workflow before handing over a larger repository or production responsibility.
- 01Ask Base44 to generate a single landing page with a clear headline, one CTA, and no auth.
- 02Review desktop and mobile layout in the workspace preview.
- 03Only then add analytics, domains, or Superagent automation if the brief requires them.
Why this is safe: A read-only page exercises generation quality without payments, credentials, or agent side effects.
Stop and review if
- The workspace asks for payment credentials before the static page works.
- An integration is added that your brief did not request.
- Credit usage spikes on retries without a clearer prompt.
The operating boundary
Privacy, data, and cost
The setup is incomplete until you know what the harness can see, what account pays for it, and who approves a risky action.
Privacy
Base44 is a Wix-owned cloud builder. Its security page labels workspace model-training opt-out Enterprise; the privacy policy describes service improvement, analytics, vendors and purpose-based retention. These pages do not establish universal no-training or zero retention. App data and workspace/superagent tools have separate access scopes.
Training on code: tier dependent
Confirm current Base44 / Wix terms for your region and plan.
Sensitive repos: Review app visibility, login and each table's create/read/update/delete rules with different roles. Multiple matching rules grant access if any rule matches, and rule changes take effect immediately; a private-looking preview alone does not establish customer-data isolation.
Pricing
Annual-equivalent published prices: Starter $16/month, Builder $40, Pro $80, Elite $160; billed annually. Monthly message/integration allowances are Free 25/100, Starter 100/2,000, Builder 250/10,000, Pro 500/20,000 and listed Elite 1,200/50,000 with selectable larger packages. Free supports up to five apps.
Model: hybrid
Watch out: Message and integration allowances are separate. Build is the default and can act immediately; use Discuss for planning before approval, at 0.3 message credits. Model selection is Builder+ and model usage varies; manual visual edits use no credits. Check Superagents separately.
When setup goes wrong
The preview looks right but publishing breaks auth or data.
Re-check auth rules, integrations, and environment-specific settings before republishing.
Superagent actions do more than the brief requested.
Narrow the agent instructions, remove unused integrations, and test with a smaller scope.
Next steps
After the first successful run
Keep the pilot small, then compare surfaces and budget before a team rollout.
Setup details change quickly. The page was checked October 2, 2026; use the official source below before installing in a managed or production environment.