> ## Documentation Index
> Fetch the complete documentation index at: https://docs.folksbase.joselito.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment Overview

> Where each part of folksbase is deployed and how the pieces connect.

folksbase is split across four platforms. Each handles a different part of the stack, and all deploy automatically on push to `main`.

## Deployment Targets

| App / Service        | Platform | URL                                                                | Trigger                                         |
| -------------------- | -------- | ------------------------------------------------------------------ | ----------------------------------------------- |
| Web app (`apps/web`) | Vercel   | [folksbase.joselito.dev](https://folksbase.joselito.dev)           | Push to `main`                                  |
| API (`apps/api`)     | Render   | Backend API                                                        | Push to `main`                                  |
| Docs (`apps/docs`)   | Mintlify | [docs.folksbase.joselito.dev](https://docs.folksbase.joselito.dev) | Push to `main` (auto-sync)                      |
| Storybook            | Netlify  | Component docs                                                     | Push to `main` (component/storybook paths only) |

## How They Connect

```mermaid theme={"dark"}
graph LR
    A[Vercel — Web App] -->|API calls| B[Render — API]
    B -->|Queries| C[Neon — Postgres]
    B -->|Cache / Rate Limit| D[Upstash — Redis]
    B -->|File Storage| E[Vercel Blob]
    B -->|Background Jobs| F[Inngest]
    B -->|Auth| G[Supabase Auth]
    B -->|Email| H[Resend]
    B -->|AI| I[Anthropic]
```

## Supporting Services

These managed services are used by the API but aren't "deployed" in the traditional sense — they're configured once and accessed via environment variables.

| Service               | Purpose                                     | Provider    |
| --------------------- | ------------------------------------------- | ----------- |
| Database              | Postgres (serverless, HTTP driver)          | Neon        |
| Cache & Rate Limiting | Redis                                       | Upstash     |
| File Storage          | CSV uploads and exports                     | Vercel Blob |
| Background Jobs       | Async processing (imports, exports, emails) | Inngest     |
| Authentication        | User auth and session management            | Supabase    |
| Email                 | Transactional emails                        | Resend      |
| AI                    | CSV column mapping suggestions              | Anthropic   |

## Preview Deploys

Every pull request gets a Vercel preview URL automatically. Playwright E2E tests run against this preview URL in CI, so you get full integration testing before merging.

Render does not create preview environments on PRs — the API is tested via unit tests in CI.

## Next Steps

* [Environment Variables](/deployment/environment) — all the env vars you need to configure
* [Vercel Deployment](/deployment/vercel) — deploying the web app
* [Render Deployment](/deployment/render) — deploying the API
* [CI/CD](/deployment/ci-cd) — GitHub Actions workflows
* [Troubleshooting](/deployment/troubleshooting) — common deployment issues