Branch limits and cost
How many branches each plan allows, what a branch's database costs past the included ones, and how branches are deleted.
Making a branch is free and takes seconds. Two things are limited: how many branches a project can have open, by plan, and how many branches with their own database are included before each one is charged.
Open branches per project
| Plan | Open branches per project |
|---|---|
| Free | 1 |
| Pro | 5 |
| Power | No plan limit |
- The count is per main project: every open branch, including branches of branches, whoever made it.
- It goes by the plan of whoever pays for the project (the team, or the owner of a personal project), not the person making the branch.
- Merged branches count until they are deleted, and so do scratch branches.
- Only making a branch is limited. After a downgrade, the branches you have keep working and can still be merged.
When the limit is reached, New branch says so and lists the merged branches you can delete to free a place. Only the project's owner can upgrade its plan.
Charged branches
Each branch with its own Floot database has a database branch of its own. A project includes 24 of them besides main. Each one past that costs $3 a month from the project's hosting balance, charged by the hour until it is deleted. Branches without a Floot database never count.
Before the first charged branch, New branch asks: someone who can make branches agrees once for the project with Allow charged branches. After that, while the next branch would be charged, New branch shows how many are charged now. Your assistant can't agree to the charge for you: it gives you the editor link instead. In practice only Power projects get past 24 open branches.
A branch's database also counts toward hosting like any database: its storage and compute are part of the project's hosting usage.
Deleting branches
Delete a branch from Branch Reviews, from a merged branch's page, or by asking your assistant. Deleting removes the branch's code, its own database copy, its comments and its published site, and stops its charge at once. A merged branch's changes stay on main. A branch that was never merged into main is lost for good, so your assistant can delete one only by saying it means to discard the unmerged work.
- Merged branches
- Deleted 7 days after the merge into main or their last comment. Not deleted while kept, once edited after the merge, or while another branch made from them is open.
- Scratch branches
- Deleted 7 days after they were last edited, opened or commented on. Not deleted while kept, or while another branch made from them is open.
- Keep
- Keep in Branch Reviews stops the automatic delete. Don't keep starts the days again from that moment.