Workflow 1
Customer-controlled authentication
Connect this capability to the academy context instead of managing it as a separate operational island.
SB
Available
Data and media integration
Run your academy on a Supabase project you control
Bring your own Supabase environment for authentication, PostgreSQL data and file storage while AcademyLauncher provides the complete academy application.
Keep academy records in your project
Control authentication and storage infrastructure
Retain the ability to inspect and manage your data
Connected workflow
Connect your Supabase project
SB
Supabase
Your provider account
AL
AcademyLauncher
Connected academy workflow
Credential
Project URL and scoped credentials
Billing
Supabase plan remains yours
Control
Own the underlying project
What you can connect
Make Supabase part of the learner journey
Use the provider where it creates value while AcademyLauncher keeps the workflow connected to users, products, learning and operations.
Workflow 2
Academy data and application records
Connect this capability to the academy context instead of managing it as a separate operational island.
Workflow 3
Uploads and file storage
Connect this capability to the academy context instead of managing it as a separate operational island.
Connection process
From provider account to academy workflow
The exact authorization fields vary by provider, but the ownership model remains clear throughout setup.
01
Choose the connection
Select Supabase from the AcademyLauncher integration settings for the academy you are configuring.
02
Authorize securely
Complete the connect your supabase project process and provide only the access required for supported workflows.
03
Test the workflow
Confirm the connection before enabling Supabase for instructors, learners or live academy operations.
04
Stay in control
Monitor the provider account and rotate, revoke or replace the connection whenever your academy requires it.
Ownership and trust
A connection should remain understandable and reversible
Provider integrations are most useful when your team knows which account is connected, what it enables and how to remove or replace it.
- Project URL and scoped credentials identifies the connection
- Supabase plan remains yours
- Own the underlying project
- Access should be limited to supported academy workflows
The AcademyLauncher standard
Your connection—not a black box
AcademyLauncher connects the provider to a useful academy experience while preserving a visible path back to the account, credential and permissions behind it.
Read our product principlesRelated connections
Build the rest of the workflow
Connect Supabase
Put Supabase to work inside your academy.
Bring the provider relationship you control and connect it to a coherent AcademyLauncher workflow.
Keep academy records in your project
Control authentication and storage infrastructure
Retain the ability to inspect and manage your data