Sync, teams and plans
Sync
Sync keeps your saved connections and saved queries the same on every computer you sign in to. It is off until you turn it on in Settings, Sync.
Everything sync sends is encrypted on your computer first, with keys Flare's servers never have. The servers can see how many items you sync, roughly how big they are, when they change and the names of your computers. They cannot read a connection's name, address, user or password, or the text of a query.
- Your recovery key. Turning sync on the first time shows a recovery key once. Keep it somewhere safe.
- Adding a computer. Sign in on the new computer, then let it in from one that already syncs: both screens show the same six digit code, and you check they match. If no other computer is at hand, use your recovery key instead.
- Conflicts. If the same connection or query changes on two computers before they sync, Flare asks which to keep: this computer's, the other's, or both.
Keep the recovery key
If you lose every computer you sync and your recovery key, your synced data cannot be recovered. Flare never has the keys, so it cannot reset them for you.
Google accounts never sync. A synced Firebase connection remembers which Google account opens each project by an id, and you connect that Google account again on each computer.
Teams
A team shares projects, environments, queries and a feed of changes, and holds each person to what the team allows. Make one in Settings, Teams; you are its owner. Invite people by email from the same page. An invitation holds a seat until it is accepted, and the link in its email lets someone make their Flare account even while Flare is on its waitlist.
- Roles. Owner, Admin, Developer and Viewer, each building on the one below, and any roles the team makes in Settings, Roles.
- Environment access. In Settings, Environment access, each teammate gets read, write or deploy on each environment, or on all of them at once. Access to one environment is the last word there: it can let a Viewer write on Staging, or keep an Admin to reading Production.
- Projects. A project groups a team's environments, such as an app's development, staging and production. A team environment names its kind of database and, for Firebase, the project. Its address and password stay on each person's own computer, in a connection linked to it.
- Team folders. A folder in your connection list shares connections with the team, end to end encrypted like sync, with or without their passwords. A Firebase connection in a folder never carries a Google account: each member opens it with their own.
- Shared queries and activity. Queries and migrations shared with the team are kept by Flare so teammates can open them, and every member's changes show in one feed, without the data needed to undo them.
Roles and access are checked by Flare before each change it makes, but they are not a lock on the database itself. The database's own users and permissions still decide what each person's credentials can do.
Plans
What each plan includes comes from the same table Flare's servers enforce. Prices, and paying for a plan, are on flare.tools.
| What it includes | Free | Solo | Team | Business |
|---|---|---|---|---|
| Saved connections | 3 | Unlimited | Unlimited | Unlimited |
| Projects | 1 | 3 | Unlimited | Unlimited |
| Dashboard widgets each | 4 | 20 | 20 | Unlimited |
| Flare Assistant | Yes | Yes | Yes | Yes |
| Encrypted sync across your computers | Yes | Yes | Yes | Yes |
| Encrypted team folders | No | No | Yes | Yes |
| Roles, shared queries and environments | No | No | Yes | Yes |
| Backups and schedules | No | Yes | Yes | Yes |
| Compare two environments | No | Yes | Yes | Yes |
| Build and check migrations | Yes | Yes | Yes | Yes |
| Run and reverse migrations | No | No | Yes | Yes |
| Audit export, and a year of shared activity | No | No | No | Yes |
A tool your plan does not include stays in the rail, labelled with the first plan that has it. Connections a team shares, in a team folder or linked to a team environment, do not count towards your saved connections, and a plan that shrinks never takes a connection away.
What leaves your computer
The data in your databases goes straight between your computer and the database. It never passes through Flare's servers. What does reach them:
- Your account: your email address and password when you sign in, your name, and the picture you choose.
- Sync and team folders: only encrypted, as above.
- What you share with a team in the clear: shared queries and migrations, shared rules and schema, and the activity feed, which names what changed and where.
- Flare Assistant: what you ask, and a summary of the database's shape (names, types, keys and indexes). Sample values go only if you turn them on.
- Crash reports, with tokens, keys and other secrets removed first. Turn them off in Settings, Updates.
- Plugins: installing one downloads it from Flare's plugin store.
Passwords and keys of your databases never leave your computer except inside sync or a team folder, encrypted. Google tokens stay on each computer. The privacy policy has the full account.