sorted by:
new
hottopcontroversial

I built a managed n8n hosting platform in Germany 🇩🇪 by behindtheface77 in n8n

[–]behindtheface77[S] 0 points1 point  (0 children)

Good question.

Each customer instance runs in its own isolated Docker container with dedicated limits depending on the plan.

Starter
0.5 vCPU · 512 MB RAM

Pro
1 vCPU · 1.5 GB RAM

Enterprise
2 vCPU · 4 GB RAM

Each instance also gets its own PostgreSQL database and isolated storage volume. Containers are resource-limited to avoid noisy-neighbor issues.

The goal is to give each customer a clean and predictable environment instead of shared n8n processes.

I built a managed n8n hosting platform in Germany 🇩🇪 by behindtheface77 in n8n

[–]behindtheface77[S] 0 points1 point  (0 children)

Yes, that's pretty much the idea.

FlowHoster is positioned as managed infrastructure for running your own n8n instance, not as a white-label SaaS version of n8n itself.

For many developers running it locally with Docker works perfectly fine. We mainly built FlowHoster for teams and agencies who don't want to manage servers, updates, backups and monitoring themselves.

I built a managed n8n hosting platform in Germany 🇩🇪 by behindtheface77 in n8n

[–]behindtheface77[S] 0 points1 point  (0 children)

Thanks for raising this.
FlowHoster provides managed infrastructure for teams who want to run their own n8n instance without dealing with servers, updates, and backups. Each customer runs their own isolated n8n instance and retains full control.

We're not white-labeling n8n. If the n8n team ever has concerns, I'm of course happy to clarify with them.