datawranglerai/self-host-n8n-on-gcr

Description and use

**Brief summary**
The *datawranglerai/self‑host‑n8n‑on‑gcr* repository provides Terraform scripts and supporting files that let you spin up a fully self‑hosted instance of n8n on Google Cloud Run, eliminating the recurring subscription fees that come with the hosted version. It’s aimed at teams that want a low‑cost, scalable automation platform for payment‑related workflows such as billing, checkout, or PSP (payment service provider) integrations.

**Value proposition**
By deploying n8n on GCR you get a powerful, open‑source orchestration engine that can be tightly coupled with your existing payment infrastructure, giving you full control over data residency, cost, and custom extensions. The ready‑made Terraform modules accelerate the setup of billing‑oriented workflows, so you can move from concept to production without building the underlying cloud plumbing yourself.

**Practical adoption path**

1. **Proof‑of‑concept** – Clone the repo, review the README, and run the provided terraform init/apply against a test GCP project. Verify that a basic n8n workflow (e.g., a Stripe webhook → Google Sheet) executes successfully.
2. **Security & licensing audit** – Confirm the MIT license meets your policy, scan the container image for vulnerabilities, and ensure any third‑party credentials are stored in Secret Manager.
3. **Incremental rollout** – Deploy the production‑grade Terraform configuration in a separate GCP project, connect it to your real payment APIs, and gradually migrate existing automation jobs.
4. **Monitoring & scaling** – Enable Cloud Logging, Cloud Monitoring, and autoscaling settings that come with the Terraform module to keep the service reliable under load.

**Production readiness**
The project scores 78/100 and shows strong OSS health signals: 600+ stars, 132 forks, recent commits (as of 2026‑05‑10), and active issue discussions. Its primary language (HCL) and well‑documented Terraform modules make integration straightforward for teams already using IaC on GCP. While no major metadata risks are flagged, a final review of the license, container security posture, and maintainer responsiveness is recommended before a full‑scale production launch. With these checks completed, the solution is considered “high” readiness for a serious pilot.

Use in a workflow

datawranglerai/self-host-n8n-on-gcr helps integrate monetization, billing, or PSP flows faster.

• integrate billing or checkout
• evaluate PSP flows
• automate payment operations

Limitations and review notes

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.