vibecodeit

Build n8n Cloud

YESreplaces $27.73/mosaves $332.76/yrback to the verdict

0%0 of 19 items done

Saved on this device only. Tick prerequisites first, then work the phases in order · do not start one until the checks above it pass.

Build an owner-operated n8n workflow instance with persistent credentials and tested recovery.

estimated effort multi-daythe files for this build are in the project pack

ApplicationUpstream n8n containerStoragePersistent upstream SQLite pilot volumeDeploymentDocker Compose; Caddy for product HTTPS

Before step 1

Everything below is assumed from the first step. Tick each one when you actually have it, not when you plan to.

  1. installDocker Engine has no hosting fee; Desktop licensing depends on your use, and a rented host is billed separately.

    Why The upstream application runs in containers.

    Get it Install Docker Engine and the Compose plugin on Linux using the official instructions. On Windows use Docker Desktop with WSL2, then work inside a Linux project folder. open ↗

    Verify docker compose version prints a v2 version and docker info reaches the daemon.

  2. decideSoftware/edition terms and optional paid features are defined by the upstream project.

    Why The guide must match the software you actually deploy.

    Get it Open https://docs.n8n.io/deploy/host-n8n/install-options/install-with-docker, choose a stable release compatible with its database requirements, record its tag and resolved digest in versions.txt, and use those values in compose.yaml. Avoid unattended latest-tag updates. open ↗

    Verify versions.txt names both application and database versions or states that the pilot uses embedded SQLite.

  3. have readyNo paid service required for this local step.

    Why This fixture makes the first end-to-end check reproducible.

    Get it Create synthetic sample data before implementation: A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records.

    Verify The fixture files and expected outcomes exist and can be inspected without a vendor account.

  4. decideNo paid service required for this local step.

    Why The full commercial product is larger than this guide.

    Get it The deliverable is an owner-operated n8n workflow instance with persistent credentials and tested recovery. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first.

    Verify You can name the primary workflow and the vendor features this version deliberately leaves out.

Data model

Create these before the first phase that stores anything. Changing a table later is the expensive kind of change.

- Use the upstream n8n schema. For the local pilot retain the entire /home/node/.n8n volume, including its SQLite database and encryption material
- keep workflow exports and pinned image digest. Product mode must rehearse the documented PostgreSQL migration/export path rather than simply changing database settings.
- Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them.
- Acceptance fixture: A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account.

Environment variables

These go in a .env file the app reads at startup. The pack's .env.example is this table as a file · copy it, never commit the filled-in version.

VariableNeededExampleWhere the value comes from
APP_IMAGErequiredreplace-with-tested-image-and-digestCopy the exact application image reference selected from upstream into compose.yaml via this variable.
SITE_URLrequiredhttp://localhost:5678The loopback URL selected in compose.yaml; replace with your HTTPS origin only after completing product deployment.
GENERIC_TIMEZONErequiredUTCSet the intended workflow timezone in the n8n service; record it beside the schedule proof.
TZrequiredUTCContainer system timezone; keep it consistent with the intended pilot timezone.

The build, in order

  1. Deployment inventory and safe pilot

    Prepare the pinned upstream deployment for an owner-operated n8n workflow instance with persistent credentials and tested recovery.

    1. Read the linked upstream installation guide and create compose.yaml, .env.example, versions.txt and OPERATIONS.md. Map APP_IMAGE and only each service's required environment variables explicitly. Keep database ports internal and map the pilot application port to 127.0.0.1.

      Files compose.yaml.env.exampleversions.txt

    2. Use the upstream n8n schema. For the local pilot retain the entire /home/node/.n8n volume, including its SQLite database and encryption material; keep workflow exports and pinned image digest. Product mode must rehearse the documented PostgreSQL migration/export path rather than simply changing database settings. Name each volume and its mount path in OPERATIONS.md; never use ephemeral container storage for the only copy. Create .env manually from .env.example and replace placeholders before starting.

      Files OPERATIONS.md.gitignore

      terminal
      docker compose config --quiet

    3. Create a private fixtures/ folder containing: A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Create a separate backup destination and an isolated restore-project name; do not reuse live volumes in restore exercises.

      Files fixtures/README.mdOPERATIONS.md

    done when · tick each as it passes
    watch out
    • A valid Compose file proves configuration syntax only, not application health.
    next phase

  2. Persistent local instance

    Persistent local instance for n8n Cloud: Deploy the official n8n image using Compose with a persistent /home/node/.n8n mount and a loopback mapping for port 5678.

    1. Deploy the official n8n image using Compose with a persistent /home/node/.n8n mount and a loopback mapping for port 5678.

      Files compose.yamlOPERATIONS.md

    2. Create the owner account and retain the generated encryption material with restricted backups; disable optional AI/cloud features for this pilot.

      Files OPERATIONS.md

    3. Use A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Check: Restarting the container retains the owner account and a saved workflow. Then check: The editor is unreachable through a non-loopback host interface. Record commands, observed results and the date in OPERATIONS.md.

      Files OPERATIONS.md

    done when · tick each as it passes
    watch out
    • Follow upstream settings for the selected release; do not copy deprecated task-runner flags from old examples.
    next phase

  3. Useful workflow proof

    Useful workflow proof for n8n Cloud: Build the Manual Trigger and Edit Fields proof, inspect output, then add a Schedule Trigger with the intended timezone.

    1. Build the Manual Trigger and Edit Fields proof, inspect output, then add a Schedule Trigger with the intended timezone.

      Files compose.yamlOPERATIONS.md

    2. Export the workflow JSON and record its expected output; keep credentials in the n8n credential store, never in exported node parameters.

      Files OPERATIONS.md

    3. Use A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Check: The manual workflow produces the exact hello field. Then check: The scheduled proof runs at the documented timezone and appears in execution history. Record commands, observed results and the date in OPERATIONS.md.

      Files OPERATIONS.md

    done when · tick each as it passes
    watch out
    • An enabled schedule is an actual side effect; test only a harmless local workflow.
    next phase

  4. Recovery and upgrade

    Recovery and upgrade for n8n Cloud: Stop the local SQLite instance for a consistent complete volume backup and store encryption material securely alongside it.

    1. Stop the local SQLite instance for a consistent complete volume backup and store encryption material securely alongside it.

      Files compose.yamlOPERATIONS.md

    2. Restore into a new isolated volume with schedules disabled, import or inspect the proof workflow and test before selecting a new image.

      Files OPERATIONS.md

    3. Use A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Check: The restored proof workflow runs and any test credential remains decryptable. Then check: The backup manifest includes the encryption material, image version and restore date. Record commands, observed results and the date in OPERATIONS.md.

      Files OPERATIONS.md

    done when · tick each as it passes
    watch out
    • Workflow JSON alone is not a backup of credentials or execution data; changing to PostgreSQL does not copy old SQLite data.
    next phase

  5. Portable delivery and clean-start proof

    Finish the n8n Cloud replacement with a documented first-run path and a recoverable export.

    1. Document prerequisites, every configuration variable, data locations and the three domain workflows: Persistent local instance; Useful workflow proof; Recovery and upgrade. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them.

      Files README.md.env.example

    2. Stop the pilot service and back up its complete persistent volume including SQLite and encryption material; retain versioned workflow exports as a secondary aid. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: A Manual Trigger to Edit Fields workflow producing hello plus a Schedule Trigger proof using no external account. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy.

      Files OPERATIONS.mdbackup/README.md

    3. Use a new folder and only README instructions to reach the fixture outcome. Verify upstream login, persistence, proof output and restore. Record exactly what passed; do not mark unrun checks complete.

      Files README.mdverification.md

      terminal
      docker compose ps
    done when · tick each as it passes
    watch out
    • Export without an import or restore rehearsal is not verified portability.
what this build does not replace
after v1, if you want it

Need the files? The project pack on the verdict page hands your agent the whole brief · more automation.