Introduction
What Flares Cloud is: projects, Basket DB, Auth and Functions.
Flares Cloud is a developer platform organised around projects. A project is the unit of everything: it holds your data, your users, your functions, your API keys, your team and your bill. Inside a project you enable the services you need:
- Basket DB — a realtime application database: collections, records, security rules, live subscriptions. Powered by Fareedah, Flares' managed data layer.
- Auth — authentication for the users of your application: email & password, one-time codes, sessions, verification, resets.
- Functions — PHP backend code deployed to an isolated runtime, served over HTTPS, billed per request.
Storage and Hosting are planned services. They appear in the console marked Coming soon and nothing about them is usable yet — this documentation describes only what exists.
Two kinds of accounts, deliberately separate
Your Flares Account signs into the Cloud console at
cloud.flaresinc.com. It identifies you, the developer, and the teammates you invite.
Your application's users live in your project's Auth user pool. They have no Flares Account, cannot open the console, and exist only inside your project. The same email address in two projects is two unrelated identities. This separation is a security boundary, not an implementation detail — nothing you do in Auth can grant anyone access to Flares itself.
How the pieces fit
Your frontend ── public key ──▶ Basket DB (rules decide per record)
│ ▲
│ sign in │ access token: rules see auth.user.id
▼ │
Flares Auth ──────────────────────┘
│
▼ access token
Your functions ◀── HTTPS ── anyone (public) or verified users (auth mode)Start with the quickstart — it walks the whole loop in one sitting.