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
- GitStatus: Available
GitHub
Import repositories, commit and push changes, and keep projects in sync with a branch.
- Sign in with the provider (OAuth)
- Import a repository into a project
- Commit and push project files to a branch
- 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
- DatabasesStatus: Available
PostgreSQL
Connect any PostgreSQL database: browse the schema and run queries from the workspace.
- Browse tables and columns in the schema browser
- Run SQL from the workspace, with confirmation for destructive statements
- Test the connection from workspace settings before saving
- PaymentsStatus: Available
Razorpay
Payments for India (UPI, cards, net banking) with your Razorpay account.
- Test the connection from workspace settings before saving
- EmailStatus: Available
Resend
Transactional email for generated apps.
- Test the connection from workspace settings before saving
- PaymentsStatus: Available
Stripe
Accept payments in generated apps with your Stripe account.
- Test the connection from workspace settings before saving
- DatabasesStatus: Available
Supabase
Postgres with auth, storage and realtime. Connect the database and the REST endpoint.
- Browse tables and columns in the schema browser
- Run SQL from the workspace, with confirmation for destructive statements
- Test the connection from workspace settings before saving
- HostingStatus: Available
Vercel
Deploy projects to your own Vercel account.
- Test the connection from workspace settings before saving
- Deploy a project to the provider from the Deploy panel
- StorageStatus: Planned
Amazon S3
Object storage for uploads and assets.
On the roadmap — no adapter yet.
- AuthenticationStatus: Planned
Auth0
Enterprise identity with social and SSO logins.
On the roadmap — no adapter yet.
- AuthenticationStatus: Planned
Clerk
Drop-in authentication and user management for generated apps.
On the roadmap — no adapter yet.
- StorageStatus: Planned
Cloudflare R2
S3-compatible storage without egress fees.
On the roadmap — no adapter yet.
- ProductivityStatus: Planned
Linear
Turn issues into prompts and link generations to tickets.
On the roadmap — no adapter yet.
- HostingStatus: Planned
Netlify
Static and serverless hosting.
On the roadmap — no adapter yet.
- AnalyticsStatus: Planned
Plausible
Privacy-friendly web analytics.
On the roadmap — no adapter yet.
- AnalyticsStatus: Planned
PostHog
Product analytics, session replay and feature flags.
On the roadmap — no adapter yet.
- ProductivityStatus: Planned
Slack
Deployment and activity notifications in your channels.
On the roadmap — no adapter yet.
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.