Help with Flare.

Flare is a desktop workspace for your databases: Firebase, PostgreSQL, MySQL, SQLite, Redis, Supabase, MongoDB, Cassandra and S3 storage. It brings their data, queries, schema, migrations, backups and team workflows into one place.

Windows 10 or later, macOS 11 Big Sur or later on Apple silicon and Intel, and 64 bit Linux.

Flare does not come with a sample database yet, so you will need something to open. The quickest ones need no server: a SQLite file on your computer, or the Firebase emulators running locally. The Free plan opens every kind of database for as long as you use it.

Firebase, PostgreSQL, MySQL, SQLite, Redis, Supabase, MongoDB, Cassandra and S3 storage. S3 means AWS S3, Cloudflare R2, MinIO, or another service that speaks the S3 API. Many more databases are on the way.

Choose New connection and paste its address: PostgreSQL, MySQL, Redis, MongoDB and Supabase addresses fill in the rest for you. Or pick the database and fill in the host, port, user, password and database. SSL can be automatic, required, or required with the certificate verified. Test tells you whether it works before you save. SQLite opens a file on your computer, and S3 takes an access key, a secret key, an endpoint and a region.

Not at the moment. Flare connects straight to the host and port you give it. If your database is only reachable through a tunnel, open the tunnel yourself and connect Flare to its local end.

On your computer, in a file encrypted with your operating system's credential storage wherever it has one. Flare's servers never see them, and nothing is shared with your team unless you choose to share it.

Yes, Firebase is where Flare started. Firestore opens as a table you can browse, query and edit, beside Authentication, Storage, Security Rules, Cloud Functions and the local emulators, with the same activity log, undo and production checks as every other database. You connect a Google account to reach your projects; the emulators on your computer open without one.

You connect a Google account from inside the app, and Flare uses your existing Google Cloud permissions. Flare does not ask you to share Firebase service account credentials.

Yes. Flare supports named Firestore databases, nested collections, and document references that only exist because they contain subcollections.

Yes, for Firestore. Add a local emulator profile in Settings, then select it like a project. Emulator connections are restricted to local addresses and never silently fall back to production.

Team plans add roles, read, write or deploy access for each environment on every database, running and rolling back migrations, team folders, shared queries and activity, named seats, and a shared monthly pool of Flare Assistant requests.

Yes, on Team and Business. There are 4 roles, and read, write or deploy access can be set for each environment, whatever database it is, so a teammate can read production and still write to staging. Team starts at 3 seats. What someone can reach in the database itself stays with the database: Google Cloud IAM for Firebase, its own users and grants for the rest.

Yes, in a team folder, on Team and Business. A connection in a team folder is shared with everyone in the team, with or without its password, end to end encrypted, so Flare's servers never see it. A team environment is the other way to share: it keeps only its name, its kind and which database it is, and each teammate links it to a connection saved on their own computer, with their own credentials.

Talk to us. We can arrange larger teams, higher usage allowances, rollout support, and pricing shaped around your organization.

Every database, with the tools to browse, query and change its data, build and check migrations, Flare Assistant with a monthly allowance, and sync across your computers. Free keeps 3 saved connections; team environments and connections in a team folder never count. Backups and Compare start on Solo, and running migrations on Team.

Your account moves to the Free plan when the period you paid for ends. Your projects, connections, saved queries and drafts stay exactly as they were. If you have more than 3 saved connections, every one stays and opens as before; you can add another once you are back under 3. Your backup files stay on your computer, and scheduled backups wait until you upgrade again.

Yes. Team owners and admins can manage subscription seats through the billing portal. Your active seat allocation is synchronized from Stripe.

Team owners and admins open Stripe's billing page from Settings, Teams in the Flare app, where every invoice can be viewed and downloaded.

A request is one thing you ask the Assistant for: a query, an explanation, a fix, an optimisation or a completion. Free and Solo plans receive a monthly allowance, while Team and Business requests draw from a shared allowance based on paid seats.

Your question, the query in the editor, and the shape of your database: its tables or collections, their fields and types, keys and indexes. Never your host, user or password, and no rows unless you attach them or turn on sample values.

Plugins add dashboard widgets, table tools, commands and query result views, and themes change the colours of the whole app. A plugin runs in a sandbox and never sees your passwords: it asks Flare for data, and Flare checks what you allowed it when you installed it. Its writes ask first on production and go into your activity log, as yours do, and it cannot read or write a production database itself until you allow it. Flare installs plugins only from its store, where any plugin that can read or change data, or reach the network, is reviewed by a person first.

No. Flare connects to your databases from your computer, and your data travels directly between the two. Team features store only the collaboration data needed to provide them, such as shared queries and the activity feed, which records the changes you make and the queries you run.

Check that your computer can reach the host and port, and that the database accepts connections from your address. If the server requires SSL, set SSL to Required. Test on the connection form says what went wrong.

First confirm that your Google account has access to the project and that the correct Firestore database or emulator profile is selected. Refresh the workspace after changing permissions.