Hugging Face finally lets orgs publish blog posts—but there's a paywall

Hugging Face shipped a feature on January 20, 2025 that seems so basic you’d assume it already existed: organizations can now publish blog articles directly under their org profile. The announcement, tucked into a Team Article post, is less than 100 words long and comes with a catch that’ll frustrate smaller teams.

The workflow is dead simple. When you head to huggingface.co/new-blog to draft a post, a new dropdown lets you select an organization instead of your personal account. Hit publish, and the article shows up under that org’s profile rather than an individual contributor’s page. For open-source projects and companies that use Hugging Face as their primary developer hub, this stops the awkward dance of having a lead engineer’s personal blog serve as the de facto company newsfeed.

But the “Note” in the announcement is doing a lot of heavy lifting: organizations need an Enterprise Hub subscription to unlock this. Hugging Face doesn’t disclose Enterprise Hub pricing publicly—you have to contact sales—but the tier is aimed at companies with serious compliance and governance needs. That means indie research collectives, community ML groups, and startups not yet ready for enterprise contracts are still stuck posting from individual accounts.

This feels like a missed opportunity to shore up goodwill with the broader community. Hugging Face has spent years building its reputation as the open, collaborative home for machine learning, and something as straightforward as org-level blogging shouldn’t require a sales call. The company has been steadily layering enterprise features on top of the platform—SSO, audit logs, resource groups—and this slots neatly into that monetization playbook. But when GitHub has offered org-level pages and repos on free plans for years, gating a blog post feature behind an opaque enterprise tier feels more like a squeeze than a value-add. The real test is whether this nudges enough teams to open their wallets, or just reminds everyone that the collaboration layer they rely on is increasingly a product with a price tag.