Database, sign-in and file storage for your app from open-source Supabase, on a PostgreSQL database Ghaym manages; Ghaym is not affiliated with Supabase.

What it creates

NameKindDefault sizeA month in amman-1
supabaseWeb serviceSmallJOD 18.000
supabase-dbPostgreSQL databaseDatabase 1GBJOD 9.000
supabase-files-<suffix>BucketJOD 0.100 per GB
Total, before storageJOD 27.000

The supabase service runs seven containers together, with one size and one address:

  • gateway: the entry. Every request goes through it.
  • auth: sign-in and users.
  • rest: a REST API for your tables.
  • realtime: live updates.
  • storage: files, kept in the template's bucket.
  • meta: reads the database's structure for Studio.
  • studio: the Supabase dashboard.

What you set after launch

  • Copy SERVICE_ROLE_KEY and DASHBOARD_PASSWORD from the screen that shows after you apply. They don't show again.
  • The public key ANON_KEY is in supabase's Variables, and you can read it any time.
  • Set GOTRUE_SITE_URL in supabase's Variables to your app's address, so users return to it after confirming their email.
  • Set SUPABASE_PUBLIC_URL in supabase's Variables to the service's public address, so email confirmation links point to it.
  • To change the mail server later, edit the GOTRUE_SMTP_* Variables in supabase.
  • The database connection string's user is ghaym. Supabase's guides say postgres; on Ghaym, use ghaym.
  • GraphQL is off at first. To turn it on, run create extension pg_graphql; in Studio's SQL editor.
  • A Realtime digest newer than the template's may fail its migrations: they need a role the database withholds.

Open Studio

Open supabase's address in a browser. The username is supabase, and the password is DASHBOARD_PASSWORD.

Move a project in

To bring a self-hosted Supabase project's database, files and keys to Ghaym, follow Move from self-hosted Supabase.