SpliceRun documentation
We run your automation app so you can build workflows instead of babysitting Docker, certificates and night-time restarts. These pages cover how that works, exactly where our responsibility ends and yours begins, and what to do at 11pm when a workflow has stopped.
Start here
New to SpliceRunQuickstartAccount, lane, first instance - in the order you actually do them.DecidingChoosing a planShared, Dedicated and Bring your own server suit genuinely different situations.Already running n8nMigrating inMove a working instance off your own VPS, Elestio, Coolify, Railway or Render.
Browse by topic
Hosting plansThe three lanes, and the exact line between what we manage and what you manage.Networking & domainsHow your instance reaches the internet, and how the internet reaches it.Your dataMoving data in, backups while it is here, and a complete copy out whenever you want one.Billing & accountWhat you pay for, what costs extra, and what happens if you cancel or stop paying.SecurityHow instances are isolated, and who at SpliceRun can reach your data.TroubleshootingOrganised by symptom, not by subsystem. Start from what you are seeing.
Most-read pages
- What we manage - the do / you-do table, including what is deliberately not included
- How pricing works - the structure behind the numbers on the pricing page
- Outbound connections and DNS - read this before your first HTTP Request node
- Backups and recovery - what is captured, how often, and how to get it back
- Billing, cancellation and data policy - nothing is deleted without notice and a window to fix it
- n8n is slow or using high CPU - how to tell a workload problem from a plan problem
Still stuck?
Search the whole site from the box in the header. If the answer is not here, contact us - and tell us what you searched for, so the page you needed gets written.