Isolated branches

A branch that can't reach real users, mail or data: what it starts with, what is off and locked, how it merges, and what isolation does not cover.

An isolated branch is a copy of the project for work that must not reach real users, mail or data: an agent's run, a contractor's starting point, a risky change. It has your code and your tables, but none of the rows and none of the real keys.

Make one

In the editor, choose New branch… › Branch type › Isolated. Ask your assistant for an isolated branch, and it calls fork_project with isolated set. A branch made from an isolated branch is isolated too, and every branch an Isolated collaborator makes is isolated whatever they ask for.

What it starts with

  • The code.
  • A database with the same tables and no rows, filled by the project's seed script if it has one.
  • Main's preview values where someone saved one; otherwise its keys are empty. Made from another branch, every key is empty.
  • None of main's private stored files. Main's public static assets, such as its logo and images, still show.
  • None of main's queued tasks, app connections (Google and Microsoft account grants), self-edit token or push notification keys. It gets a push key of its own, so a push reaches only people who subscribed on the branch.

What is off and locked

These switches are off on every isolated branch, and nobody can turn them on:

  • Send email: every email the branch sends, including sign-in and password-reset codes, is caught in its test inbox and never delivered. Email logs show it as "Caught · not sent".
  • Receive main's email: main's real inbound mail never reaches the branch.
  • Both realtime switches: its live messages stay on its own channels. Main's users never see them, and it never sees theirs.

What waits or runs in test mode

  • Scheduled jobs and queued jobs start off. Turned on, they run against the branch's own data. Your assistant can turn the branch's scheduled jobs on or off.
  • Payments and shipping run in test mode.
  • Webhooks from outside services are set up with main's address, so they don't reach the branch.
  • OIDC cloud connections can't be used.

Merging and isolation

Merging an isolated branch into main is an ordinary merge, made by someone with Full access: its code and migration script run on main, and reviewing the merge is the gate. Merging main into an isolated branch carries code and tables only: the migration script can't read main's data, and no key values, connections or email domains are copied, so the branch stays isolated.

What isolation does not cover

  • Floot does not block the branch's own code from calling the internet.
  • Outside services work only with keys you put on the branch, and those are used as they are: a real key saved as a preview value, or a key or address written into the code, reaches the real service.
  • Services billed to the project's payer, such as AI credits and hosting usage, still count.
  • A database outside Floot is not copied, so the branch connects to the real one.
  • Anything in the code itself, such as values written into files under static/, column defaults or enum values, can be read on the branch.