Self-hosted automation
The “when this, then that” glue between your services does not need to run in someone else’s cloud reading all your data. n8n gives you that workflow automation on your own server.
n8n is a workflow tool: it connects APIs, databases and webhooks into automations you build visually. Self-hosted, it keeps the credentials for all those services — which is exactly why you might not want them in a SaaS.
Give it a database
By default n8n uses SQLite, which is fine for a handful of workflows and poor once they multiply. Point it at PostgreSQL for anything you rely on — see running PostgreSQL.
The encryption key is everything
n8n encrypts stored credentials with a key it generates on first run. Lose that key and every saved credential becomes unreadable; leak it and they are all exposed. Set N8N_ENCRYPTION_KEY explicitly, back it up, and treat it like the secret it is — see managing secrets.
Webhooks need to be reachable
Half of what n8n does is receive webhooks from other systems. That means a stable public URL behind TLS — set WEBHOOK_URL to match, or triggers silently never fire. See a reverse proxy in front.
It can reach your whole network
An automation server is powerful precisely because it talks to everything. That also makes it a prize if compromised. Keep its own login behind strong authentication, restrict what it can reach on your internal network, and patch it promptly.
Back up workflows and credentials
The database holds your workflows and encrypted credentials; the encryption key unlocks them. Back up both, together, or a restore gives you workflows you cannot run. See backups that actually restore.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base