How to Host n8n on a New Zealand VPS

Self-hosting n8n on a New Zealand VPS gives you control over the automation environment and keeps the server close to New Zealand systems and users. A production deployment needs more than simply starting a container: plan the database, HTTPS, backups, updates and access controls before workflows become business-critical.

Choose enough capacity

Resource needs depend on workflow frequency, concurrency, payload size and the nodes being used. A small test environment can start modestly. For production, allow headroom for PostgreSQL, container overhead and temporary workflow data. Memory is usually the first resource to watch as workflow volume grows.

Use PostgreSQL for production

Use PostgreSQL rather than the default embedded database for a production service. Keep database credentials outside the compose file where possible, restrict database exposure to the private container network, and back up both the database and n8n encryption key.

Put n8n behind HTTPS

Expose the service through a reverse proxy such as Nginx, Caddy or Traefik. Use a valid TLS certificate and configure n8n's public URL and webhook URL to match the external hostname. Do not expose the editor directly on an unencrypted port.

Protect the editor and credentials

  • Use strong authentication and restrict administrative access where practical.
  • Store the n8n encryption key securely and include it in the recovery plan.
  • Limit inbound firewall rules to required ports.
  • Keep the operating system, container runtime and n8n image updated.
  • Review community nodes before installing them into a production environment.

Back up the parts required for recovery

A complete recovery set normally includes the PostgreSQL database, n8n encryption key, environment configuration, reverse-proxy configuration and any files mounted into workflows. Test restoration on a separate server so the first restore is not attempted during an outage.

Monitor the whole automation path

Monitor the VPS, container health, database, queue behaviour and important workflow outcomes. A successful HTTP health check does not prove that a workflow can reach its external systems or process credentials correctly.

Plan scaling before queues build up

When workflow concurrency increases, n8n can use queue mode with Redis and separate workers. This changes the architecture and backup requirements, so introduce it when monitoring shows a real need rather than adding complexity on day one.

A SiliconKiwi New Zealand VPS provides root access for a self-managed deployment. If you prefer an app-ready environment with a web application firewall and daily local backups, compare Kiwi Apps.