Published on · Updated on: · By Vamsi Mullapudi
- 10 min read
How to Self-Host n8n in One Click with Kuberns
n8n is one of the most capable workflow automation tools available today. It connects your apps, APIs, and services through a visual interface, and unlike cloud-only alternatives, it gives you full control over your data when self-hosted. But getting n8n running on your own server has traditionally required configuring a database, a Redis instance, reverse proxies, SSL certificates, and environment secrets before you write a single workflow.
Kuberns is an AI-Powered deployment platform that removes all of that. With the n8n one-click self-hosting template, you can have a fully operational n8n instance running on a production-grade server in under ten minutes, with zero manual infrastructure work.
This guide walks you through every step of the process using the Deploy n8n in One Click template on Kuberns.
Step 1: Select the n8n Template on Kuberns
Start by visiting Kuberns and navigating to the template library. Search for n8n and you will find the one-click self-hosted deployment template. Click on it to begin.
The template page gives you a clear overview of what is being deployed: n8n with a PostgreSQL database for persistent workflow storage and a Redis instance for queue management and caching. You also get a one-minute demo video if you want to see the process before committing.
Unlike setting up n8n from scratch on a VPS, where you would manually install Node.js, configure a Postgres database, wire up Redis, and handle process management with PM2 or systemd, this template has already solved every one of those problems. The entire stack is pre-configured and production-ready from the first click.
Step 2: Sign Up on Kuberns
If you do not already have a Kuberns account, this is where you create one. Sign up with your email address, or connect instantly using your GitHub or Google account. The onboarding process takes about two minutes.
During onboarding, Kuberns will ask a few brief questions: your name, what best describes you, and what you plan to deploy. This helps the platform tailor your experience. Once complete, you are taken directly to your workspace and you are ready to deploy.
There is no credit card required to get started. You can deploy n8n immediately on the free tier and decide later whether to upgrade as your automation workloads grow.
Step 3: Fill in Basic Project Details
After signing up, you will be taken to the project setup screen for your n8n deployment. This is where you give your project a name and select a deployment region.
You will notice the form is intentionally simple. Enter a project name such as n8n-production and choose the hosting region closest to your users or team. That is all Kuberns needs from you at this stage.
No infrastructure decisions are required here. You are not asked to choose a machine size, configure a network, or select a database engine. All of that is handled automatically behind the scenes by Kuberns AI, which understands what n8n needs to run reliably and configures the environment accordingly.
Step 4: Add the Required Environment Variable
Environment variables are the only manual configuration step in this entire deployment. n8n on Kuberns requires one variable to be set before you click Deploy.
That variable is REDIS_PASSWORD. It is the secret key used to authenticate with the Redis server that handles n8n’s background job queue. You generate this value yourself and paste it in. Kuberns stores it securely and injects it into the environment at runtime.
### Generating Your REDIS_PASSWORD
To generate a secure value for REDIS_PASSWORD, open your terminal and run the following command. This produces a random 24-character base64 string that is strong enough for production use.
# Generate REDIS_PASSWORD (24+ characters recommended) openssl rand -base64 24
Copy the output from the command. In the Kuberns project setup screen, click Add Env Variable, enter REDIS_PASSWORD as the key, and paste your generated value. Click Save to confirm.
This is very different from a traditional n8n installation, where you would need to install and configure Redis manually, set up authentication in the Redis config file, and pass the password through multiple n8n environment variables. Here, you generate the secret once and Kuberns takes care of the rest.
Step 5: Launch the Deployment
Once your environment variable is saved, click Deploy. From this point, the Kuberns AI-powered deployment system takes over completely.
You will see a live progress screen as Kuberns works through each stage: setting up the environment, provisioning the server, configuring the PostgreSQL database, setting up Redis, enabling SSL, and finalizing the deployment. The whole process typically completes in five to eight minutes.
What is happening in the background is significant. Kuberns is provisioning infrastructure, connecting your n8n instance to its database and cache layer, configuring networking, generating and installing an SSL certificate, and starting the n8n service with proper health checks, all without you touching a single config file.
No manual steps are required that you would find on platforms like Render or Heroku. There is no repository to connect, no build command to specify, and no port to define. Kuberns handles all of it automatically.
Step 6: Access Your n8n Instance
Once deployment is complete, your Kuberns dashboard will show a live URL. This is your n8n instance, running over HTTPS, ready to use immediately.
The URL follows a format like https: //your-app-name.kuberns.cloud. SSL is enabled automatically. There is no certificate setup, no Let’s Encrypt configuration, and no nginx rule to write. You click the link and you are in n8n.
From your dashboard, you can also monitor your server’s RAM usage, storage consumption, active database connections, and recent activity logs. Everything you need to understand the health of your deployment is in one place.
Once you land in the n8n interface, you are ready to start building. Create your first workflow, connect your services, and set up your automation triggers. The infrastructure is stable, monitored, and production-ready. You only need to think about what you want to automate.
Why Use Kuberns to Self-Host n8n?
n8n is a powerful tool, but it was designed to run in a properly maintained server environment. When you install it manually, you take on responsibility for that environment over time. That means keeping Node.js updated, managing database backups, maintaining Redis health, renewing SSL certificates, and ensuring the worker process that handles queued executions stays running reliably.
For many teams, especially those who adopted n8n to get away from manual work and not create more of it, this becomes the hidden cost of self-hosting.
Kuberns changes that experience. Instead of reasoning about Redis configurations and Postgres connection strings, you deploy n8n through an AI-powered system that prepares the entire runtime automatically. The platform understands what n8n requires and configures every layer of the infrastructure correctly from the start.
On Kuberns, the infrastructure supporting your workflows is managed automatically. The runtime environment is stable, HTTPS is enabled by default, and the system is monitored for reliability. You get the full power of a self-hosted n8n deployment, with complete data ownership, unlimited workflows, and no per-seat pricing, without the operational overhead that usually comes with it.
n8n Self-Hosting: Kuberns vs Manual VPS Setup
If you have ever tried to self-host n8n on a raw VPS, you know how many moving parts are involved. Here is a direct comparison of what each approach requires.
| What You Need | Manual VPS Setup | Kuberns One-Click |
|---|---|---|
| PostgreSQL database | Install and configure manually | Provisioned automatically |
| Redis for queues | Install, auth config, link to n8n | Provisioned automatically |
| SSL certificate | Let’s Encrypt + nginx config | Enabled by default |
| Process management | PM2 or systemd setup | Managed by platform |
| Environment variables | Manually written to .env file | Set via UI, injected securely |
| Time to first workflow | 1 to 3 hours | Under 10 minutes |
The difference is not just in setup time. It is in the ongoing cost of maintenance. A manual VPS deployment requires you to revisit these configurations every time a dependency updates or a certificate expires. On Kuberns, that surface area simply does not exist.
What Can You Build with Self-Hosted n8n?
Deploying n8n on Kuberns is the starting point, not the end goal. Once your instance is live, you have access to n8n’s full library of integrations and a workflow engine that can handle complex, multi-step automations at scale.
CRM and Lead Automation
Connect your CRM, email platform, and lead capture forms into a single automated pipeline. When a new contact is added in HubSpot or Salesforce, n8n can enrich the record, send a personalized welcome sequence, notify your sales team in Slack, and log the activity, all without manual intervention.
Data Sync Between Internal Tools
Many teams run into the problem of the same data living in different places. n8n can act as the connective layer, keeping your databases, spreadsheets, project management tools, and analytics platforms in sync on a scheduled or event-driven basis.
AI-Powered Workflows
n8n has native integrations with OpenAI, Anthropic, and other AI providers. You can build workflows that automatically classify incoming support tickets, summarize documents, generate draft responses, or route requests to the right team based on content analysis.
Internal Operations and Reporting
Finance teams, operations managers, and analysts can use n8n to automate report generation, data aggregation from multiple sources, and scheduled delivery to stakeholders. Tasks that once required a dedicated script and a cron job can be built visually and maintained without a developer.
Conclusion
Self-hosting n8n gives you full ownership of your data, unlimited workflows, and complete flexibility to design powerful automations without execution caps or per-seat pricing. The real challenge has never been n8n itself, it has been the time and complexity required to set up and maintain the infrastructure around it.
With Kuberns, that complexity disappears. You generate one secure variable, click Deploy, and within minutes your production-ready n8n instance is live with PostgreSQL, Redis, SSL, and monitoring already configured. Instead of managing servers, you can focus entirely on building workflows that automate and scale your operations.
Ready to get started? Visit kuberns.com and deploy n8n in minutes.
Frequently Asked Questions About Self-Hosting n8n
Is it free to self-host n8n on Kuberns?
Kuberns offers a free tier that lets you deploy n8n and start building workflows immediately. The free plan includes two deployments per day and services are paused after two hours of inactivity. For production workloads that run continuously, a paid plan is recommended.
Do I need to know Docker or Kubernetes to deploy n8n on Kuberns?
No. Kuberns abstracts all container and infrastructure management away from you. You do not need to write a Dockerfile, configure a Kubernetes cluster, or understand how containers work. The platform handles all of that behind the one-click deployment.
What database does n8n use on Kuberns?
Kuberns provisions a PostgreSQL database automatically for your n8n deployment. PostgreSQL is the recommended database for production n8n instances, and it is configured and connected to your instance without any manual setup required.
Why does n8n need Redis?
n8n uses Redis as a queue backend when running in queue mode, which is how it handles concurrent workflow executions reliably. Redis manages the job queue so that workflows can be processed in parallel without conflicts. Kuberns provisions and connects Redis automatically as part of the deployment.
Can I use a custom domain with my n8n instance on Kuberns?
Yes. After deployment, you can configure a custom domain through your Kuberns dashboard. By default, your instance will be available on a Kuberns-provided subdomain with SSL enabled. Adding your own domain follows the same simple configuration flow.
How is self-hosted n8n different from n8n Cloud?
n8n Cloud is the managed SaaS version of n8n, which handles all infrastructure for you but comes with pricing based on workflow executions and active workflows. Self-hosted n8n gives you full control over your data, no execution limits imposed by n8n, and the ability to run as many workflows as your server can handle. The trade-off is that you are responsible for the infrastructure, which is where Kuberns removes the friction.
How long does it take to deploy n8n?
The full deployment process, from clicking the template on Kuberns to having a live n8n instance accessible via a secure URL, typically takes between five and eight minutes. Most of that time is the automated infrastructure provisioning running in the background.