Skip to main content
Before deploying or developing with toorow, ensure you have prepared the required cloud services and local development tooling.
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 for full deployment steps.

​
1. Account & Infrastructure Prerequisites

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

​
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:

​
Next Steps & Cross-References

Quickstart Guide

Set up and launch toorow locally in under 5 minutes.

Self-Hosting Guide

Step-by-step deployment guide and full .env variable reference.

Platform Constraints

Review security rules, zero-telemetry policies, and architectural invariants.

Cloud Hosting

Examine the maintainers’ managed GCP Cloud Run architecture.