Platform

Self-hosted node

A self-hosted node is a server you run that performs the work a sales platform would otherwise do on shared infrastructure — sending, crawling, background jobs. The vendor keeps the account and the interface; the parts that touch your data and your domain run on a machine you control.

Also called: Tenant node, Own infrastructure

The split that makes it workable#

Fully self-hosting an application means owning its upgrades, its migrations and its outages. Running only the work layer is a much smaller commitment: one service, on one machine, that the hosted control plane talks to.

The division is also easy to reason about: the vendor runs the product, you run the machine that does the work touching your data and your domain.

What you actually get#

Mail leaves your mailbox over your infrastructure, so the reputation you build belongs to your domain. Crawling and enrichment run from your address space. And the data that would otherwise sit in a shared pipeline sits on your machine.

The trade is operational: you keep the node reachable and patched, and a node that is down is a queue that is not moving. It is a real cost, and it is a much smaller one than running the whole platform.

Questions to ask before choosing it#

Is it the same product with the work moved to you, or a cut-down edition with a friendlier name? Only the first is worth operating a server for.

And can you leave with your data — a full export, in a format something else can read — without asking anyone? Data ownership that requires a support request is not ownership.

Self-hosted node in SalesShift#

SalesShift supports this as an option on any plan: register your own node in Billing and sending, crawling and background jobs run on your machine, using your own mailboxes, while the account and the interface stay with the control plane. It changes where the work runs, not which plan you are on.

Further reading#

See it running

Signals, prospect search, sequences, deliverability and pipeline on one record.