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.
Base44
browser · checked September 3, 2026
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 whether you are building a web app, marketing site, or an autonomous Superagent. Each path shares hosting and integrations but changes the first prompts you should write.
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
Paid tiers advertise in-app code edits and AI model selection. Do not jump to code changes until the generated structure matches your brief.
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 cloud builder operated by Wix. Prompts, generated apps, analytics, and Superagent actions run on vendor infrastructure — review current terms before confidential data or regulated workloads.
Training on code: not verified
Confirm current Base44 / Wix terms for your region and plan.
Sensitive repos: Do not connect production customer data or secrets until you have reviewed generated auth, storage, and integration scopes.
Pricing
Free tier with core features; paid plans from about $16/mo when billed annually (confirm live pricing). Credits and feature gates vary by plan.
Model: hybrid
Watch out: Credit consumption on retries and agent workflows can exceed the sticker plan price — monitor usage during the first build session.
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 September 3, 2026; use the official source below before installing in a managed or production environment.