Separate n8n UI deployment

Describe the issue/error/question

Is it able to separate the n8n UI editor to another deployment? We currently have 3 docker that runs for UI, webhook, and worker. It works perfectly, but if the UI editor can be deployed on another deployment, it will be a point plus

Information on your n8n setup

  • n8n version: 0.183.0
  • Database you’re using (default: SQLite): MySQL
  • Running n8n with the execution process [own(default), main]: own
  • Running n8n via [Docker, npm,, desktop app]: docker

Hi @awk,
at the moment the n8n UI is coupled to the main process. What improvements are you looking for seperating the UI from the main instance?

Hi @marcus ,

Currently we are using more than 2 kubernetes pod to deploy main deployment because our traffic seems high sometimes. If we only using 1 pod to serve both UI thing and main process, we experiencing some delay before the workflow executed, it’s vary from minutes until 1-2 hour delay, depend on traffic. If we increase to 5 or more pod, delays are gone. But from the cost perspective, it’s not efficient because actually only 1 pod that serve the UI