Publify

A self-hosted Ruby on Rails publishing platform, honestly reviewed. No marketing fluff — just what you actually get when you try to run it in 2026.

TL;DR

• What it is: Open-source (MIT) Ruby on Rails blogging engine — multi-user, IndieWeb-aligned, with Twitter syndication and a plugin system [3].
• Who it’s for: Technically comfortable bloggers who want an IndieWeb-friendly self-hosted publishing platform and are willing to manage a Ruby/Rails stack. Not for non-technical founders [1][2].
• Cost savings: Publify itself is free (MIT). You need a VPS to run it ($5–20/mo). There is no SaaS tier to compare against — this is purely a self-hosted tool.
• Key strength: 20+ years of existence, genuine IndieWeb feature coverage (POSSE, h-review, self-hosted URL shortener), and an MIT license with no strings attached [1][3].
• Key weakness: Requires Ruby 2.5–2.7 and Rails 5.2.x — both are end-of-life. The Twitter integration at the heart of its pitch is now broken by API changes. Only 1,854 GitHub stars, minimal third-party reviews, and no evidence of an active user community in 2026 [3].

---

What is Publify

Publify is a Ruby on Rails web publishing platform that has been running in some form since 2004. The README calls it “the oldest Ruby on Rails open source project alive” [3]. It started life as a project called Typo and was eventually renamed Publify to reflect a broader mission around the IndieWeb movement — specifically the idea of self-hosting your own site and syndicating outward from it rather than living on someone else’s platform [1][3].

The core of the product is a multi-user blogging engine. On top of that it layers a short-message system designed to push posts to Twitter, text filters (Markdown, Textile, SmartyPants, @mention and #hashtag linking), a widget system with a drag-and-drop plugin API, custom themes and templates, and what the project describes as “advanced SEO capabilities” [2][3].

The IndieWeb wiki page [1] describes its implemented features as: POSSE to Twitter with short messages, h-review microformat support on default themes, a self-hosted URL shortener, PESOS (Publish Elsewhere, Syndicate to Own Site) for previously posted tweets, Markdown, Textile, Flickr import, auto-linking, Twitter handler discovery, and syntax highlighting.

That feature set reads like a 2010–2015 IndieWeb wishlist. And that is roughly when Publify’s active development peaked. The project repository exists, CI badges appear to pass, but the dependency requirements — Ruby 2.5–2.7 and Rails 5.2.x — tell a different story about where development momentum has gone [3]. Ruby 2.7 reached end-of-life in March 2023. Rails 5.2 was superseded several major versions ago.

The GitHub repository has 1,854 stars [merged profile]. For context, Ghost (the most direct modern comparison) has well over 46,000. WordPress (the incumbent) is effectively ubiquitous.

---

Why people choose it

The honest answer is that finding independent third-party reviews of Publify in 2026 is itself the data point. There are none of meaningful depth.

The IndieWeb wiki page [1] lists the known IndieWeb users who have run Publify on their primary self-identifying site: none currently active. The two past users listed are Frédéric de Villamil, who ran it from 2006 to 2016 before migrating to Medium, and Don Park, who ran it until approximately 2015 before his site became a static HTML page. The wiki page for Publify is marked as a stub needing expansion.

LinuxLinks [2] covers Publify briefly with a feature summary that is essentially a restatement of the README. There is no usability analysis, no real-world performance report, and no comparison with alternatives.

This absence of coverage is itself informative. People who choose Publify in 2026 are likely doing so for one of two reasons:

Historical continuity. They set it up years ago, it runs, and migrating a working blog is a project they have not prioritized. This is a legitimate reason to keep running it but not a reason to choose it fresh.

IndieWeb ideological alignment. The IndieWeb community values specific technical protocols: Webmentions, h-entry microformats, POSSE syndication. Publify implements several of these [1]. Someone building out a personal IndieWeb setup who happens to know Ruby might prefer a Rails app they can extend over a static site generator or a managed platform like micro.blog.

For the target audience of this site — non-technical founders looking to escape SaaS bills — neither reason applies.

---

Features

Based on the README [3] and LinuxLinks coverage [2]:

Publishing engine:

• Multi-user blogging with role-based access (Administrator, Publisher) [3]
• Text filters: Markdown, Textile, SmartyPants, @mention linking, #hashtag linking [2][3]
• RSS/Atom feed generation [1]
• Advanced SEO configuration [2][3]
• Custom themes and templates [2][3]
• Multilingual UI: English, French, German, Danish, Norwegian, Japanese, Hebrew, Simplified Chinese, Italian, Lithuanian, Dutch, Polish, Romanian, and others [3]

Social and syndication:

• Short-message system originally designed for Twitter POSSE [1][3]
• Self-hosted URL shortener [1]
• PESOS import from Twitter [1]
• h-review microformat support on default themes [1]

Extension system:

• Widget system [3]
• Drag-and-drop plugin API (sidebar plugins, in-page plugins) [2][3]
• REST API [merged profile]

Database support:

• MySQL, PostgreSQL, SQLite3 [3]

What is not here:

There is no Markdown-native editor of the type users expect in 2026. No built-in image optimization pipeline beyond ImageMagick integration. No mention of webhooks, headless CMS usage, or modern content APIs. The Twitter integration — a centerpiece of the original feature pitch — is functionally broken since Twitter/X ended free API access in 2023. No social syndication is available unless you manage API credentials separately.

---

Pricing: SaaS vs self-hosted math

Publify has no SaaS tier. There is no hosted version, no subscription, no pricing page. You either self-host it or you do not use it.

Self-hosted cost:

• Software: $0 (MIT license) [3]
• VPS to run it: $5–20/month depending on provider and specs
• Domain: $10–15/year
• Your time to set up and maintain a Ruby/Rails application stack

There is no direct SaaS equivalent to compare savings against, because Publify does not offer one. The comparison that makes sense is against Ghost Pro (the managed SaaS version of Ghost), which runs $9–25/month depending on tier, or WordPress.com, which runs $4–45/month. Self-hosting Publify theoretically gets you to $5–7/month, but Ghost self-hosted (Docker Compose, 30 minutes) achieves the same infrastructure cost with a dramatically better setup experience and active development.

The savings math that makes self-hosting compelling on other tools does not apply cleanly here because there is no Publify SaaS bill you are replacing.

---

Deployment reality check

This is where Publify diverges most sharply from modern self-hosted tools.

The README installation path [3] is not Docker Compose. It is:

bundle install
rake db:setup
rake db:migrate
rake db:seed
rake assets:precompile
rails server

That requires a working Ruby environment, Bundler, a configured database (MySQL, PostgreSQL, or SQLite), ImageMagick, and a compatible JavaScript runtime for asset compilation. The README specifies CRuby 2.5, 2.6, or 2.7 — versions that are no longer maintained and are absent from most modern VPS base images [3].

Getting Ruby 2.7 running on a 2026 VPS means either using rbenv/rvm to build from source or finding a base image that still ships it. This is a significant barrier compared to tools that provide a docker-compose up path.

Heroku instructions are in the README [3], but Heroku eliminated its free tier in 2022. Those instructions also require manually configuring S3 for file storage, modifying the Gemfile, and running migration commands via heroku run. The workflow is not wrong, but it assumes familiarity with Ruby deployment that most users choosing a blogging tool do not have.

What you actually need to run this:

• A VPS with at least 1GB RAM
• A working rbenv or rvm installation with Ruby 2.7
• Bundler and the gem dependencies (which may have upstream compatibility issues by now)
• A configured database
• A reverse proxy (nginx or Caddy) for HTTPS
• ImageMagick
• SMTP for email notifications

Realistic time estimate for a developer who knows Ruby: 2–4 hours. For anyone else: this project is not achievable without dedicated technical help, and even then the Ruby version pinning creates ongoing maintenance risk.

---

Pros and Cons

Pros

• MIT license with no restrictions. Genuinely free to use, fork, modify, or embed [3]. No commercial license, no “fair code” clause.
• 20+ years of existence. If longevity signals something about stability, Publify has been running in some form since 2004 [3]. It is not going to shut down because a startup pivots.
• IndieWeb protocol coverage. POSSE, h-review, self-hosted URL shortener, Webmention support via IndieWeb extensions [1]. For bloggers who care about these protocols, the feature coverage is genuine.
• Multi-user with roles. Supports teams at the publishing level, not just single-author blogs [3].
• Plugin and widget API. Extensible via a documented API [2][3].
• Multi-database support. MySQL, PostgreSQL, and SQLite3 — works with whatever you have [3].

Cons

• EOL dependencies. Ruby 2.5–2.7 and Rails 5.2 are end-of-life. This is not a minor caveat — it means no security patches on the runtime, increasing friction with modern hosting, and dependency rot over time [3].
• Twitter/X integration is broken. The short-message syndication system — one of the two headline features — requires Twitter API access that is no longer freely available [3]. This removes a core part of what made Publify distinct.
• No Docker Compose path. Installation requires managing a Ruby environment from scratch [3]. This is a high barrier for the self-hosted audience in 2026.
• No active community. Zero current IndieWeb users documented using Publify as their primary site [1]. No active third-party reviews. No apparent community forum.
• No cloud option. There is no managed Publify hosting to fall back on if self-hosting becomes a burden.
• 1,854 GitHub stars. Weak signal for a project that has been public since 2004 [merged profile]. Ghost hit 46,000+ in roughly a decade of active development.
• No modern editor experience. No block editor, no drag-and-drop content builder, nothing comparable to what Ghost, WordPress, or even Micro.blog provide.
• Heroku instructions are stale. The deployment guide points to the Heroku free tier, which no longer exists [3].

---

Who should use this / who shouldn’t

Consider Publify only if:

• You already run Publify and it works — migration overhead may not be worth it.
• You are an IndieWeb enthusiast who knows Ruby/Rails and wants to extend a platform that implements h-review, POSSE, and related protocols natively [1].
• You specifically need an MIT-licensed Rails-based blogging engine for embedding in a larger Rails application.

Do not use Publify if:

• You are a non-technical founder. Full stop. The Ruby environment setup alone will cost you hours before you write a single post.
• You need Twitter/X syndication — the integration is broken by API policy changes [3].
• You want an actively maintained platform. The dependency requirements suggest maintenance has stalled.
• You are starting a new blog in 2026 and want something that will still be easy to run in two years.
• You need a modern editorial experience (block editor, media management, scheduling).

For non-technical founders specifically: Ghost self-hosted is a one-afternoon Docker deployment, produces a professional publication, and has active development. WordPress is the default for a reason. Neither requires touching a Ruby version manager.

---

Alternatives worth considering

• Ghost — the direct modern comparison. Self-hosted via Docker Compose ($0 software, ~$6/mo VPS), actively developed, clean editor, newsletter support, memberships, 46,000+ GitHub stars. Ghost Pro cloud starts at $9/mo.
• WordPress — the incumbent. Larger plugin and theme ecosystem than anything else, massive community, actively maintained. Self-hostable or via WordPress.com. The default choice if you have no preference.
• Micro.blog — IndieWeb-aligned hosted platform at $5/mo, if managing infrastructure is not the point [1]. Cheaper than Ghost Pro with native IndieWeb support.
• Known — another IndieWeb-focused open-source publishing platform [2], arguably better maintained for IndieWeb protocol coverage than Publify today.
• WriteFreely — lightweight, federated (ActivityPub), minimal by design. Better for simple text-first blogs.
• Jekyll/Hugo with Netlify — static site generators. No database, no runtime maintenance. Suitable for technical bloggers.

The realistic shortlist for a self-hosted blog in 2026 is Ghost vs WordPress. Publify does not belong on that shortlist for a new deployment.

---

Bottom line

Publify is a historically significant project — the oldest surviving Ruby on Rails open-source application — but historical significance is not the same as current viability. Its two distinguishing features, the Twitter/X syndication system and its IndieWeb protocol coverage, are either broken by external API policy changes or better served by other tools today. The dependency on end-of-life Ruby versions and Rails 5.2 makes every new deployment a technical liability before it starts. The near-total absence of active users, third-party reviews, and community suggests the project is in maintenance mode at best.

If you are a Ruby developer with an existing Publify installation that works, keeping it running may be lower cost than migrating. If you are choosing a self-hosted blogging platform from scratch in 2026, Ghost covers the same IndieWeb-adjacent positioning with Docker Compose deployment, an active development team, and a modern editorial experience that your writers will not immediately revolt against.

If deployment is the blocker regardless of platform, that is what upready.dev handles — one-time setup, you own the infrastructure.

---

Sources

1. Publify — IndieWeb Wiki. IndieWeb wiki entry covering Publify’s history, IndieWeb feature implementation, and known users. https://indieweb.org/Publify
2. Publify — Simple Web Publishing Software. LinuxLinks product overview. https://www.linuxlinks.com/publify-simple-web-publishing-software/
3. Publify GitHub Repository and README. Primary source for installation requirements, feature list, and deployment instructions. https://github.com/publify/publify

Primary sources:

• Official project website: https://publify.github.io/
• GitHub repository: https://github.com/publify/publify (1,854 stars, MIT license)