01
Feed
One chronological home for everything posted across every space.
Live · running a paid community in production
The community platform that lives in your product
Feed, spaces, courses, direct messages, and a leaderboard — inside the same app your members already log into. CommunityOS replaced a paid community platform outright rather than sitting next to one.
12
surfaces live today
1
login, no second platform
MCP
driveable from Claude
12 surfaces
Everything a paid community needs, and nothing it does not.
Built by replacing a hosted community platform feature by feature, which is a very effective way to find out which features nobody was using.
02
Spaces
Public and private channels, each with its own access and its own header.
03
Posts & comments
Rich composer with mentions, GIFs, images, and threaded replies.
04
Courses
Structured courses with lessons, progress, and an admin course builder.
05
Direct messages
One-to-one conversations so support does not have to happen in public.
06
Members & profiles
Profiles with tags, activity heatmaps, and streaks that show real work.
07
Leaderboard
Weekly points for the behaviour you actually want, not for posting volume.
08
Bookmarks
Save any post or lesson and find it again without scrolling the feed.
09
Giveaways
Scheduled draws with a confirmation step before anything is announced.
10
Ideas & competitors
Member-submitted ideas and a shared board of what everyone is watching.
11
Admin & metrics
Space and course management plus engagement metrics keyed to paying members.
12
Notifications
Bell and push with deep links straight to the comment that mentioned you.
Why CommunityOS
Your community should not live on someone else’s domain.
Hosted community platforms charge a monthly tax to keep your members, your content, and your engagement data one export away from you.
01
Same app, same login
Members do not cross a domain, sign in twice, or learn a second interface. The community is a tab in the product they already pay for.
02
Entitlement is the membership
Access follows the Stripe subscription. Cancelling revokes community access automatically — no reconciling two member lists by hand every month.
03
Your data, your database
Posts, courses, and engagement history live in your own Postgres with row-level security. Nothing to export if you change your mind.
04
Proven by decommissioning one
This module was built to replace a paid community platform, and it did — end to end, subscription cancelled. It is not a demo of a feed.
Questions
Before you ask.
Is this actually in production?
Yes. CommunityOS runs a live paid community today — feed, spaces, courses, direct messages, leaderboard, giveaways, and admin metrics are all in production, and it replaced a hosted platform that has since been shut off.
Can I run my own community on it?
Not yet as a self-serve product. Today CommunityOS runs one community end to end; opening it up for members to host their own is a roadmap item, not something you can switch on.
How does access control work?
Spaces can be public or private, and membership is driven by entitlement rather than a separate invite list. Private spaces are genuinely private — even automated agents only ever see public spaces.
Are there notifications?
Bell notifications and web push, both deep-linked to the exact post or comment. There is also a weekly recap, which stays silent in weeks with nothing new rather than sending an empty digest.
What about mobile?
It is a progressive web app — installable, and it updates itself at safe moments instead of reloading under you mid-scroll.
One platform
CommunityOS is one of eight systems.
Every module shares the same login, the same subscription, and the same integrations. Add the ones you need as the work grows.
A community inside your product, not beside it.
CommunityOS is included with your AIOS membership. Sign in and open the feed.
Sign in →