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

# Prerequisites

> Account requirements, cloud infrastructure dependencies, and local development tools for toorow.

Before deploying or developing with **toorow**, ensure you have prepared the required cloud services and local development tooling.

<Note>
  **toorow** is designed for containerized cloud deployment on **Google Cloud Platform (Cloud Run)** with **Nango** and **PostgreSQL**. A local sandbox is also available for development. See [Self-Hosting Guide](/self-hosting) for full deployment steps.
</Note>

## 1. Account & Infrastructure Prerequisites

The following table summarizes the external accounts and managed services required to run a complete toorow instance:

| # | Service / Provider              | Purpose                                                                                                                    | Free Tier / Dev Compatibility                     |
| - | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| 1 | **GitHub Account**              | Access the repository and manage GitHub Actions CI/CD workflows.                                                           | Yes                                               |
| 2 | **PostgreSQL 15+**              | Platform database for connections, governance, audit logs, and job queue (`PLATFORM_DB_URL`).                              | Yes (Supabase free tier or local Docker Postgres) |
| 3 | **Google Cloud Platform (GCP)** | BigQuery analytical warehouse, Cloud Run container hosting, Secret Manager, and Google OAuth APIs (GA4, GSC, Sheets, Ads). | Yes (within GCP free tier quotas)                 |
| 4 | **Nango Broker**                | OAuth broker for non-Google connectors (Meta Ads, TikTok, LinkedIn, Shopify, Stripe, Klaviyo).                             | Yes (Nango Cloud free tier or self-hosted Docker) |
| 5 | **Langfuse** *(optional)*       | OpenTelemetry tracing and evaluation for MCP tool calls.                                                                   | Yes (Cloud free tier or self-hosted Docker)       |

### GCP Project Setup Prerequisites

When preparing your GCP project for production or staging deployment:

1. **GCP Billing Account**: A linked GCP billing account is mandatory to enable BigQuery and Cloud Run APIs (Human Gate).
2. **Artifact Registry**: A Docker repository named `connector` in region `europe-west1` (`europe-west1-docker.pkg.dev/<PROJECT_ID>/connector`).
3. **Secret Manager**: Secrets created for `NANGO_ENCRYPTION_KEY` and optional static/JWT tokens.
4. **Workload Identity Federation (WIF)**: A configured WIF Pool (`github-pool`) and Provider (`github-provider`) for keyless GitHub Actions CI/CD deployments.

***

## 2. Local Development Tooling Prerequisites

To build, test, or run toorow locally, the following development environment tools are required:

| Tool                 | Version Requirement       | Purpose                                                                     |
| -------------------- | ------------------------- | --------------------------------------------------------------------------- |
| **Python**           | `3.12`                    | Core backend runtime and FastMCP server.                                    |
| **uv**               | Latest (`astral.sh/uv`)   | Fast Python package and environment manager.                                |
| **Node.js**          | `22.x` or higher          | Admin Console UI and MCP App widgets build environment.                     |
| **pnpm**             | `9.x` (`corepack enable`) | UI workspace package manager.                                               |
| **Docker & Compose** | Desktop or Engine 24+     | Local container runtime for PostgreSQL, Nango, and local integration tests. |
| **Terraform**        | `1.7+` *(optional)*       | Infrastructure-as-code execution for GCP BigQuery and IAM provisioning.     |

***

## Next Steps & Cross-References

<CardGroup cols={2}>
  <Card title="Quickstart Guide" icon="rocket" href="/quickstart">
    Set up and launch toorow locally in under 5 minutes.
  </Card>

  <Card title="Self-Hosting Guide" icon="server" href="/self-hosting">
    Step-by-step deployment guide and full `.env` variable reference.
  </Card>

  <Card title="Platform Constraints" icon="shield-check" href="/constraints">
    Review security rules, zero-telemetry policies, and architectural invariants.
  </Card>

  <Card title="Cloud Hosting" icon="cloud" href="/cloud-hosting">
    Examine the maintainers' managed GCP Cloud Run architecture.
  </Card>
</CardGroup>