Docs

Introduction

What Sovaria gives every project, how your app talks to it, and where to start.

Updated Oct 13, 2026

Sovaria is the backend for your app. Each project you create comes with a Postgres database, sign-in for your users, file storage, server-side functions, realtime messaging and a JSON document store. Your app reaches all of it through one URL and one key, from the browser, a mobile app, your server or the command line.

Project home in the Sovaria consoleProject home in the Sovaria console
The project home: environment, region, database health, your project URL and shortcuts to every service.

What every project includes

How your app talks to Sovaria

Your app calls your project URL, https://<project-ref>.sovaria.in, through the JavaScript SDK, the Python SDK, the sov CLI or plain HTTP. Every request goes through the same four steps:

  1. Identify — who is calling: a signed-in user's session, the public anon key, or a server-only service role key (API keys).
  2. Authorise — your project's access policies decide whether this caller may use the table, bucket, channel or function, and row-level security decides which rows (Row-level security and access).
  3. Execute — the database, storage, functions or realtime service does the work.
  4. Record — usage counts toward your plan and important actions go to the audit log.

Your team vs. your app's users

Console members (your team)App users (your customers)
WhoYou and the people you invitePeople who sign up in the app you build
Where they sign inconsole.sovaria.in or sov loginYour app, through the SDK (auth.signUp, auth.signIn, …)
Managed inOrganization → TeamProject → Users
What they can reachProjects of organizations they belong to, by roleOnly what your project's policies allow

Where to start

Something unclear or missing on this page?Tell us