Choose how you build
Connect your application to TaruviBase with an SDK, a framework integration, or HTTP requests. Configure your site, app, and credentials once, then follow the product guide for each task.
Application SDKs
Both SDKs include modules for authentication, Database, Storage, Functions, Secrets, access policies, app settings, users, and Analytics. Each product guide shows the SDK calls available for its tasks.
JavaScript
Use @taruvi/sdk in browser apps and JavaScript servers.
- Browser apps sign users in through TaruviBase's hosted sign-in and send the user's session with each request.
- Server code uses a signed-in user's session token. For server calls made with
an API key, send HTTP requests with an
Authorization: Api-Keyheader — see JavaScript SDK.
Python
Use the taruvi package in services, jobs, scripts, and notebooks. Choose the
synchronous client for blocking code or the asynchronous client for asyncio
applications.
- Both clients expose the same product modules.
- Authenticate with an API key, a session token, or a JWT.
Framework integrations
Refine
Use the TaruviBase providers in a Refine 5 application for data, authentication, storage, users, and app services.
For Next.js, React, Vue, React Native, Node.js, and Python projects, see the framework guides.
Call the API directly
Call TaruviBase over HTTP from any language. Send requests to your site address,
TARUVI_SITE_URL, with an Authorization: Api-Key TARUVI_API_KEY header for
server-side calls. Use a REST example only when a product guide shows one for
that task. See API request lifecycle for
the response format and error handling.
New to TaruviBase?
Follow Create your first task to create a tasks
table and store a record with JavaScript or Python.
Add a capability
- Database — create tables, store records, and build queries
- Users and authentication and access policies — users, roles, policies, and permission checks
- All products — storage, functions, events, analytics, and more
Deploy your app
Deploy with GitHub Actions to publish your frontend and backend configuration on every merge.
Related
- Releases — product changes
- Version compatibility — the SDK and API versions these guides use