Your data is the centre
You define tables in Studio, and each becomes a database table and an API at once: list, read, add, change and delete, with filters, sorting and relations. There is no server for you to write and no layer to keep in sync. See Database.People sign in
Auth knows who each person is: passwords, passkeys, social and company sign-in, two-step verification, roles and organizations. The same identity is used everywhere else, in your data, files, realtime, flows and agents. See Auth.One set of rules decides who may do what
An access rule says who can do something: “signed-in users”, “people who own the record”, “admins”, “a key with this scope”. You write a rule once and use it for tables, files, realtime channels, flows, routes, agents and models. Rules are enforced on the server, so a person can’t skip them by changing your app. See Access rules.Things happen when data changes
When something happens (a record is created, a user signs up, a payment arrives, an agent finishes), Pawabase announces it as an event. You react with:- a flow: a visual workflow that can send email, call other services, update data, ask a model or run an agent
- a webhook: a signed call to another system
- a realtime message: a live update to everyone watching
- a schedule: the same flows, on a timer