Platform architecture
TaruviBase is a hosted backend for your applications. You organize work into organizations, sites, and apps, then reach each app through TaruviBase Console, the SDKs, the REST API, or an AI coding tool.
Organizations, sites, and apps
- An organization is your account. It owns sites, members, and billing.
- A site is an environment, such as development or production. Each site has its own web address, its own users, and its own data, kept separate from every other site.
- An app is one application inside a site. It holds that application's data tables, storage buckets, functions, event subscriptions, secrets, analytics queries, roles, and policies.
See Tenancy and request scope for how a request reaches the right site and app.
Ways to reach your app
| Interface | Use it to |
|---|---|
| TaruviBase Console | Create sites and apps, design tables, manage users and policies, and inspect data |
| JavaScript and Python SDKs | Call TaruviBase from application code |
| REST API | Call TaruviBase over HTTP at TARUVI_SITE_URL/api/… |
| MCP server | Let an AI coding tool work with your app at TARUVI_SITE_URL/mcp/ — see Build with AI |
| Hosted sign-in | Let your users sign in on pages TaruviBase serves for your site — see Users and authentication |
TARUVI_SITE_URL is your site's address. Copy it from your app's
Settings → Connect page in the Console.
Where your frontend runs
Host your application's built frontend on TaruviBase with frontend workers, or on any other host. Either way, it talks to your site through the SDKs or the REST API.