self-host-n8n-on-gcr and n8n-self-host-on-gcp-pulumi
These are competitors offering alternative Infrastructure-as-Code approaches to the same problem—one uses Docker/GCR while the other uses Pulumi—so users would choose based on their preferred IaC tooling rather than use both together.
About self-host-n8n-on-gcr
datawranglerai/self-host-n8n-on-gcr
Self-host n8n on Google Cloud without the subscription fees or server headaches - because your automation workflows shouldn't cost more than your coffee budget
Deploys n8n on Google Cloud Run with PostgreSQL backend, supporting both official and custom Docker images with startup initialization handling; includes Terraform automation for fully scripted provisioning. Integrates native Google Cloud services (Cloud SQL, Secret Manager, Artifact Registry) and OAuth authentication with Google Sheets/Drive, plus optional queue mode deployment for production scaling. Covers practical patterns like port mapping for Cloud Run's dynamic port assignment and startup delay workarounds for database race conditions.
About n8n-self-host-on-gcp-pulumi
VeVarunSharma/n8n-self-host-on-gcp-pulumi
Self-host n8n on Google Cloud via Pulumi IaaC - own your data, keep costs at minimum!
Deploys n8n to Cloud Run with Postgres backend via modular Pulumi components, enforcing least-privilege IAM through Workload Identity and storing secrets in Secret Manager. The TypeScript infrastructure includes Jest-based unit tests with Pulumi mocks, enabling safe validation of Cloud SQL bindings and service configuration without cloud credentials. Supports per-stack configuration for database tier, CPU allocation, and optional public access, scaling from ~$25/month starter setups.
Scores updated daily from GitHub, PyPI, and npm data. How scores work