Base44 Introduces Branches for Parallel App Development
Base44Base44 launched Branches, a native feature that lets developers build and test new ideas on an isolated copy of their app without touching the live version. Each branch gets its own chat history and live preview, apps support up to five parallel builds, and branches share live data, connectors, automations, and settings with main. Changes only reach end users after a merge to main and publish, giving teams a single governed path to production.
Key Takeaways
- Branches let developers build safely on isolated copies of an app, keeping the live version fully untouched until changes are explicitly merged and published.
- Merging is a single "Merge to main" action, and Base44's AI resolves most conflicts automatically, only prompting the user when a genuine conflict can't be resolved on its own.
- Live data, connectors, automations, and settings are shared across all branches, so records changed in a branch preview affect the same data the live app uses everywhere — a critical gotcha for testers.
- Test data mode (Builder plan and above) decouples a branch's data from production, letting users experiment with zero risk to real records.
- Apps support up to five branches building in parallel, enabling teams to work on multiple features or redesigns at once without blocking each other.
- GitHub-connected apps cannot use Base44 branches — those apps rely on their connected repository for version management instead.
A Native Branching Model for Vibe-Coded Apps
Base44 introduced Branches, a feature that brings a git-like parallel development workflow to its AI app builder. Instead of editing the live app directly and hoping nothing breaks, developers can now spin off an isolated branch, build and test on it freely, and only bring the changes into the production app when they are ready. The live app stays untouched the entire time.
Creating a branch is conversational, in keeping with Base44's prompt-first approach: a user clicks the app name in the editor, selects "Create new branch," and describes what they want to build. Base44 automatically names the branch from that first message and starts building immediately. Branches always originate from main, even when created while already viewing another branch.
What's Isolated, and What's Shared
Each branch carries its own chat history, live preview, and design/page changes, so experiments on one branch never bleed into another. Builds also run independently — an app can have up to five branches building in parallel, with additional build requests queued until a slot frees up.
Underneath that isolation, branches still share the app's live data, connectors, automations, workflows, in-app agents, and publishing configuration with main. That means records added, changed, or deleted while previewing a branch affect the same data the live app uses everywhere — a meaningful caveat for anyone testing against production records. To avoid this, Builder-plan and higher workspaces can turn on test data mode per branch, which decouples the branch's data from the live database for safe, no-consequence experimentation.
Certain actions remain main-only regardless of branch: publishing, editing entity schemas, managing secrets/connectors/automations/workflows/agents, direct code edits, theme changes, and restoring version history. Apps connected to GitHub can't use Base44 branches at all — their repository handles versioning instead.
Merging and Staying in Sync
When work on a branch is ready, a single "Merge to main" action pulls it into the main branch; the merged branch then becomes read-only but keeps its chat history for reference. If main changes while a branch is still in progress, Base44 surfaces a banner prompting an update — the AI attempts to resolve the merge automatically and only asks for input when there's a genuine conflict. Nothing reaches an app's actual users until a developer publishes from main, so teams retain one controlled path to production no matter how many branches are in flight.
Why It Matters
Branches address a workflow gap that's common as AI-built apps mature past a single prototype: testing a redesign, running a variant for a campaign, or letting two team members build unrelated features at the same time, all without risking the live app. It's a notable step toward treating vibe-coded apps with the same safety rails long-standing software teams expect from version control, while keeping Base44's no-code, conversational interaction model intact. Branch building consumes credits the same way main development does, and there's no cap on the number of branches an app can have.