Documentation

Da8a backend

Give any site a database, auth, file storage and edge functions. Da8a projects speak the Supabase APIs, so the tools you know work unchanged.

One-click database

  1. Open your site in the dashboard and go to the Storage tab.
  2. Create a Da8a database. Chapong provisions the project and links it to the site.
  3. The backend’s URL and public key are added to the site’s environment, and its auth redirect URLs are kept in sync with your site’s addresses, including preview deploys.
  4. Redeploy so the build picks up the new variables.

On an own-server plan the backend can run on the same server as your sites.

Use it from your app

src/lib/db.ts
import { createClient } from '@supabase/supabase-js';
export const db = createClient(import.meta.env.VITE_SUPABASE_URL, import.meta.env.VITE_SUPABASE_ANON_KEY);

The linked backend’s URL and anon key arrive as SUPABASE_URL and SUPABASE_ANON_KEY (see environment variables); in a Vite app, map them to VITE_ names as above. Keep the service_role key on servers only: it bypasses Row Level Security.

Manage the backend

Open the project in the Da8a dashboard for tables, auth settings, storage buckets and SQL. From the terminal, the avoca CLI uses the same layout as the Supabase CLI:

shell
$ avoca projects list
$ avoca link --project-ref <project-id>
$ avoca migration new create_todos
$ avoca db push --dry-run
$ avoca db push
$ avoca functions deploy hello
$ avoca secrets set OPENAI_API_KEY=sk-…
$ avoca keys

Migration history is stored in supabase_migrations.schema_migrations, the same table the Supabase CLI uses. Each migration runs in one transaction. Function secret names starting with SUPABASE_ are reserved.

Templates

The Business website and Client portal templates create their Da8a database and apply their schema for you.