Known

Self-hosted social publishing, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source PHP social publishing platform — write posts, share photos, publish status updates — all to your own domain, with optional syndication to social networks [website][README].
• Who it’s for: IndieWeb advocates, bloggers, and small communities who want to own their publishing infrastructure and syndicate outward, rather than feeding content into platforms they don’t control [website].
• Cost savings: No SaaS pricing tier — it’s self-hosted only, meaning your cost is a VPS ($5–10/mo) plus the time to set it up. The software itself is free.
• Key strength: ActivityPub and WebMention support make it interoperable with the Fediverse and the wider IndieWeb — your site can respond to, comment on, and receive comments from other IndieWeb sites without a centralized platform in the middle [README][website].
• Key weakness: 1,108 GitHub stars and a license field that reads “NOASSERTION” signal a project in ambiguous territory — not dead, but not thriving. The hosted cloud version (withknown.com) appears to no longer offer signups. Setup requires PHP 8.3+ with multiple extensions and a PHP-fluent ops environment that most non-technical founders won’t have.

---

What is Known

Known (also known by its underlying project name “Idno”) is a social publishing engine for PHP. The pitch is simple: instead of posting to Twitter, Instagram, or Medium and hoping those platforms don’t disappear or change their terms, you post to your own domain and optionally push copies (syndicate) to wherever your audience is. The IndieWeb community calls this POSSE — Publish on your Own Site, Syndicate Elsewhere [website].

The platform supports blog posts, status updates, photos, check-ins, and other content types. Multiple authors can post to a single Known instance, making it usable for small community sites or group blogs, not just personal publishing [website]. Sites built on Known can talk to each other — leave comments, bookmark each other’s posts, and respond across instances — through the WebMention and ActivityPub protocols [README][website].

The project has been around since roughly 2013, started by Ben Werdmuller and Erin Jo Richey as a tool for the IndieWeb movement. It sits at 1,108 GitHub stars as of this review — modest but nonzero, indicating a real (if small) user base. The GitHub repository is at github.com/idno/idno, which is itself a signal about naming evolution: the project started as Idno, became Known, and the repo name never followed.

One thing to flag upfront: the license field in the repository metadata shows “NOASSERTION,” which means GitHub’s license detection couldn’t identify a clear open-source license. This matters. If you’re building something commercial on top of Known, or deploying it in an organization with legal review, that ambiguity needs investigation before you commit [merged profile].

---

Why people choose it

There are no substantial third-party review articles covering Known specifically. The tool occupies a specific corner of the self-hosted space — the IndieWeb and personal publishing community — rather than attracting mainstream coverage from SaaS-comparison blogs. That narrowness is itself information: Known is chosen by people who already know what IndieWeb is and have specifically gone looking for a self-hosted POSSE-compatible platform.

The people who land on Known typically share two characteristics. First, they’ve been burned by platform dependency — Twitter changing its API, Instagram suppressing links, Medium paywalling content — and want a canonical home for their writing that no company can touch [website]. Second, they’re not satisfied with a static blog generator (Hugo, Jekyll) because they want the social features: comments, responses, WebMentions, multi-author collaboration, and Fediverse connectivity [README][website].

The website quotes describe it as something that lets you “more easily organize all your digital info in one place,” and as “designed to give everyone a fully open publishing platform” [website]. These aren’t technical claims — they’re philosophy. If that philosophy matches yours, Known is in the conversation. If you’re optimizing for SEO, performance, or a polished editorial workflow, you’re probably looking at the wrong tool.

---

Features

Based on the website and README:

Publishing types:

• Blog posts with full HTML and WYSIWYG rich text editing [website]
• Status updates (short-form) [website]
• Photos [website]
• Support for multiple content types via the plugin system [merged profile]

Social and syndication:

• Hashtag support across all content [website]
• Bookmarklet for posting from any webpage [website]
• RSS, XML, JSON, and KML feeds [website]
• WebMention support — send and receive responses between IndieWeb sites [website]
• ActivityPub — your Known instance can federate with Mastodon and other Fediverse platforms. Post distribution to followers, follow-accept delivery, update/delete propagation all go through the async queue [README]

Multi-user:

• Unlimited collaborators on a single instance [website]
• Per-post privacy controls — keep content private for personal journaling or internal group use [website]

Customization:

• Custom domain support [website]
• Static pages (about, contact) [website]
• Custom JavaScript and CSS editors for visual customization [website]
• Plugin architecture (MongoDB and plugins listed as canonical features) [merged profile]

Async event queue (required for ActivityPub):

• By default, events like WebMentions, syndication, and ActivityPub delivery happen synchronously inside the web request — making saves slow [README]
• The async queue moves this to a background worker. This is required for ActivityPub to work at all — without a running queue worker, remote servers never receive posts [README]
• Setup involves systemd (or cron as a fallback), a separate PHP process, and persistent environment configuration [README]

Responsive design:

• Works on mobile and desktop — the UI adapts [website]
• Email notifications for post responses [website]

---

Pricing: SaaS vs self-hosted math

Known does not appear to offer a managed cloud tier. The withknown.com website prompts visitors to “Download & Install” — no pricing page, no sign-up flow for hosted accounts [website]. This is a self-hosted-only proposition.

What you’re paying:

• Software: Free (with the caveat that the license situation needs clarification)
• VPS: $5–10/mo on Hetzner, Contabo, or DigitalOcean for a server capable of running PHP + MongoDB
• Domain: $10–15/yr if you don’t have one

Comparison alternatives:

• Ghost (self-hosted): free software, but Ghost(Pro) runs $9–$199/mo. Self-hosted Ghost is a cleaner, more modern CMS for purely editorial use.
• WordPress.com Business: $25/mo
• Micro.blog: $5/mo managed, including ActivityPub/Fediverse integration, and you don’t touch a server
• WriteFreely: free self-hosted, minimal and focused on long-form writing with ActivityPub support

For the IndieWeb use case specifically, Micro.blog is worth comparing directly: it costs $5/mo managed, handles ActivityPub and WebMentions without any server setup, and lets you use a custom domain. That’s the choice Known forces you to make — full control and self-hosting vs. $5/mo to have someone else handle the ActivityPub queue worker for you.

---

Deployment reality check

This is where Known gets honest friction. The requirements are:

• PHP 8.3+ with selected extensions — this is current but non-trivial to configure correctly on a fresh VPS [README]
• A supported database backend — MongoDB is listed as a canonical feature [merged profile], though the docs indicate other backends are possible
• Composer for dependency management [README]
• An async queue worker if you want ActivityPub (systemd recommended, cron as fallback) [README]
• A web server (nginx or Apache) with appropriate PHP configuration
• A domain and SSL

The README install path is: clone the repo, run composer install, configure config.ini, set up the database, optionally configure the async queue worker as a systemd service [README]. There’s no Docker Compose file in the repo — each component is configured manually.

The async queue setup deserves specific attention because the README is explicit: if the queue worker isn’t running, ActivityPub doesn’t work. You need to create a systemd unit file, enable it, and know how to restart it after updates [README]. If you’ve never set up a systemd service, budget time to learn.

Realistic install estimate:

• Technical user comfortable with PHP and Linux: 2–4 hours
• Non-technical founder following a guide: full day, possibly two, with a real chance of giving up on the ActivityPub queue step
• Non-technical founder with no Linux experience: not a realistic self-install target

Unofficial packages are available from a community contributor [README], which helps, but these aren’t official and the documentation points to them as a convenience, not a supported path.

The project documentation lives at docs.idno.co — the link is referenced in the README, though given the project’s age and ambiguous license status, verifying the docs are current before relying on them is worth doing [README].

---

Pros and Cons

Pros

• Genuine IndieWeb and ActivityPub support. If Fediverse interoperability is the requirement, Known delivers it — WebMentions, ActivityPub post distribution, follow-accept delivery. The async queue architecture is described clearly in the README [README].
• Multi-author out of the box. Unlimited collaborators on one instance, making it usable for small team blogs or community sites without per-seat pricing [website].
• POSSE philosophy baked in. The whole product is built around the idea that your site is canonical and syndication is secondary. That’s a meaningful architectural choice, not a feature checkbox [website].
• Plugin system for extensibility [merged profile].
• Privacy controls — you can publish privately for personal use on the same instance as public content [website].
• No per-post or per-user SaaS costs — once it’s running, the marginal cost of more content or more users is zero.

Cons

• License is “NOASSERTION.” This is a real problem for anything beyond personal use. Before deploying at an organization or building commercially on top of Known, get legal clarity [merged profile].
• 1,108 stars and unclear active development. Not a death sentence — some excellent tools have modest GitHub counts — but it means a smaller community for support, fewer plugins, and more uncertainty about long-term maintenance.
• No Docker or containerized install. Manual PHP environment setup in 2026 is a meaningful friction point compared to alternatives with docker-compose one-liners.
• ActivityPub requires a queue worker that can fail silently. If the systemd service dies and you don’t notice, remote servers stop receiving your posts. There’s no dashboard to verify the worker is healthy [README].
• No managed cloud option. Micro.blog, Ghost(Pro), and others let you get the same outcome (own-domain publishing with Fediverse support) without touching a server. Known doesn’t offer that path.
• PHP 8.3+ dependency. Not a dealbreaker, but many cheap VPS providers default to older PHP versions, adding one more configuration step.
• Sparse third-party review coverage. No independent benchmarks, no Trustpilot reviews, no community comparison posts in the mainstream self-hosted forums. Hard to verify real-world performance claims.
• MongoDB as a canonical dependency is unusual for a PHP CMS and adds operational complexity compared to tools that run on SQLite or MySQL [merged profile].

---

Who should use this / who shouldn’t

Use Known if:

• You’re already in the IndieWeb community and want a platform that speaks WebMention and ActivityPub natively.
• You want a multi-author community site where everyone posts to a shared domain and you want genuine Fediverse federation.
• You’re comfortable with PHP, systemd, and manual server configuration — or willing to pay someone who is.
• POSSE (own your content, syndicate outward) is the specific workflow you want and you’ve evaluated the alternatives.

Skip it if:

• You’re a non-technical founder who hasn’t set up a Linux server before. The deployment complexity is real and the community support for troubleshooting is limited.
• You want a clean editorial CMS. Ghost is more polished, better documented, and has a clearer license.
• You want Fediverse integration without the ops burden. Micro.blog is $5/mo managed and handles ActivityPub correctly.
• The “NOASSERTION” license matters to your organization’s legal review.
• You’re evaluating for a production team environment. The unclear license, modest star count, and absence of enterprise features make it a difficult argument.

Skip it (pick WriteFreely) if:

• You want a minimal, fast, ActivityPub-enabled writing platform with a clear open-source license (AGPL) and a simpler deployment story.

---

Alternatives worth considering

• Ghost (self-hosted) — more polished editorial UI, TypeScript-based, clear MIT license on self-hosted version, strong documentation. No ActivityPub in the open-source edition. Ghost(Pro) adds $9+/mo.
• Micro.blog — $5/mo managed, custom domains, built for POSSE and IndieWeb, ActivityPub-native, no server setup. The direct managed alternative if Known’s ops burden is the blocker.
• WriteFreely — minimalist long-form publishing with ActivityPub support, AGPL licensed, simpler Docker deployment. Better fit if writing-focused rather than multi-media social publishing.
• WordPress + IndieWeb plugins — the nuclear option. Full IndieWeb suite available as plugins (Webmention, Micropub, etc.), massive community, more complex. Clear license.
• Mastodon — if the actual goal is Fediverse presence rather than a personal canonical domain, Mastodon does that job better and the deployment story is more mature.
• Hugo or Eleventy (static) — if you want content ownership without the social features, static site generators have zero ops overhead and infinite longevity.

---

Bottom line

Known is a coherent answer to a specific question: “How do I run a multi-author social publishing site on my own domain, with WebMentions and ActivityPub, so my content isn’t hostage to any platform?” For that specific question, it works. The IndieWeb philosophy is embedded in the architecture, not bolted on.

The problems are real though. The license ambiguity (NOASSERTION) is a genuine blocker for anything beyond personal use. The deployment story — manual PHP, MongoDB, systemd queue workers — is meaningfully harder than the Docker-first tools that have become standard. And the modest community around the project means you’re more on your own when something breaks.

If you want own-domain social publishing with Fediverse support and you can run the server, Known is a legitimate option. If the ops burden is the problem, Micro.blog at $5/mo gets you to the same philosophical destination without touching a command line. And if you want a self-hosted CMS that’s more actively maintained, better documented, and has a clear license, Ghost or WriteFreely are the cleaner choices.

---

Sources

1. Known — Official Website (withknown.com). https://withknown.com/
2. Known (Idno) — GitHub Repository and README (1,108 stars). https://github.com/idno/idno