Skip to main content
SocialWeb

Features

Everything you need. Nothing you didn’t ask for.

Read, message, and search — on open protocols, with structural privacy built in from the start.

The feed

Your feed, your rules.

SocialWeb delivers your subscriptions in the order they were published — newest first, no exceptions. No engagement score, no paid placement, no editor deciding what you should care about. When you subscribe to a source, you get everything from that source. When you don't, you get nothing. The feed is the contract you set, and SocialWeb keeps it. When there's nothing new, the feed stops. That's a feature, not a bug.

Stacks

Organize by topic, not by what's trending.

A stack is a named group of subscriptions. Create one for Sports, one for Finance, one for the handful of blogs you actually read. Switch between them from a tab at the top of the feed. Your main feed is all subscriptions together; your stacks are focused lenses into the same data. You decide what belongs in each one. Nothing moves between stacks automatically. Nothing gets added without your action.

Group chat

Conversation on a server you control.

SocialWeb's group chat is built on an extension to RSS. A host — a person, a team, a community — runs a server (or uses SocialWeb's managed cloud) that holds the conversation. Participants subscribe to it like a feed. New messages appear in order. The host chooses who can post. The data lives on the host's server, not on a shared corporate platform that owns it by default. If you want the full technical specification, it's published as an open standard.

Group chat diagram: SocialWeb extends RSS with a conversation layer. Subscribers post replies that appear as items in a shared RSS channel. No proprietary server required — any compatible client can participate.Subscriber ASubscriber BPublisherRSS channelopen protocolReads repliesReads repliesOpen RSS extension — no proprietary lock-in

Private video

Video sharing modeled on podcasting.

Private video on SocialWeb works the way podcasts have always worked: a video is hosted at a URL, and subscribers download or stream it directly. The host keeps the link secret and shares it only with intended viewers through the RSS feed. No corporate video platform holds the content. No CDN profile is built on viewers. Streaming goes server-to-server, not through a third party that logs who watched what and when.

Video privacy diagram: SocialWeb fetches video content on your behalf. The video provider sees only SocialWeb's server — not your identity. No watch history is stored on SocialWeb's servers.Video platformYouTube / VimeoSocialWebfetches for youYour deviceno watch historyhistory not storedsees SW IP onlyPlatform never sees your identity or viewing patterns

Hosting

Your server or ours. Same privacy either way.

On first launch, SocialWeb asks: self-host, or use managed cloud? Self-hosted means your data lives on hardware you control. You can inspect every byte, delete anything at will, and run SocialWeb entirely off the grid. Managed cloud means SocialWeb's infrastructure handles the setup — the protocol-level privacy properties are identical, but you don't manage servers. Both options use the same open protocol. You can migrate between them. The choice is yours, and it's reversible.

AI

AI that stays in its lane.

SocialWeb does not apply AI to your content without your explicit opt-in. If you enable it, two options are available: local AI runs entirely on your device (self-hosted only) — no data ever leaves your machine. Cloud AI routes through Baseten under terms that explicitly prohibit using your content for model training. Either way, the AI assists you; it doesn't build a profile on you. Disabling it is always an option, and the app works fully without it.

Try it free for 7 days.

No credit card required.

Start free trial