Where the line is drawn#
Self-hosting usually means one of two things, and they are very different commitments. Running the whole application — database, migrations, upgrades, backups, uptime — is a genuine operations project, which is why most teams who say they want it do not end up doing it.
The other version is narrower and much more practical: the account, the interface and the shared data pool stay with the vendor, and the work layer moves to a machine you control. That layer is the part that touches your data and your domain — sending, crawling and enrichment, and background jobs.
- Stays with the control plane
- Your account, the interface, the shared signal and prospect pool, the record itself.
- Runs on your node
- Sending, crawling and enrichment, and background jobs.
- What you operate
- One service, on one machine, kept reachable and patched.
- What you do not operate
- Schema migrations, application upgrades, the web tier.
That is the arrangement this guide is about, and it is the one SalesShift’s node registration implements — as an option on any plan, not a tier.
Four reasons teams do it#
- Control over where the work runs. Prospect notes and reply bodies are commercially sensitive, and the honest answer to where does this go is architectural rather than contractual when the answer is your own machine.
- Reputation ownership.Mail leaving your own mailboxes builds reputation for your domain, and it is unaffected by other senders on someone else’s shared infrastructure.
- Network position. Crawling and sending originate from your own machine, under your own operational policies, rather than from shared infrastructure.
- Portability. Your mailboxes stay yours, so the sending identity your reputation is built on never belongs to the vendor.
The reason that is not on that list is features. A self-hosted arrangement worth choosing is not a reduced product — it is the same product with the work happening somewhere else.
What it does not change#
A self-hosted arrangement worth choosing changes where the work runs, not what the product is. The features are the same, the record is the same, and moving between your node and the managed one should be an account change rather than a migration.
What a plan can reasonably meter is the parts a vendor supplies from a shared resource, which is why an allowance of prospect reveals from a shared pool is a coherent limit and a cap on how many contacts you may store is not.
SalesShift works this way. Register a node from Billing and sending, crawling and background jobs run on it, using your own mailboxes. It is an option on any plan, and it changes what you operate — not which plan you are on or what it costs. Every plan includes every feature; see pricing.
Sending from your own mailbox#
This is the part that changes day-to-day behaviour most. Mail leaves the mailboxes you connect, over your own infrastructure, which means the reputation you build belongs to you and travels with you.
It also means the consequences are yours. Nobody else’s bad list affects your placement, and your bad list affects nothing but your own domain — which is an argument for caps, ramps and automatic pauses, not against them. Those controls apply identically whether the node is yours or ours.
Reply detection follows from the same design: replies land in the mailbox that sent the original, so a product that sends through your mailbox can read them, categorise them and stop the sequence. The rotation guide covers how several mailboxes share the load.
Where the AI runs#
Drafting and rewriting are the parts of a sales platform most likely to send your text somewhere else, so it is worth knowing where they run.
In SalesShift the assistant runs on infrastructure we operate and is metered in credits, so there is nothing to configure. Your data is never used as training data. Workspaces whose policy requires a specific model provider can connect their own key in Settings instead.
What it costs you#
Being straightforward about the downside is what makes the rest credible.
- Availability is yours. A node that is down is a queue that is not moving. Sending and background work stop until it is reachable; the record itself is unaffected.
- Patching is yours. One service on one machine, but it is a machine somebody has to keep current.
- Deliverability is entirely yours. There is no shared reputation absorbing a mistake, which is the point and also the risk.
- Support is narrower by nature. Half of a problem is on infrastructure the vendor cannot see.
For a team of one or two with a server they already run, that is a small price. For a fifteen-person sales org with no infrastructure practice, it usually is not — and the honest recommendation there is the managed version.
The test that matters: leaving#
Every claim about data ownership resolves to one question: can you leave with your data, without asking anyone? A full export, in a format something else can read, obtained without a support ticket. Ownership that requires a request is not ownership.
The second question is mobility between plans. If the difference between self-hosted and managed is whose infrastructure runs the work, moving is an account change. If the difference is which features exist, moving is a migration — and the direction you can move is the direction the vendor prefers.
The third is the right of the people in your database. A prospect record is personal data, and a right-to-erasure request has to reach every copy — including the ones held by other workspaces — and survive the next crawl of the same public source. SalesShift stores the request as a hash, deactivates the pool record, strips saved copies across every workspace, and checks that hash before any subsequent insert.
If self-hosting appeals for the reasons above, the developer-tools and founder-led sales pages describe the two situations where it most often turns out to be the right call.