Inkwell vs WriteFreely vs Plume
WriteFreely and Plume bring federated, minimalist writing to the fediverse. Inkwell takes a different path for editorial teams. Here is an honest three-way comparison.
If you are searching for a WriteFreely alternative, you have likely already met Plume too. All three projects let you own your blog on your own server, but they make very different bets about what blogging should be. This is an honest, vendor-neutral comparison to help you pick the right one. For a wider field, see our roundup of self-hosted blogging platforms for 2026.
WriteFreely: minimal, distraction-free, federated
WriteFreely is a Go-based, deliberately minimal writing platform. Its whole philosophy is to get out of your way: clean typography, a quiet editor, and almost no chrome. Crucially, it federates over ActivityPub, so a WriteFreely blog can be followed directly from Mastodon and the wider fediverse. If your priority is writing essays and reaching fediverse readers with the least possible friction, WriteFreely is excellent and well-loved for good reason.
The flip side of that minimalism is that WriteFreely intentionally omits heavier editorial features. There is no rich analytics suite or complex multi-author workflow baked in. That is a feature, not a bug, for solo writers who want calm.
Plume: Rust-based federation for communities
Plume is a Rust-based federated blogging engine that also speaks ActivityPub, and it is popular across European communities. It leans toward shared, multi-author instances where several writers publish under blogs on one server, with federation connecting them to the fediverse. Plume is community-maintained, so its pace and support depend on volunteer momentum rather than a vendor.
If federation and a community-driven, European-friendly project matter most to you, Plume is a strong, principled choice.
Inkwell: editorial features and multi-tenancy on .NET
Inkwell makes a different bet. It is a free, MIT-licensed, self-hosted engine built on ASP.NET Core and EF Core, targeting .NET 10, and it is multi-tenant by default so one install can host many independent blogs. Where WriteFreely and Plume optimise for federated minimalism, Inkwell optimises for teams that want editorial tooling.
- A full WYSIWYG editor with drafts, scheduling, autosave, and publish, rather than a Markdown-only flow.
- A built-in analytics dashboard, an audit trail, newsletter and subscriber management, and redirect rules in v1.0.1.
- Six Layouts and ten colour Presets for a typography-first look without touching code.
- Microsoft SQL Server (2019+ or LocalDB) as the database, fitting naturally into .NET shops.
- No telemetry and GDPR-compliant by architecture, since you host everything yourself.
One honest trade-off: ActivityPub federation is not Inkwell's focus. If being followable from Mastodon out of the box is essential, WriteFreely or Plume will serve you better today. Inkwell aims instead at organisations running multiple branded blogs with real editorial workflows.
Pick federation-first minimalism with WriteFreely or Plume; pick editorial tooling and multi-tenancy with Inkwell.
How to choose
Choose WriteFreely if you are a solo writer who wants the quietest possible editor and native fediverse reach. Choose Plume if you want Rust-based, community-driven federation, especially within European communities. Choose Inkwell if you are a team or agency that needs a WYSIWYG editor, many blogs per install, built-in analytics and newsletters, and a home on the .NET and SQL Server stack. If you are also weighing hosted-feeling tools, our Ghost versus self-hosted alternatives piece adds useful context.
Whichever you pick, you keep ownership of your content and your data. To see how Inkwell installs and runs, read the documentation.
Frequently asked questions
Is Inkwell a drop-in WriteFreely alternative?
Not exactly. Both are self-hosted and open-source, but WriteFreely focuses on minimal, ActivityPub-federated writing, while Inkwell focuses on a WYSIWYG editor, multi-tenancy, and built-in analytics on .NET. Pick based on whether federation or editorial tooling matters more.
Does Inkwell support ActivityPub federation like WriteFreely and Plume?
No. ActivityPub federation is the strength of WriteFreely and Plume, and it is not Inkwell's focus. Inkwell prioritises editorial workflows, multiple blogs per install, and analytics instead.
What database and stack does Inkwell use?
Inkwell is built on ASP.NET Core and EF Core targeting .NET 10, and it uses Microsoft SQL Server 2019 or later, or LocalDB. WriteFreely is written in Go and Plume in Rust.
Can one Inkwell install host many blogs?
Yes. Inkwell is multi-tenant by default, so a single install can host many independent blogs, each with its own Layout and Preset. This suits agencies and organisations running several branded sites.
Ready to host your own blog?
Inkwell is free, open-source, and self-hosted — your content, your server, your rules. Deploy in minutes on .NET 10.