Skip to main content

Setting up your automation instance

This page is the short map for after you create a SpliceRun account. Pick your lane, then follow the right guide. Nothing here invents a SLA or a credential email that the product does not send.

Three lanes​

LaneWho owns the serverBefore you payAfter you pay
SharedSpliceRunA SpliceRun accountWait for provision; open the app; you create the first admin user
DedicatedSpliceRun (we rent the VPS)Account + a domain you control (recommended)We provision the box; you point DNS and claim the app owner
Bring your own serverYouVPS + domain, with DNS already pointing at itWe give you an SSH key to install, then preflight and install the stack

If you are still choosing a lane, start with Choosing a plan and What we manage.

Shared (we host it)​

  1. Sign in at app.splicerun.com and open Deploy.
  2. Pick Shared, the size you want, and complete payment.

The deploy wizard with Shared managed chosen and the Shared XS size selected, with the order summary filled in on the right

Continue stays greyed out until you have picked both the hosting style and a size - that is the step people get stuck on.

  1. Provisioning is automatic. Watch the instance page - there is no fixed “ready in 2-3 minutes” promise; load, queue depth and image pulls vary.
  2. When the status is live, open the instance URL. There is no email with admin credentials. The first person to complete signup in the app becomes the owner (we seed that path so the instance is not left unclaimed).
  3. Build workflows. OS security patching, HTTPS and backups are on us - see What we manage.

Full Shared onboarding: Shared hosting.

Dedicated (we buy the server for you)​

  1. Have a domain or subdomain ready (A record will point at the server IP we show you after provision).
  2. Deploy Dedicated, choose size/provider options offered at checkout, pay.
  3. We create and harden the VPS, install the stack, and attach TLS when DNS is correct. Timing depends on the provider - watch the instance page, not a marketing estimate.
  4. Claim the app owner the same way as Shared: open the URL and complete first signup when prompted. No separate “password by email”.

Full Dedicated onboarding: Dedicated server.

Bring your own server​

You need the VPS and the domain before you start - including the DNS A record pointing at the server, because the HTTPS certificate cannot be issued without it.

You do not need our SSH key yet. It does not exist until you begin the setup: we generate a key pair for your instance and show you the public half, with a ready-made command to install it.

The last step of the wizard for Bring your own server, explaining that the SSH public key is issued after the instance is requested

Spec, key install, preflight and post-setup are written in full here:

Bring your own server

That guide is the product source of truth for BYOS (minimum 1 vCPU / 1 GB RAM / 10 GB free disk, Ubuntu 22.04/24.04 or Debian 12, ports 22/80/443, root or passwordless sudo).

First workflow (any lane)​

Once the app is open and you are signed in as owner:

  1. Add a simple workflow (for example a webhook and a debug/log node).
  2. Execute it once from the editor.
  3. Activate it only when you are happy with the result.

Next steps​

Need help? Contact support

Published Updated