Self-hosted node

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 economically honest. What a vendor genuinely pays for is compute, sending capacity, data and model tokens. A workspace supplying some of those consumes less, which is why usage a vendor does not carry should not appear on the bill.

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.

Does the discount exist because the work moved to you, or because features were removed? The first is a coherent arrangement; the second is a cut-down edition with a friendlier name.

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.

SalesShift supports this on every 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 what you operate rather than what you pay — usage we do not carry is not metered to you.