Vibecode n8n Cloud
track this build5 steps, step by step0%YES · one-shottable
Because n8n itself is open source, the core cloud subscription can be replaced by self-hosting if you can own hosting, updates, and backups.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of n8n Cloud. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # n8n Cloud indie build ## Goal Build the smallest trustworthy replacement for the core n8n Cloud workflow for one developer or a tiny team. ## Scope Self-host n8n, connect credentials, create workflows, and run a small VPS with backups. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed hosting - backups - scaling - email support - reduced ops burden - team/admin features If those capabilities are essential, use n8n instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a self-hosted n8n setup to replace n8n Cloud. Requirements: - Do not rebuild the tool, n8n is open source. Set it up properly on my VPS instead. - Docker Compose: the official n8n image with SQLite storage (fine at personal scale, skip Postgres), a named volume for /home/node/.n8n, restart unless-stopped. - n8n binds to 127.0.0.1 only, published through my existing reverse proxy on an HTTPS subdomain; n8n's own user management guards the editor. - Set N8N_ENCRYPTION_KEY explicitly in .env and tell me to back that key up separately. Losing it orphans every stored credential, say so loudly. - Webhook env vars (WEBHOOK_URL) set to the public subdomain so external services can call my workflows. - Nightly backup script: export workflows and credentials with n8n's CLI plus copy the data volume to backups/YYYY-MM-DD/, keep 14 days. - An update script that pins a version tag, backs up first, then pulls and restarts. Never run :latest blind. - Import two starter workflows as JSON smoke tests: an RSS-to-email digest and a webhook-to-Telegram alert. - Out of scope: multi-user teams and high-availability scaling. This is one person's automation box. - README: first-boot owner account, a backup restore drill, and the update routine. Ops is the subscription being replaced here. ## Required capabilities - VPS or Docker host - domain/HTTPS - database/storage - backups - API credentials - update routine ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of n8n Cloud. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # n8n Cloud indie build ## Goal Build the smallest trustworthy replacement for the core n8n Cloud workflow for one developer or a tiny team. ## Scope Self-host n8n, connect credentials, create workflows, and run a small VPS with backups. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed hosting - backups - scaling - email support - reduced ops burden - team/admin features If those capabilities are essential, use n8n instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build me a self-hosted n8n setup to replace n8n Cloud. Requirements: - Do not rebuild the tool, n8n is open source. Set it up properly on my VPS instead. - Docker Compose: the official n8n image with SQLite storage (fine at personal scale, skip Postgres), a named volume for /home/node/.n8n, restart unless-stopped. - n8n binds to 127.0.0.1 only, published through my existing reverse proxy on an HTTPS subdomain; n8n's own user management guards the editor. - Set N8N_ENCRYPTION_KEY explicitly in .env and tell me to back that key up separately. Losing it orphans every stored credential, say so loudly. - Webhook env vars (WEBHOOK_URL) set to the public subdomain so external services can call my workflows. - Nightly backup script: export workflows and credentials with n8n's CLI plus copy the data volume to backups/YYYY-MM-DD/, keep 14 days. - An update script that pins a version tag, backs up first, then pulls and restarts. Never run :latest blind. - Import two starter workflows as JSON smoke tests: an RSS-to-email digest and a webhook-to-Telegram alert. - Out of scope: multi-user teams and high-availability scaling. This is one person's automation box. - README: first-boot owner account, a backup restore drill, and the update routine. Ops is the subscription being replaced here. ## Required capabilities - VPS or Docker host - domain/HTTPS - database/storage - backups - API credentials - update routine ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of n8n Cloud. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # n8n Cloud product brief ## Problem Because n8n itself is open source, the core cloud subscription can be replaced by self-hosting if you can own hosting, updates, and backups. ## Product outcome Self-host n8n, connect credentials, create workflows, and run a small VPS with backups. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - VPS or Docker host - domain/HTTPS - database/storage - backups - API credentials - update routine ## Explicit non-goals for v1 - managed hosting - backups - scaling - email support - reduced ops burden - team/admin features ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build me a self-hosted n8n setup to replace n8n Cloud. Requirements: - Do not rebuild the tool, n8n is open source. Set it up properly on my VPS instead. - Docker Compose: the official n8n image with SQLite storage (fine at personal scale, skip Postgres), a named volume for /home/node/.n8n, restart unless-stopped. - n8n binds to 127.0.0.1 only, published through my existing reverse proxy on an HTTPS subdomain; n8n's own user management guards the editor. - Set N8N_ENCRYPTION_KEY explicitly in .env and tell me to back that key up separately. Losing it orphans every stored credential, say so loudly. - Webhook env vars (WEBHOOK_URL) set to the public subdomain so external services can call my workflows. - Nightly backup script: export workflows and credentials with n8n's CLI plus copy the data volume to backups/YYYY-MM-DD/, keep 14 days. - An update script that pins a version tag, backs up first, then pulls and restarts. Never run :latest blind. - Import two starter workflows as JSON smoke tests: an RSS-to-email digest and a webhook-to-Telegram alert. - Out of scope: multi-user teams and high-availability scaling. This is one person's automation box. - README: first-boot owner account, a backup restore drill, and the update routine. Ops is the subscription being replaced here. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted n8n Cloud capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# n8n Cloud indie build ## Goal Build the smallest trustworthy replacement for the core n8n Cloud workflow for one developer or a tiny team. ## Scope Self-host n8n, connect credentials, create workflows, and run a small VPS with backups. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - managed hosting - backups - scaling - email support - reduced ops burden - team/admin features If those capabilities are essential, use n8n instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build me a self-hosted n8n setup to replace n8n Cloud. Requirements: - Do not rebuild the tool, n8n is open source. Set it up properly on my VPS instead. - Docker Compose: the official n8n image with SQLite storage (fine at personal scale, skip Postgres), a named volume for /home/node/.n8n, restart unless-stopped. - n8n binds to 127.0.0.1 only, published through my existing reverse proxy on an HTTPS subdomain; n8n's own user management guards the editor. - Set N8N_ENCRYPTION_KEY explicitly in .env and tell me to back that key up separately. Losing it orphans every stored credential, say so loudly. - Webhook env vars (WEBHOOK_URL) set to the public subdomain so external services can call my workflows. - Nightly backup script: export workflows and credentials with n8n's CLI plus copy the data volume to backups/YYYY-MM-DD/, keep 14 days. - An update script that pins a version tag, backs up first, then pulls and restarts. Never run :latest blind. - Import two starter workflows as JSON smoke tests: an RSS-to-email digest and a webhook-to-Telegram alert. - Out of scope: multi-user teams and high-availability scaling. This is one person's automation box. - README: first-boot owner account, a backup restore drill, and the update routine. Ops is the subscription being replaced here. ## Required capabilities - VPS or Docker host - domain/HTTPS - database/storage - backups - API credentials - update routine ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# n8n Cloud product brief ## Problem Because n8n itself is open source, the core cloud subscription can be replaced by self-hosting if you can own hosting, updates, and backups. ## Product outcome Self-host n8n, connect credentials, create workflows, and run a small VPS with backups. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - VPS or Docker host - domain/HTTPS - database/storage - backups - API credentials - update routine ## Explicit non-goals for v1 - managed hosting - backups - scaling - email support - reduced ops burden - team/admin features ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build me a self-hosted n8n setup to replace n8n Cloud. Requirements: - Do not rebuild the tool, n8n is open source. Set it up properly on my VPS instead. - Docker Compose: the official n8n image with SQLite storage (fine at personal scale, skip Postgres), a named volume for /home/node/.n8n, restart unless-stopped. - n8n binds to 127.0.0.1 only, published through my existing reverse proxy on an HTTPS subdomain; n8n's own user management guards the editor. - Set N8N_ENCRYPTION_KEY explicitly in .env and tell me to back that key up separately. Losing it orphans every stored credential, say so loudly. - Webhook env vars (WEBHOOK_URL) set to the public subdomain so external services can call my workflows. - Nightly backup script: export workflows and credentials with n8n's CLI plus copy the data volume to backups/YYYY-MM-DD/, keep 14 days. - An update script that pins a version tag, backs up first, then pulls and restarts. Never run :latest blind. - Import two starter workflows as JSON smoke tests: an RSS-to-email digest and a webhook-to-Telegram alert. - Out of scope: multi-user teams and high-availability scaling. This is one person's automation box. - README: first-boot owner account, a backup restore drill, and the update routine. Ops is the subscription being replaced here. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted n8n Cloud capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay to avoid maintaining an automation server that their business workflows depend on.
xmanaged hosting
xbackups
xscaling
xemail support
xreduced ops burden
xteam/admin features
share on X ↗"I just replaced n8n Cloud ($27.73/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Activepieces Community EditionA genuinely open-source workflow runner with a simpler one-container path.open source↗
AutomatischA smaller AGPL automation server for people who do not need n8n's entire ecosystem.open source↗
n8n Community EditionThe same workflow engine without the cloud bill; you inherit updates, backups, and uptime.free↗all 3 free alternatives to n8n Cloud →· no votes, no pay-to-list · just what's real
n8n Cloud pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| community edition (self-hosted) | $0/workspace | $0/workspace | Unlimited workflows, steps and users in the software; hosting, database and operations are user-supplied. |
| starter (cloud) | $27.73/workspace | $23.11/workspace | 2,500 executions/month, 1 project, 5 concurrent executions, 2,300 AI credits/month, 7-day logs and 2.5 GB stored execution data. |
| pro (cloud) | $69.33/workspace | $57.77/workspace | 10,000 executions/month, 3 projects, 20 concurrent executions, up to 13,700 AI credits/month, 30-day logs and 25 GB stored execution data. |
| business (self-hosted) | — | $770.72/workspace | 40,000 executions/month, 6 projects and 30-day insights; self-hosting required. |
| enterprise | custom | — | Custom executions, unlimited projects, 200+ concurrency and up to 365-day insights. |
free tierno free n8n Cloud plan; Community Edition is free to self-host with unlimited workflows/users, but infrastructure is not included
billingStarter/Pro monthly + annual; Business published annual price; 14-day Business trial and no-card Starter/Pro trial; VAT/tax may apply
hidden costsAn execution is one complete workflow run regardless of steps. AI credits reset and expire monthly, cannot be carried over or purchased separately. Business overage is €4,000 (about $4,622.00) per additional 300,000 executions; no prorated refunds.
verified 2026-08-11 · source ↗
Is n8n Cloud free?
No free cloud plan, just a trial; self-hosting the open source core is free. Paid is Starter (Cloud) at $27.73/mo (checked 2026-08-11).
Vibecode n8n Cloud
Yes. A competent AI coding agent (Claude Code, Codex, Cursor) can build a usable personal n8n Cloud replacement in one session with the prompt on this page. It runs on your own machine or server with no subscription.
How much does n8n Cloud cost?
n8n Cloud costs about $27.73/month (Starter (Cloud), checked 2026-08-11), which is $332.76 per year. That's what you save by replacing it with one prompt.
What do I lose by replacing n8n Cloud?
Honestly: managed hosting; backups; scaling; email support; reduced ops burden; team/admin features. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to n8n Cloud?
Yes: Activepieces Community Edition (A genuinely open-source workflow runner with a simpler one-container path.) Automatisch (A smaller AGPL automation server for people who do not need n8n's entire ecosystem.) n8n Community Edition (The same workflow engine without the cloud bill; you inherit updates, backups, and uptime.) All 3 curated free alternatives are at vibecodeit.com/n8n-cloud/alternatives. The prompt is for when you want it exactly your way.