Hashnode Guide: Own-Domain Blogging (2026)

If you write technical content and want a blog that lives on your own domain instead of someone else's, Hashnode has been one of the default answers since 2020. It gives you a hosted editor, a built-in newsletter, and a community feed layered on top of a blog you actually own. What changed in 2026 is the price of admission: several of the features that made Hashnode worth choosing over Medium or a bare WordPress install, custom domains, the API, scheduled publishing, are no longer automatically free. This guide covers what Hashnode is, what's free versus Pro in mid-2026, how its distribution actually works, and how it stacks up against Dev.to, Medium, and self-hosting.

This is a long read (about 15 minutes). Use the table of contents to jump to what you need.

What is Hashnode?

Hashnode is a blogging platform built specifically for developers, founded in 2016 by Sandeep Panda and Syed Fazle Rahman.¹ It relaunched in June 2020 around a specific pitch: blog on your own custom domain, own your content outright, and never worry about a paywall blocking your readers.² That pitch resonated. Hashnode raised a $2.1 million seed round led by Sequoia India's Surge in December 2020,³ then an $6.7 million Series A in August 2021 led by Salesforce Ventures, with angels including Guillermo Rauch and Naval Ravikant, bringing total funding to roughly $10 million.⁴ In the twelve months leading up to that raise, Hashnode grew from 100,000 to 1 million monthly active users and reached 60,000 active blogs.⁵

The founders framed the pitch in explicitly ownership-first terms: "We launched Hashnode last year based on the fundamental idea of blogging on a custom domain and owning the content, which instantly resonated with the developer audience," they wrote at the time of the Series A. "Developers are becoming aware of content ownership, and personal branding. They understand if they are publishing their content on a third-party website in exchange for views, they are doing it wrong."⁶

Fast forward to 2026: both co-founders have since started a new company, Bug0, focused on AI-driven software testing. Fazle Rahman has described Hashnode as "a developer media platform with millions of users" that the team has run for five years,⁷ a more general figure than the precise MAU numbers Hashnode reported around its Series A. Hashnode itself is still actively developed; its public changelog shows entries through at least July 11, 2026.⁸ But 2026 has clearly been the year Hashnode shifted from growth-at-all-costs to monetization, and the details of that shift matter for anyone planning to build on the platform.

Key Hashnode statistics in 2026

Treat the MAU and active-blog figures as a snapshot of Hashnode's growth phase around 2021 rather than a current count; Hashnode has not published a comparably specific user number since, and the co-founder's 2026 description ("millions of users") is intentionally looser. The homepage's rolling 24-hour counter is the most current, if narrow, activity signal available as of this writing.

The core model: your domain, your content, no paywall (mostly)

Hashnode's pitch has stayed consistent since 2020 even as pricing has changed underneath it. You get a blog on username.hashnode.dev by default, or on a custom domain you own, with free SSL provisioning. Hashnode's terms of service assert that you retain ownership of the content you publish,⁹ and the platform has always positioned itself explicitly against Medium's paywall model: no reader paywalls, ever, on Hashnode-hosted content.¹⁰ There's also a built-in newsletter with double opt-in, CSV import from Medium, Substack, or Ghost, and open and click metrics in the blog dashboard,¹¹ which is a meaningfully different value proposition than Dev.to, which has no equivalent native newsletter tool.

What changed is which parts of that model are free. As of the June 11, 2026 launch of Hashnode Pro, the free plan is limited to one publication on a hashnode.dev subdomain.¹² Custom domains, the GraphQL API, headless mode, webhooks, GitHub backup, native scheduled publishing, and the redesigned AI writing tools all sit behind Hashnode Pro at $5/month or $50/year, with support for up to 10 publications on one account.¹³ Accounts that already had a custom domain connected before the change were grandfathered onto the free plan for that domain, so if you set up Hashnode in 2024 or early 2025 and never touched your plan settings, you may still be running on the old free terms. New sign-ups do not get that grace period.

Practically, this means the honest 2026 pitch for Hashnode is: free to try, genuinely inexpensive to run seriously, but no longer free to run the way most tutorials from 2021 to 2024 describe it. If you're evaluating Hashnode against alternatives like WordPress or a fully owned blog, budget the $5/month in your comparison.

Distribution: your domain's SEO plus a shrinking community feed

Hashnode's distribution model is genuinely dual, and understanding both halves matters for setting expectations.

Your own domain. Every article published on a Hashnode custom domain accrues to that domain's SEO, not Hashnode's. This is the platform's core structural advantage over Dev.to and Medium: publish consistently on blog.yourdomain.com for a year, and you're building your own domain authority, not a third party's.¹⁴ The caveat worth stating plainly: articles on the default hashnode.dev subdomain do not inherit hashnode.com's domain authority the way, say, a Medium subdomain post benefits from Medium's overall traffic. The custom domain is where the real SEO value lives, which is exactly the feature that now sits behind Pro for new accounts.

The community feed. Separately, articles also surface in Hashnode's Explore feed, tag pages, on-platform recommendations, and the Hashnode Forums, added February 28, 2026, as a dedicated Q&A space.¹⁵ This is Hashnode's answer to Dev.to's community reach, and it's real, but it's noticeably smaller. Developer and technical writer Shahed Nasser put it bluntly in a widely cited comparison: "it's not easy to get much traffic in Hashnode... you wouldn't generate the same kind of traffic you would at DEV."¹⁶ That's a useful expectation-setter: don't choose Hashnode expecting Dev.to-level discovery traffic from the feed alone.

The playbook that has emerged from that gap is straightforward and widely practiced: publish the canonical version of an article on your Hashnode custom domain to capture the SEO benefit, then cross-post the same piece to Dev.to with a canonical URL pointing back to Hashnode. You get Dev.to's community reach without splitting SEO credit, since the canonical tag tells search engines which version is authoritative.

Content formats: editor, series, pages, and native scheduling

Hashnode's editor is a Markdown-based WYSIWYG with slash commands, embeds, and AI writing assistance, redesigned in February 2026 as part of a broader platform refresh.¹⁷ A "zen mode" and drag-and-drop image support were added as recently as July 11, 2026, indicating the writing experience is still being actively iterated on even as monetization tightens elsewhere.¹⁸

Beyond single articles, Hashnode supports:

• Series: grouping related articles into a numbered sequence, useful for tutorials or multi-part deep dives.
• Static pages: an about page, a contact page, or anything outside the article stream.
• Widgets: third-party embeds you can place inline in an article or pin to your blog's sidebar.
• Drafts with shareable preview links: send an unpublished draft to a colleague or editor for feedback before it goes live.
• Native scheduled publishing: set a future publish time from a draft's settings panel. The draft stays locked until it publishes or you cancel the schedule.¹⁹
• Raw Markdown URLs: as of June 23, 2026, appending .md to any published article's URL returns the raw Markdown source, a small but notable move toward making Hashnode content easy for LLMs and other automated tools to consume.²⁰

The scheduling feature and the AI writing tools are both now part of the Hashnode Pro bundle, alongside the API access covered next.

The GraphQL API: gql.hashnode.com, now Pro-only

Hashnode runs a single GraphQL endpoint at https://gql.hashnode.com, accepting POST requests only. The older api.hashnode.com endpoint has been discontinued. Authentication is a personal access token, generated from your Hashnode developer settings and passed in the request's Authorization header.²¹

The API surface covers the operations you'd expect from a headless CMS: a publishPost mutation for immediate publishing, createDraft for saving unpublished content, and scheduleDraft, which takes a draft ID and an ISO 8601 publishAt timestamp to queue a future publish.²² There are also queries for fetching publications, posts, and running search against Hashnode's content.

The change that matters most for anyone building on top of Hashnode: as of May 13, 2026, both read and publish access to the GraphQL API require a Hashnode Pro subscription.²³ Before that date, the API was usable on the free plan; developers building integrations, static-site generators, or scheduling tools against Hashnode's API now need their Hashnode account (or the account they're integrating on behalf of) upgraded to Pro. Hashnode also shipped an official GraphQL agent skill for Claude Code, Cursor, and GitHub Copilot on June 18, 2026, aimed at helping AI coding assistants work with the API correctly,²⁴ which suggests the company still sees developer tooling and agent-driven workflows as a priority even as it monetizes the underlying access.

Headless Hashnode is the other API-dependent pattern worth knowing. Hashnode publishes an official Next.js and Tailwind starter kit on GitHub for building a fully custom frontend against the GraphQL API,²⁵ which is how teams run a blog at a /blog subpath of their own marketing site while writers keep using Hashnode's editor on the backend. Headless mode is explicitly part of the Pro feature bundle as of the June 2026 launch, so it now carries the same $5/month requirement as the raw API.

Why developers and devrel teams still use Hashnode in 2026

The core appeal hasn't disappeared, it's just no longer free by default. Own-domain hosting with effectively zero server maintenance remains a strong pitch for individual developers who want a blog without running WordPress or Ghost themselves.²⁶ For devrel and content teams, GitHub backup, publishing every article as Markdown into a repository, appeals directly to docs-as-code workflows, letting technical writing live under version control the same way code does; that feature is now Pro-gated as well. Headless mode lets a marketing or docs team keep full control of their site's frontend and design system while writers use Hashnode's editor purely as a content-entry tool, which is a common pattern for company blogs that need to match a broader brand site.

Hashnode also historically offered a "Hashnode for Teams" product for editorial workflows and multi-author publications.²⁷ Its current standalone status in 2026 is unclear from public sources; what is confirmed is that Hashnode Pro itself now supports up to 10 publications per account, which covers a meaningful chunk of what a small team would need without necessarily requiring a separate Teams product.

Hashnode vs Dev.to vs Medium vs Ghost or your own blog

Vs Dev.to: Dev.to's advantage is community reach on a shared, high-traffic domain at zero cost, and it's fully open source. Hashnode's advantage is your own domain, full design control, and a built-in newsletter, at the cost of weaker feed traffic and, since June 2026, a subscription fee for the features that made it distinctive. The practical answer for many technical writers, as noted above, is to use both: canonical on Hashnode, cross-posted to Dev.to.

Vs Medium: Medium gates a large share of content behind its Partner Program paywall and its algorithm tends to favor established, large publications over individual writers. Hashnode's pitch has always been the inverse: no reader paywall, a developer-specific audience, and full Markdown control. That contrast is one of the few pieces of Hashnode's original positioning that the 2026 pricing changes haven't touched.²⁸

Vs Ghost or a fully self-hosted blog: Ghost and a self-managed blog give you total control, including memberships and monetization you design yourself, but you pay for hosting and you're responsible for maintenance, security, and uptime. Hashnode was, until mid-2026, the managed alternative that gave you most of that control for free. The Pro-gating narrows that gap: at $5/month you're now paying something for a managed custom domain, which changes the calculus if you were already comfortable running Ghost yourself.²⁹ The tradeoff that comes with any hosted platform, dependency on someone else's pricing and roadmap decisions, was always there for Hashnode; 2026 just made it visible.

Posting to Hashnode in practice

posterly publishes articles to Hashnode as part of its unified content calendar, alongside your other social and blogging channels. Because Hashnode's GraphQL API now requires a Pro subscription for both read and publish access, you'll need your Hashnode account on Pro (or on a grandfathered plan with existing API access) for posterly's Hashnode integration to authenticate and schedule content. Once that's set up, Hashnode articles sit in the same calendar as your other posts instead of requiring a separate login to hit a publish time. If you're comparing this against manually scheduling from Hashnode's own draft settings, the tradeoff is the same one that applies across every platform posterly supports: one calendar, one place to plan, instead of switching between each platform's native scheduler. Details on setup live on our Hashnode scheduler page, and our pricing page covers plan tiers if you're weighing posterly's cost against Hashnode Pro's own $5/month fee.

For a broader look at what content actually performs well on developer-focused platforms versus general audiences, see our platform-specific content guide. And if GitHub itself is part of your distribution strategy alongside your blog, our GitHub guide covers how repos and profile READMEs function as a parallel audience channel.

Final word

Hashnode in 2026 is still a genuinely useful place to run a developer blog: an editor built for Markdown-first writing, a built-in newsletter, series and pages for structuring longer content, and a real (if secondary) community feed on top of whatever SEO value your custom domain accrues. What's different from the Hashnode of 2021 to 2024 is that the platform's best features, your own domain, the API, native scheduling, GitHub backup, headless mode, now cost $5 a month through Hashnode Pro, following the API paywall in May 2026 and the Pro launch in June. That's not a story of Hashnode failing; both founders have simply moved most of their attention to a new company, Bug0, while Hashnode keeps shipping and has chosen to monetize the parts of the product that used to be free.

The practical takeaway: budget for Hashnode Pro if you want the custom-domain SEO benefit and API access that make Hashnode worth choosing over Dev.to or a bare Medium account, treat community-feed traffic as a bonus rather than your primary distribution channel, and consider the Hashnode-plus-Dev.to canonical pattern if you want both the domain ownership and the wider community reach. For everything else in your content stack, our WordPress guide covers the fully self-hosted alternative if you decide platform dependency isn't worth even $5 a month.