Integrations
Connect the services your app needs
Workspace-level connections for databases, AI providers, payments, email and hosting, plus GitHub for source control. Credentials are encrypted at rest, tested before they are saved, and never sent to the browser.
Available means an adapter exists in Codexa today (9 integrations). Planned means it is on the roadmap and nothing can be connected yet (9). We do not list integrations we have not built.
- AI providersStatus: Available
Anthropic
Use your own Anthropic API key (Claude) for generation in this workspace.
- Test the connection from workspace settings before saving
- Bring your own API key for this workspace's AI runs
- AI providersStatus: Available
OpenAI
Use your own OpenAI API key for generation in this workspace.
- Test the connection from workspace settings before saving
- Bring your own API key for this workspace's AI runs
How connections work
Three kinds of configuration, each with a clear owner.
- Workspace connections
- Admins add PostgreSQL, Supabase, OpenAI, Anthropic, Stripe, Razorpay, Resend and Vercel under Settings → Integrations. Every project in the workspace can use them.
- Account links
- GitHub is linked per user through OAuth, then used to import repositories and push commits from any project you can edit.
- Operator infrastructure
- Sandbox drivers (Linux namespaces by default; Docker and E2B drivers exist for the runner service), the GitHub OAuth app and default AI keys are configured by whoever hosts Codexa through environment variables, not through this directory.
- Project environment variables
- Secrets a generated app needs at runtime are stored encrypted per project and injected into the sandbox. See the environment variables guide.
Missing a service you rely on? Request an integration or read the integrations documentation.
Connect your stack
Create a free account, add a database or AI key to your workspace, and start building against real services.