Self-Host
Run it yourself. Own it completely.
SocialWeb is built to be self-hosted. Managed cloud is there for convenience, and the privacy is the same either way.
Why self-host
Three reasons to run your own.
Complete control.
Your data lives on your hardware. You decide what runs, what stays, and what gets deleted.
No shared infrastructure.
Your instance is yours alone. Your subscriptions never sit in a shared database next to a stranger's.
Your data, your terms.
Export, move, or delete it any time. We keep no copy, no backup, and have no access.
Architecture
What a self-hosted instance looks like.
Your server runs the SocialWeb backend: it fetches your feeds, proxies your searches, and hosts your group chats. The mobile and web apps connect straight to it over HTTPS. It works exactly like the managed cloud, except no one else can reach your server.
Requirements
What you’ll need.
- A Linux serverA small VPS or home server is plenty for personal use.
- DockerSocialWeb ships as a single Docker image.
- A domain nameNeeded for HTTPS. Point an A record at your server.
- About 15 minutesFrom a fresh server to a running instance.
SocialWeb’s group chat is built on an open extension to RSS. The full specification is published separately.
Read the protocol spec →