Glossary
The terms used across Sovaria's console, API and docs, in one place.
| Term | Meaning |
|---|---|
| Organization | Holds your team, billing and projects. |
| Project | One backend: its database, users, storage, functions, keys and settings. Projects never share data. |
| Environment | An extra database for a project (staging, preview…) with its own functions, policies and API URL — see Environments, staging and deploying to production. |
| API version | An environment labelled v2, v3… that stays live next to production (v1), so old and new app builds both keep working — see API versions: run v1 and v2 side by side. |
| Project URL | https://<project-ref>.sovaria.in — where your app sends every request. |
| Anon key | Public key for browsers and apps; does only what your policies allow — see API keys. |
| Service role key | Server-only key that bypasses policies. Never ship it to clients. |
| App user | A user of your app (signs up through your project). Different from a team member. |
| Team member | Someone with access to the Sovaria console for your organization. |
| App role | A role you give app users (for example librarian), used in policies as app:<role>. |
| Access policy | A rule in Sovaria's policy language deciding whether a caller may use a table, collection, bucket, channel or function — see Security, policies and audit. |
| Row-level security (RLS) | Postgres rules deciding which rows a caller sees and changes — see Row-level security and access. |
| Simulation | Requests sent as each user type to check access, without writing data — see Simulate access before you ship. |
| User type (persona) | Who a simulation acts as: not signed in, signed-in user, an app role, or a team role. |
| Timeline, commit | The recorded history of your project's configuration — see Version history: see, undo and restore changes. |
| Staging first | Setting that sends schema changes to staging until you deploy them to production. |
| Allowed origins | The websites that may call your API from a browser — see Allowed origins (CORS) for browser apps. |
| Log drain | Forwarding of request and function logs to an external tool — see Logs and log drains. |
| Migration | A recorded, ordered schema change, ideally with down SQL to undo it — see Migrations. |
| Gateway | The single entry point that checks every request before an engine runs it. |
| Sovariq | Sovaria's AI assistant; it uses the same API and your permissions. |
Something unclear or missing on this page?Tell us