Notion
There is no self-hosted Notion. There is no on-premise edition, no community edition, and no licence that puts the server in your data centre. Notion is a hosted product; the desktop app is a client for it.
What you can do is get your content out — Notion exports to Markdown, HTML, CSV and PDF, and there is an API. That is portability, and it matters. It is not the same as running the thing, and if your requirement came from a compliance rule rather than a preference, the distinction is the whole point: an export is a copy of the data, not control of where the processing happens.
So if “self-hosted Notion” is a hard requirement, the honest search is not for a Notion setting. It is for a different tool.
Make
Make is the one where the naming does real damage, because Make does have something called an on-premise agent, and it is not Make on your premises.
From Make's own help centre: with the on-premise agent installed on your system, “you can access applications and databases on your local network without changing the settings of your firewall”, and “one on prem agent can connect to many applications that are located in the same network”.
Read that carefully. The agent is a bridge. Make's platform keeps running in Make's cloud; the agent is a component you install so that cloud can reach machines behind your firewall without you opening ports. Your scenarios, your connections and your execution history stay where they were. It solves a network-access problem, not a data-residency one.
It is also enterprise-only — Make's documentation describes it as available to enterprise customers, and it does not appear on the standard plans. Genuinely on-premise deployments of the platform itself exist in Make's white-label and enterprise arrangements, which is a sales conversation, not a download.
What that actually leaves you
Three routes, and they are honestly different in cost, not just in shape.
| Route | What you run | The real cost |
|---|---|---|
| Keep both, accept the cloud | Nothing. | You have not solved the requirement, you have decided it was a preference. Fine, if it was. |
| Swap the automation half | A self-hostable automation tool — n8n is the obvious one, and its documentation covers hosting it yourself. | Your automations are yours; your documents and databases are still in someone else's cloud. Half a solution, but the half that touches the most systems. |
| Swap both | A workspace and an automation layer you host, or an app that keeps the data on your own devices in the first place. | Migration, and giving up whatever the hosted products were genuinely better at — real-time multiplayer editing, mainly. |
There is also a fourth answer that people arrive at more often than they expect: the reason for wanting self-hosting was “I do not want my work living on a server I do not control”, and for a single person or a small team, keeping the data on your own devices answers that without you having to run a server at all. Self-hosting is one way to own your data. It is not the only one, and it is the one with a pager attached.
Where Platform stands on this
Platform is being built around the fourth answer first: databases, workflows, a knowledge graph and charts in one native app for iPhone, iPad and Mac, with your records on the device rather than in a cloud you rent.
Self-hosting the backend is on offer — PostgreSQL and RabbitMQ on your own hardware, no cloud vendors — but let me be exact about the state of it, because this is a page about people making promises they have not kept: the source is not published yet. There is no repository to clone today. If self-hosting is why you are here, mail support@synccy.com and I will walk you through what exists. The app itself is not on the App Store yet either; the waitlist is how you hear about both.