Bring the account
Connect your provider account, project or scoped API credentials instead of inheriting a hidden dependency.
Accept payments, teach live, choose your AI provider and run communication through services you control—without turning your academy into a collection of disconnected tools.
Academy connection map
One workflow, provider choice underneath
18
connection options
7
integration categories
4
AI provider choices
1
connected academy
Featured connections
Connect the infrastructure, intelligence and delivery services that make your academy distinctly yours.
Connect your Stripe account
Use your Stripe account to accept payments for courses, memberships, bundles and recurring access while AcademyLauncher keeps purchases connected to learner entitlements.
Explore integrationConnect your Google account
Use Google Meet links inside AcademyLauncher workshops, instructor sessions and cohort schedules so learners find live teaching where they already learn.
Explore integrationBring your OpenAI API key
Connect an OpenAI API key to approved AcademyLauncher AI workflows while keeping provider usage, billing and credential rotation under your control.
Explore integrationConnect your Supabase project
Bring your own Supabase environment for authentication, PostgreSQL data and file storage while AcademyLauncher provides the complete academy application.
Explore integrationBring your Resend API key
Connect Resend credentials for transactional academy messages and keep domains, sending reputation, usage and provider billing under your control.
Explore integrationConnect a compatible AI client
Use AcademyLauncher’s MCP server to connect compatible AI clients to defined academy tools, with role, permission and human-approval boundaries around consequential work.
Explore integrationA clearer kind of integration
AcademyLauncher keeps each connection explicit, replaceable and tied to the academy workflows where it creates value.
Connect your provider account, project or scoped API credentials instead of inheriting a hidden dependency.
Usage and provider fees remain visible in the account your academy manages directly.
Rotate credentials, revoke access or move to another supported provider as the academy evolves.
Integration directory
Sell in the markets you serve
Connect established payment providers to sell courses, memberships, events and recurring access.
Connect your Stripe account
Use your Stripe account to accept payments for courses, memberships, bundles and recurring access while AcademyLauncher keeps purchases connected to learner entitlements.
Explore integrationBring your Razorpay credentials
Connect Razorpay to offer familiar regional payment experiences and keep enrollment access synchronized with successful academy purchases.
Explore integrationConnect your PayPal account
Add PayPal to your academy checkout mix and connect confirmed payments to the products and learning access purchased by each customer.
Explore integrationBring people together live
Create live-class experiences around the meeting platform your instructors and learners already know.
Connect your Google account
Use Google Meet links inside AcademyLauncher workshops, instructor sessions and cohort schedules so learners find live teaching where they already learn.
Explore integrationConnect your Zoom account
Connect Zoom with workshops, cohort calendars and instructor-led programs instead of distributing meeting details through disconnected tools.
Explore integrationConfigure your Jitsi service
Use Jitsi for browser-based live learning and connect session links to the AcademyLauncher experiences learners and instructors already use.
Explore integrationChoose your intelligence layer
Bring an approved AI provider key and select the model family that fits each academy workflow.
Bring your OpenAI API key
Connect an OpenAI API key to approved AcademyLauncher AI workflows while keeping provider usage, billing and credential rotation under your control.
Explore integrationBring your Gemini API key
Connect Google Gemini as an AI provider for supported creation, assistance and operational tasks without locking the academy to one model family.
Explore integrationBring your Anthropic API key
Use Anthropic Claude within supported AcademyLauncher workflows while keeping control of the API account, usage and enabled use cases.
Explore integrationBring your Kimi API key
Connect a supported Kimi model through your provider credentials and use it in eligible AcademyLauncher AI workflows.
Explore integrationOwn the infrastructure underneath
Connect customer-controlled data and delivery services without giving up the AcademyLauncher experience.
Connect your Supabase project
Bring your own Supabase environment for authentication, PostgreSQL data and file storage while AcademyLauncher provides the complete academy application.
Explore integrationBring your Bunny credentials
Connect customer-managed BunnyCDN credentials to deliver course media through infrastructure and billing controlled by your academy.
Explore integrationCommunicate through your accounts
Send transactional email, reminders and SMS through credentials and provider relationships you control.
Bring your Resend API key
Connect Resend credentials for transactional academy messages and keep domains, sending reputation, usage and provider billing under your control.
Explore integrationConfigure your email provider
Use configurable email-provider credentials where supported so your academy can keep its sending identity and provider relationship.
Explore integrationConfigure an approved SMS gateway
Connect supported SMS API gateway credentials for reminders, verification and operational messages without forcing every academy into one regional provider.
Explore integrationProtect deliverability
Validate addresses before important campaigns and reduce avoidable bounces in your audience data.
Bring your Reoon API key
Connect Reoon to check addresses before high-value communications and improve the quality of learner and lead data entering your workflows.
Explore integrationBring your NeverBounce API key
Use your NeverBounce account to validate addresses in supported AcademyLauncher workflows before messages affect deliverability and sender reputation.
Explore integrationMake the academy agent-ready
Connect compatible assistants and automations to clearly defined AcademyLauncher capabilities.
AcademyLauncher’s MCP server is designed to make defined academy tools available to compatible AI clients while preserving role, permission and human-approval boundaries.
Permission-aware connection
Agent → MCP → Academy tool
Integration questions
You do. When an integration uses customer-supplied credentials or an account connection, the provider relationship and billing remain with your academy.
Supported connections are designed to be revocable and replaceable. The exact switching process depends on the provider and the AcademyLauncher workflows using it.
AcademyLauncher is being designed around provider choice so academies can select supported model families for different requirements instead of being locked to one vendor.
No. The intended model is scoped tools, user roles, explicit permissions and human approval around consequential actions—not unrestricted database access.
Start with the services you already trust and expand the connection map as your learners, team and business grow.