Codapult keeps provider-specific behavior behind adapters. Select a provider through the environment configuration, then verify its required credentials with npx @codapult/cli env check.
Core providers
| Capability | Choices | Default | Production guidance |
|---|---|---|---|
| Database | Turso/libSQL, PostgreSQL | Turso/libSQL | Use PostgreSQL or Turso cloud according to query, hosting, and operational needs. Keep both schemas in sync. |
| Authentication | Better-Auth, Kinde, none | Better-Auth | none is for landing-mode or intentionally public projects, not an authenticated SaaS. |
| Payments | Stripe, LemonSqueezy, Polar | Stripe | Configure the provider's secret and webhook signing secret; test signed webhooks before launch. |
| SSO | BoxyHQ Jackson SAML, none | none | Run a real identity-provider acceptance flow for production SSO. |
| Storage | Local, S3, R2 | Local | Local storage is convenient for development; use durable object storage for production uploads. |
| Jobs | In-memory, BullMQ/Redis, none | In-memory | Use BullMQ/Redis for durable retries and multi-instance workers. |
| Notifications | Polling, SSE, WebSocket | Polling | Choose SSE or WebSocket when the product needs live updates and configure the corresponding transport. |
| Support | Crisp, Intercom, none | none | Add the provider credentials only when support is part of the product experience. |
AI providers and storage
| Capability | Choices | Default | Notes |
|---|---|---|---|
| AI models | OpenAI, Anthropic, Google, Groq, Together, custom OpenAI-compatible endpoint | Configured model/provider | The gateway uses the model registry and can apply allow-lists, fallback, retries, metering, and guardrails. |
| Embeddings | OpenAI, Ollama | OpenAI | Ollama is useful for local development and self-hosted embedding workloads. |
| Vector store | SQLite, memory | SQLite | Memory is intended for tests or short-lived processes; it is not a durable production index. |
Provider selection gives each capability its deployment path. Complete the provider credentials, webhook setup, Redis, object-storage lifecycle, model selection, and deployment configuration for the product you are launching. See database/provider limitations and enterprise production readiness.
For the complete capability picture and the evidence behind each foundation area, see Capability Coverage.
Accounts you bring
Codapult provides the application integration and configuration surface. The production accounts themselves remain yours to create and operate: hosting, database, payment processor, email delivery, object storage, Redis, AI model providers, SAML identity provider, monitoring, and domain/DNS services. Start locally with the built-in file database and development adapters, then add only the accounts required by the capabilities your product keeps.