Skip to content
NowHosted

n8n hosting that keeps your workflows running

n8n hosting from NowHosted gives your team a managed instance for running workflows on your own domain. We run n8n, apply updates, and back up its persistent database. HTTPS webhooks and queue workers support your workflows, with a choice of server region. The service runs on Agency and Scale and counts as one site.

n8n instance

https://flows.studio.example.com

Running
Version
1.112.0
Queue workers
Active
Region
eu-central
Webhook endpointsLast call
  • /webhook/orders09:42 UTC
  • /webhook/forms09:38 UTC
  • /webhook/inventory09:31 UTC

01

Keep your attention on the workflow

A workflow connects business systems, but the service behind it also needs care. NowHosted manages the running n8n instance so your team can work on triggers, actions, and the business rules that connect them. You do not need to take on routine hosting work just to keep a useful workflow available.

You own the workflow logic and the services it connects. You decide which events start a workflow, what data it uses, and who can change it. We handle the hosting operation, updates, and backups. Our managed hosting page explains how this division of responsibility works across the platform.

  • Managed n8n operation and updates.
  • A persistent database for the instance.
  • Database backups as part of managed hosting.
  • Your own domain for access and webhook endpoints.

02

Give incoming events a stable destination

Webhooks let another application send an event to n8n when something happens. Your instance receives those requests over HTTPS on your own domain. That gives integrations a clear destination and protects data in transit between the sending service and the hosted endpoint. Your team still controls what each workflow accepts and does with that data.

Queue workers handle workflow jobs as part of the hosted instance. The persistent database keeps the instance's stored data separate from a temporary running process. These are hosting foundations for your workflows, not a promise about the response time or capacity of an external service that a workflow calls.

Before moving an existing workflow, identify its active webhook URLs and connected systems. Review those references during the move so the receiving endpoint and the sending service agree. For applications that work alongside n8n, web application hosting brings supported Git projects into the same hosting service.

Workflow execution

  1. 01
    HTTPS webhookReceived

    /webhook/orders

  2. 02
    QueueAccepted

    orders

  3. 03
    WorkerRunning

    workflow-runner

  4. 04
    Persistent databaseSaved

    Execution record

03

Keep the instance maintained and recoverable

We apply n8n updates and back up the database. This covers the hosted service, while your team checks that its workflows still match the way the business operates. A change in a connected application can affect a workflow even when the hosting itself is healthy. Keep an owner for each integration and review changes to its dependencies.

Backup retention follows your plan. Agency includes 30-day backups, while Scale includes 90-day backups. Choose the retention period that fits the way your team reviews and recovers from changes. A backup gives you a recovery point for hosted data; it does not reverse actions already taken in a connected system.

Our hosting security page explains the wider approach to isolation, access, and recovery. Use it to review hosting controls alongside your own rules for workflow permissions and connected account access. Your team's data handling rules still apply to the information passing through a workflow.

Instance maintenance

n8n
Application update
Applied
Database backup
Complete
Backup location
Off-site

Agency

30 days

Scale

90 days

04

Place the instance where your work happens

Choose North America, Europe, or Asia-Pacific as the server region for your n8n instance. Region choice is per site, so an app and a website in the same account can serve different audiences. Consider the people using n8n as well as the systems sending requests to it when making that choice.

Use your own domain to keep the instance address aligned with the rest of your business. HTTPS protects connections to the webhook endpoint. Review any domain references in workflow settings and connected applications before a move. Clear ownership of DNS access helps keep the migration organized without sharing unrelated account access.

Custom domain

flows.studio.example.com

HTTPS · Connected

  • North AmericaAvailable
  • EuropeSelected
  • Asia-PacificAvailable

05

Run n8n on Agency or Scale

Managed n8n is available on Agency and Scale. An instance counts as one site within the plan's site allowance. It shares the plan's storage allocation with the other sites and apps in your account. Compare the full WordPress hosting plans before choosing a plan for a mixed portfolio.

Plan Monthly subscription Yearly billing Sites Storage Backup retention
Agency Monthly subscription149 USD per month Yearly billing74 USD per month, 888 USD per year Sites20 Storage150 GB Backup retention30 days
Scale Monthly subscription399 USD per month Yearly billing199 USD per month, 2,388 USD per year Sites60 Storage500 GB Backup retention90 days

Agency includes team roles and priority support. Scale adds dedicated resources and account controls such as SAML SSO and an audit log. Select based on the hosting and account requirements of your team, rather than assuming that every workflow needs the same setup.

Bring your domain and workflow requirements

Start with the plan that fits your sites and apps. Identify the domain, preferred region, current instance, and workflows that need to move. Our free website migration process covers the hosting handover, a staging copy, review, and DNS cutover with zero downtime. You review the application before the live destination changes.

The old host stays untouched until you cancel it. After the move, keep workflow ownership clear and review connected account access as your team changes. You can export a full backup and cancel at any time, with access continuing until the end of the paid period.

FAQ

  • Managed n8n runs on Agency and Scale. Each instance counts as one site and uses storage from the plan allocation.

  • Yes. Your managed n8n instance uses your own domain, and webhooks receive requests over HTTPS. Your team maintains the endpoint references in its connected services.

  • We run the instance, apply updates, and back up its persistent database. Queue workers support workflow jobs. Your team owns workflow logic and access to connected services.

  • Yes. Choose North America, Europe, or Asia-Pacific for the instance. Region choice is per site, so other sites in the account can use a different region.