No. xiben8n is an independent hosting service built on top of the open-source n8n project and E2B sandboxes. You get a familiar n8n UI, but support and infrastructure are provided by xiben8n.

Yes. You can export workflows from your existing n8n instance and import them into your xiben8n instance via the standard n8n import/export flow.

When your sandbox is idle for some time, E2B pauses compute. Your data remains intact. On the next incoming request—UI visit, webhook, or API call—the sandbox is resumed and your n8n instance is available at the same URL.

Yes. When a webhook request comes in, E2B will resume the sandbox and forward the request. There may be a small cold-start delay, but your workflows continue to function.

Credentials are stored inside your dedicated n8n instance running in the sandbox. We treat access to your sandbox and data with the same care as other infrastructure providers and continuously harden the environment.

Absolutely. If you are comfortable managing servers, reverse proxies, and monitoring, self-hosting on a VPS or Kubernetes cluster can be a good fit. xiben8n is for people who prefer to offload that responsibility while keeping the power of n8n.