DEV Community: DevToolsPicks

Best Tools for Building in Public in 2026

DevToolsPicks — Sun, 14 Jun 2026 03:50:10 +0000

Building in public is not just a marketing tactic. It is a forcing function. When you commit to sharing your progress publicly, you ship more consistently, think more clearly, and build an audience that grows alongside your product.

The friction is the enemy. If sharing an update takes 30 minutes, you will skip it most days. These five tools reduce that friction to the point where building in public becomes a habit rather than a chore.

Quick Verdict

Tool	Purpose	Free Tier	Starting Price
Typefully	Twitter/X threading and scheduling	15 posts/month	$8/mo (Pro, annual)
Kit	Email newsletter for audience ownership	Free to 10K subs	$25/mo (Creator)
Tella	Product demo and update videos	Limited free	$12/mo (Pro, annual)
Plausible	Traffic analytics with public sharing	30-day trial	$9/mo (Starter)
Notion	Public roadmap and changelog	Unlimited (personal)	$8/user/mo (Plus)

Typefully

Twitter/X is the primary network for building in public. Where founders announce launches, share revenue milestones, document failures, and build audiences before a single line of product code is written. Typefully is the tool that makes this consistent.

Pricing: The free plan allows 15 posts per month, enough to get started but tight for daily posting. Pro starts at $8/month (annual) and includes unlimited posts, X/Twitter analytics, AI writing assistance, multi-platform scheduling (X, LinkedIn, Bluesky, Threads, Mastodon), and up to 10 social accounts. The free plan is best treated as a trial.

What makes it worth using: The thread editor. Typefully shows you exactly how your thread will render on X before it goes live, with live character counts per tweet, numbered thread markers, and auto-split for long text. This matters because poorly formatted threads tank engagement. Writing in Typefully versus writing directly in X is the difference between structured drafting and reactive posting.

The queue feature lets you build a backlog of scheduled posts across multiple days so that you can sit down once and populate a week of content without being glued to your phone every morning.

The honest limitation: Typefully is focused on text-based social platforms. It has no support for Instagram, TikTok, or Facebook. For a solo indie hacker building in public, this is rarely a constraint, since Twitter/X and LinkedIn are the primary channels. If you need multi-platform visual content management, Buffer is a better fit. For building in public through threads and founder-style posts, Typefully is purpose-built for the job.

Kit (ConvertKit)

Twitter/X gives you reach. A newsletter gives you ownership. An algorithm change, an account suspension, or a platform shift can reduce your X following to zero reach overnight. Your email list is yours regardless of what happens to any platform.

Pricing: Kit is free to 10,000 subscribers with unlimited sends, landing pages, opt-in forms, and basic automations. The Creator plan starts at $25/month and adds advanced automation sequences, third-party integrations, and multiple newsletters. Pricing scales with subscriber count above 10,000.

What makes it worth using: Kit's automation and tagging system is built for the BIP use case. You can tag subscribers based on how they found you (from a specific thread, from a Product Hunt launch, from a Reddit post) and send targeted sequences based on that origin. When you launch a product, you can message only subscribers who have been following for more than 3 months and are more likely to become paying users.

The free tier is the most generous in its class. Beehiiv and Substack both have free options but with tighter limits or revenue cuts respectively. For an indie hacker starting out, Kit's free plan handles everything you need until you are well past 1,000 subscribers.

The honest limitation: Kit's writing editor is functional but not the most pleasant writing experience. Beehiiv and Substack have better newsletter reading experiences and stronger built-in discovery networks. If your primary goal is a standalone newsletter brand with publication-style design, those platforms are worth considering. For a SaaS-focused audience building alongside a product, Kit's automation depth wins. See the full comparison in the Kit vs Beehiiv vs Mailchimp breakdown.

Tella

Building in public on video means showing the product working, not just describing it. A 60-second demo of a new feature communicates more than three Twitter threads. Tella is the screen recorder purpose-built for this use case.

Pricing: Tella has a limited free plan where recorded videos expire after 7 days. Pro costs $12/month (annual) or $19/month (monthly) and adds unlimited video storage, 4K export, AI-powered editing, captions in 106 languages, analytics, and collaboration features. A 7-day trial is available with no credit card required.

What makes it worth using: The editing workflow. Unlike Loom, which is optimised for quick internal async communication, Tella is optimised for polished shareable demos. You get zoom effects, background replacement, multiple camera layouts, AI-generated subtitles, and clip-level editing without leaving the browser. A founder can record a product demo in 10 minutes and have something genuinely watchable rather than a raw screen recording.

The BIP use case is specifically demo clips shared on Twitter/X or embedded in newsletter updates. Tella exports and sharing links work well for this. For a detailed comparison of Tella against Loom and Supercut, see the screen recorder comparison.

The honest limitation: Tella has no free plan in the traditional sense. The 7-day video expiry on the free tier means you cannot use it indefinitely without paying. If you want free unlimited screen recording for internal use, Loom's free plan is more generous. Tella earns its cost specifically when you are creating polished shareable video content regularly.

Plausible

The most credible thing you can share when building in public is real numbers. Not screenshots that could be edited, but a live link to your actual traffic dashboard. Plausible has a public stats sharing feature built for exactly this.

Pricing: No free tier, but a 30-day free trial with no credit card. The Starter plan is $9/month for up to 10,000 monthly pageviews on one site. Growth at $14/month adds 3 sites and team access. A self-hosted Community Edition is also available for free.

What makes it worth using: The public stats link. In your Plausible settings, you enable public sharing with one toggle and get a permanent URL showing your real-time traffic. Sharing this link in your newsletter or on your profile page is a standard BIP practice. Readers can see your growth trajectory without you having to manually create charts or risk being accused of cherry-picking screenshots.

The dashboard is also fast enough to check in 30 seconds. Traffic by day, top sources, top pages, countries, devices. No configuration required, no funnel setup needed. For a solo founder who checks numbers once per day and needs to know three things quickly, Plausible is the right tool. For a broader look at analytics options, see the analytics comparison post.

The honest limitation: Plausible does not track individual user journeys, funnels, or event sequences. For understanding what users do inside your SaaS product, PostHog or Mixpanel are necessary additions. Plausible is for public-facing marketing analytics, not product analytics.

Notion

Your audience wants to know where your product is going. A public roadmap gives them a reason to follow your journey even before you have something to launch. Notion lets you publish a page publicly with a single link, making it the lowest-friction way to maintain an open roadmap and changelog.

Pricing: The personal free plan is unlimited for individual use: unlimited pages, unlimited blocks, custom domains for published pages, and basic sharing. This is sufficient for a public roadmap. The Plus plan at $8/user/month adds version history and advanced permissions.

What makes it worth using: The combination of database views and public publishing. You can build a roadmap as a Notion database with status columns (planned, in progress, shipped), publish the page publicly, and update it from the same workspace where you do all your other planning. No separate tool, no migration, no maintenance overhead.

A public changelog documents what you have shipped. A public roadmap shows what is coming. Together they give followers a reason to check back and give potential users confidence that the product is actively developed.

The honest limitation: Notion public pages load slowly compared to native websites. If your public roadmap gets significant traffic, the load time is noticeable. For a high-traffic public changelog, a dedicated tool like Featurebase or Canny performs better. For a BIP audience of a few hundred to a few thousand followers, Notion is fine. For a deeper look at how Notion compares for documentation and planning, see the best productivity stack post.

The Minimal Stack

Start with zero cost: Kit free + Notion free + Typefully free (15 posts/month). That covers a newsletter, a public roadmap, and basic Twitter/X scheduling for nothing.

When you have traffic worth tracking, add Plausible at $9/month. When you are shipping features worth demonstrating on video, add Tella at ~$15/month. When you are posting daily and need unlimited scheduling, upgrade Typefully to Pro at $8/month.

The full paid stack costs $32/month. At the point where building in public is worth $32/month in tools, it is almost certainly generating more than that in audience value.

Best Productivity Stack for Solo SaaS Founders in 2026

DevToolsPicks — Sat, 13 Jun 2026 03:50:09 +0000

Running a SaaS solo means you are the product team, the marketing team, the support team, and the admin team. The right stack does not make you a 10-person company. It removes the friction of being one person.

These five tools cover the non-technical essentials: keeping your thinking organised, growing your audience, automating the repetitive work, understanding your traffic, and shipping without losing track.

Quick Verdict

Tool	Purpose	Free Tier	Starting Price
Notion	Docs, notes, planning	Unlimited (personal)	$8/user/mo (Plus)
Kit	Email list and newsletter	Free to 10K subs	$25/mo (Creator)
Make.com	Workflow automation	1,000 credits/mo	$9/mo (Core)
Plausible	Privacy-first analytics	30-day trial	$9/mo (Starter)
Linear	Issue tracking and shipping	Free (up to 250 members)	$8/user/mo (Standard)

Notion

Notion is the central hub for everything that does not live in your codebase. Product requirements, feature ideas, SOPs, content calendars, investor updates, customer research notes. One workspace, one search bar, zero context switching to find something.

Pricing: The personal free plan is genuinely unlimited for individual use. Unlimited pages, unlimited blocks, custom domains for published pages, basic AI features. The Plus plan at $8/user/month (annual) adds unlimited version history, guest invites, and advanced permissions. For a solo founder, the free plan handles everything.

What makes it worth using over alternatives: The flexibility. Notion is a blank canvas that adapts to how you think, not a rigid tool with a fixed structure. You can build a simple reading list or a full project management system in the same workspace. The database and relation features let you connect a product roadmap to a content calendar to a feature request tracker without leaving the app.

The honest limitation: Notion is slow compared to a native notes app. If you have a large workspace with many databases, page loads can feel sluggish. For focused writing and daily notes, a faster tool like Obsidian is a better experience. For structured documentation and planning across categories, Notion wins. The Notion vs Obsidian vs Anytype comparison breaks down the difference in detail.

Kit (ConvertKit)

Every SaaS founder building for the long term needs an email list. When your product breaks, gets acquired, or when you want to launch something new, the email list is the only audience channel you fully own.

Pricing: Kit is free to 10,000 subscribers with unlimited sends, landing pages, opt-in forms, and basic automation. The Creator plan starts at $25/month and unlocks (for up to 1,000 subscribers, scaling with list size) unlocks advanced automation sequences, third-party integrations, and the free newsletter migration service. The Creator Pro plan adds subscriber scoring, newsletter referral system, and Facebook custom audiences.

What makes it worth using: The tagging and automation system is built for SaaS workflows. Tag subscribers when they sign up, when they activate a key feature, when they upgrade or downgrade. Build behaviour-based sequences triggered by real product events via webhooks. This is not a newsletter tool with product features bolted on. It is an email platform where audience segmentation is native.

The honest limitation: The free plan includes Kit branding on your landing pages and forms until you upgrade. The editor is less polished than Beehiiv or Substack for newsletter-first creators. If your goal is a publication-style newsletter, those platforms have better writing and discovery features. For a SaaS-first list with product-triggered automations, Kit is the right tool. For a full comparison, see the Kit vs Beehiiv vs Mailchimp breakdown.

Make.com

Every solo SaaS founder has a list of tasks that are done manually every week that could be automated. New user signs up, send a Slack notification. Stripe invoice failed, open a support ticket. Blog post published, auto-tweet a thread. Each one takes 5-10 minutes manually and adds up to hours per month.

Pricing: The free plan gives you 1,000 operations per month with 2 active scenarios. Make.com Core at $9/month (annual) gives you 10,000 operations and unlimited active scenarios. Pro at $16/month adds priority execution, larger file transfer limits, and custom variables.

What makes it worth using: The visual builder. You can see every step of a workflow as a connected diagram of modules. Building a 5-step automation that connects Stripe to Notion to Slack to email takes about 20 minutes and zero code. The breadth of integrations (over 3,000 apps) means most tools you already use have native modules.

The honest limitation: Make.com counts each module execution as one operation. A 5-step workflow triggers 5 operations, not 1. Complex workflows can burn through credits faster than expected on the free plan. Also, Make has a learning curve for anything beyond simple trigger-action patterns. For a detailed comparison of Make.com against Zapier and n8n, see the automation tools comparison.

Plausible

Google Analytics 4 is powerful and free. It is also unnecessarily complex for a solo founder who wants to answer three questions: where is my traffic coming from, which pages convert, and is traffic growing? Plausible answers all three in 10 seconds on a single dashboard.

Pricing: No free tier, but a 30-day free trial with no credit card required. The Starter plan costs $9/month and covers up to 10,000 monthly pageviews for one site. The Growth plan at $14/month adds 3 sites and team members. There is also a Community Edition that is self-hosted and free.

What makes it worth using: No cookie banner needed. Plausible collects no personal data and uses no cookies, so it is fully GDPR-compliant out of the box. This matters practically: no consent pop-up hurting your conversion rate, no risk of cookie compliance issues. The script is also lighter than Google Analytics, which means slightly faster page loads.

The numbers are more accurate than GA4 because Plausible is not blocked by most privacy-focused browsers and ad blockers. If your users are developers and indie hackers (and they are), a meaningful percentage of them block Google Analytics. Plausible they generally do not. For a deeper look at analytics options including PostHog and Fathom, see the analytics comparison post.

Linear

Most task management tools are built for teams. Linear is built for shipping software, which makes it the right fit for a solo developer who wants to track what needs to get done, what is in progress, and what is done without ceremony.

Pricing: Free for teams up to 250 members with unlimited issues, cycles, and roadmaps. The Standard plan at $8/user/month adds git integrations, advanced analytics, and insights. For a solo founder, the free plan is complete.

What makes it worth using: The speed. Linear is genuinely fast, with keyboard-first navigation and near-instant search. The issue workflow (backlog, todo, in progress, done) maps naturally to how developers work. Git commit linking means closing an issue from a commit message actually closes it in Linear. The weekly cycle view helps you think about what to ship in the next week without complex sprint planning.

Triage mode is worth calling out specifically. When you have a backlog of feature requests from users and bugs from testing, Linear's triage view lets you process every incoming issue in one pass: accept it into the backlog, close it, or add it to the current cycle. This takes about 10 minutes per week and keeps your backlog from becoming a graveyard of forgotten ideas.

The honest limitation: Linear is overkill for a pre-launch project or a project with just a few features. At that stage, a Notion database or even a simple text file works fine. Linear earns its place once you have a steady stream of bugs, feature requests, and planned work that you need to keep untangled.

Assembling the Stack

Start with what you actually need today, not what you might need at $10K MRR.

Pre-launch: Notion (free) + Linear (free). That is enough to plan and ship. Notion holds your product spec, your content ideas, and your customer research. Linear holds your tasks and bugs.

Post-launch with users: Add Plausible ($9/month) immediately to understand where traffic comes from. You cannot improve what you cannot measure, and GA4 is too slow and complex for the quick daily check you actually need. Add Kit (free to 10,000 subs) to start building your list from day one. Every person who signs up for your product and also opts into your email list is an asset you own regardless of what happens to your SaaS.

Growing: Add Make.com Core ($9/month) once you have enough repetitive tasks to justify automating them. Most founders hit this point around month 3-6, when manual processes (customer onboarding steps, weekly reports, notification routing) are taking more than a couple of hours per week.

The full stack at $18/month (Plausible Starter + Make.com Core) covers everything a solo founder needs to run the product, grow the audience, automate the work, and track what matters. Kit and Linear are free until you outgrow their free tiers. Notion stays free unless you need team collaboration features.

How to Handle EU VAT as a Solo SaaS Founder in 2026

DevToolsPicks — Fri, 12 Jun 2026 03:35:09 +0000

EU VAT on digital services is not optional. It applies from your first sale to an EU consumer, regardless of how small your SaaS is. Ignoring it does not make you exempt. It just means you are accumulating a liability.

The good news: there are two clean approaches, and one of them requires almost no work on your part.

The Two Approaches

Option 1: Use a Merchant of Record

A merchant of record (MoR) like Lemon Squeezy, Paddle, or Gumroad acts as the legal seller in each transaction. They collect VAT from your customers, remit it to the relevant EU governments, and send you the net amount. You have zero VAT compliance burden.

This is the right path for most solo indie hackers. You focus on the product. The MoR handles the compliance.

Option 2: Handle VAT Yourself via OSS

If you process payments directly through Stripe, you are the seller of record. You must register for EU VAT, collect the correct rate from each customer, and file quarterly returns through the EU One Stop Shop (OSS) system.

This is more work but gives you full control over pricing and payment flows. It is the right choice if you have pricing reasons to avoid MoR fees (typically 5-10% of revenue) or if you need direct relationships with your payment processor.

The €10,000 Threshold

If you are based in an EU country, there is a €10,000 annual threshold for cross-border B2C sales. Below this threshold, you can charge your home country's VAT rate on all EU sales instead of each customer's local rate.

Once you cross €10,000, you must either register for OSS or use an MoR.

Important: this threshold does not apply if you are based outside the EU. US, UK, Australian, and other non-EU founders owe local VAT from the very first sale to an EU consumer. There is no grace period. Most early-stage non-EU founders solve this by using Lemon Squeezy or Paddle from day one, which eliminates the obligation entirely.

B2B vs B2C: The Distinction That Changes Everything

VAT treatment depends entirely on whether your customer is a business or a consumer.

B2C (consumer): You charge VAT at the customer's country rate. Germany: 19%. France: 20%. Italy: 22%. Hungary: 27%. Luxembourg: 17%. You collect and remit this VAT.

B2B (business): Use the reverse charge mechanism. You charge 0% VAT and note "VAT reverse charge applies" on the invoice. The customer's business accounts for VAT under their own obligations. You owe nothing.

The test is simple: did the customer provide a valid VAT number? Validate it at the EU VIES tool (ec.europa.eu/taxation_customs/vies). Valid number: B2B, zero VAT. No number or invalid: B2C, charge local rate.

Most SaaS billing tools (Stripe, Paddle, Lemon Squeezy) have VAT number collection built in. Turn it on.

The VAT Decision Flow

How OSS Registration Works

If you go the self-registration route, here is the process:

Step 1: Register for Union OSS (EU founders) or Non-Union OSS (non-EU founders) through your country's tax authority online portal. EU founders register in their home country. Non-EU founders register in any EU member state they choose.

Step 2: Collect evidence. You need two non-contradictory pieces of location evidence per sale: billing address, IP address, phone country code, or bank details. Keep records for 10 years.

Step 3: Apply the correct VAT rate. Rates range from 17% (Luxembourg) to 27% (Hungary). Most billing tools can automate this by country.

Step 4: File quarterly returns. Deadlines are the end of the month following each quarter (Q1 due April 30, Q2 due July 31, Q3 due October 31, Q4 due January 31). One return covers all 27 EU member states.

Step 5: Pay. One payment to your member state of registration. They distribute to other countries.

Registration typically takes 30-60 minutes online. The first filing is where most founders struggle, since you need to categorise every B2C sale by customer country and VAT rate.

What Merchant of Record Actually Covers

When you use Lemon Squeezy or Paddle as an MoR, they handle:

VAT registration in all relevant jurisdictions
Charging the correct VAT rate at checkout
Collecting the VAT from customers
Filing returns in each country
Remitting VAT to governments
Managing audits if they occur

You receive payments net of their fees and net of VAT. Your accounting is simpler because the MoR revenue is your revenue, no VAT adjustment needed.

The trade-off is cost. MoR fees typically run 5-10% of revenue on top of payment processing fees. At $5,000/month in revenue, that is $250-500/month. At scale, many founders switch to self-managed OSS to reclaim that margin. For a detailed comparison of MoR options, see the Lemon Squeezy vs Stripe vs Paddle comparison and the Polar vs Lemon Squeezy vs Creem breakdown.

What to Do Right Now

If you are pre-revenue or very early stage: Set up Lemon Squeezy or Paddle from the start. The compliance cost of doing it yourself at early stage is not worth it.

If you are already processing payments via Stripe with EU customers and have not registered for VAT: You have a liability. The practical steps are: register for OSS immediately, account for back VAT owed (your accountant can advise on the right approach for your situation), and turn on VAT collection in your Stripe Tax settings going forward.

If you are above €10,000 in EU B2C sales: Register for Union OSS if you have not already. The quarterly filing is manageable once set up. Tools like Taxually, Quaderno, or TaxJar can automate the reporting.

If you are a non-EU founder just starting: Use an MoR from day one. You have no threshold protection and the compliance overhead of self-managing OSS as a non-EU business is significantly higher than for EU-based founders.

One thing that does not change your obligation: Being small. EU VAT authorities have been increasing enforcement on digital services, and "I didn't know" is not a defense. The rules have applied since 2015 and the OSS simplification has been in place since July 2021.

A note on ViDA: The EU's VAT in the Digital Age (ViDA) reform package was adopted in March 2025 and is in early implementation in 2026. The major changes (mandatory B2B e-invoicing, digital reporting requirements) do not affect solo SaaS founders until 2028-2030 at the earliest. The current OSS rules, thresholds, and B2B reverse charge mechanism described in this post remain in force throughout 2026.

Note: This post covers the general framework and is not tax advice. For your specific situation, consult a VAT accountant or a service like Taxually.

Best Ghost Alternatives for Indie Hackers in 2026

DevToolsPicks — Thu, 11 Jun 2026 03:25:08 +0000

Ghost 6.0 raised entry pricing in late 2025. Starter went from $9/month to $15/month, and the Starter plan now blocks paid membership tiers entirely. If you want to charge subscribers, you need the Publisher plan at $29/month.

For an indie hacker running a blog and newsletter on a tight budget, that is a meaningful jump. Here are four alternatives worth considering.

Quick Verdict

Tool	Best For	Free Tier	Starting Price
Beehiiv	Newsletter-first with 0% revenue cut	2,500 subs	$43/mo (Scale)
Substack	Zero upfront cost, audience discovery	Unlimited free	10% of revenue
Hashnode	Free developer blog, no membership needs	Full features	Free forever
WordPress	Full CMS flexibility, plugin ecosystem	Self-hosted free	~$6-10/mo (VPS)

Beehiiv

Beehiiv is the strongest Ghost alternative if your publication is newsletter-first. It combines a blog, email newsletter, and paid subscription tools in one platform, with one key advantage over Ghost: 0% take rate on paid subscriptions.

Pricing: The Launch plan is free for up to 2,500 subscribers with unlimited email sends, a website with custom domain, and basic analytics. No credit card required. The Scale plan starts at $43/month (annual) and unlocks monetization: paid subscriptions, ad network access, referral programs, A/B testing, and advanced segmentation. Scale pricing increases with subscriber count. The Max plan starts at $96/month (annual) and adds team features, multiple publications, and priority support.

The jump from free to Scale ($43/month) is steep. There is no middle tier. Kit offers a more gradual on-ramp if that gap concerns you.

What you get over Ghost: Better newsletter-native features. Beehiiv's discovery network, Boosts, and ad network are specifically built for newsletter growth. Ghost is CMS-first with newsletter added on. If most of your readers come via email rather than Google, Beehiiv fits the workflow better.

The catch: Beehiiv is newsletter-forward. If you want a blog that doubles as a CMS with custom layouts, theme control, and a content-heavy archive, Ghost's editor and theme system is more flexible. Beehiiv posts are functional but not as customizable for complex blog structures.

Who should switch: Indie hackers running a newsletter where paid subscriptions are a revenue goal and subscriber count matters more than design customization. The 0% take rate is the key reason: at $1,000/month in subscriptions, Beehiiv saves you $100/month compared to Substack (10% cut) while costing $43/month. That math works in Beehiiv's favour from roughly $500/month in revenue.

Who should not: Developers or founders who want a technical blog without newsletter features. Hashnode is a better fit.

Substack

Substack is the easiest switch from Ghost. No monthly fees, no server to manage, and an audience discovery network that Ghost cannot match. The trade is the 10% platform cut.

Pricing: Free to publish. Substack takes 10% of paid subscription revenue plus Stripe processing fees (2.9% + $0.30/transaction + 0.7% recurring fee). Total effective cost runs 13-16% of gross earnings. On $1,000/month in subscriptions, you pay roughly $130-160/month in combined fees. At $10,000/month, that is $1,300-1,600/month. Custom domains cost a one-time $50 fee.

What you get over Ghost: Zero risk to start. You pay nothing until readers pay you. The Substack network surfaces your writing to new readers organically via recommendations. For early-stage newsletters, that discovery mechanism is worth something real. Substack also handles payments, tax compliance, and subscriber management without setup.

The catch: The 10% cut does not scale well. A writer earning $5,000/month pays roughly $700/month to Substack in combined fees. Ghost Publisher at $29/month becomes cheaper than Substack the moment your subscriptions exceed around $350/month. Once you are past that threshold, staying on Substack is paying a tax on your audience.

Design flexibility is limited. Substack publications look like Substacks. There is no theme editor, minimal customization, and no ability to build a custom website experience.

Who should switch: Writers and indie hackers just starting a paid newsletter who want zero upfront cost and access to the Substack discovery network. Once you are consistently above $500/month in subscriptions, revisit the math.

Who should not: Anyone who has already built a substantial paid subscriber base. At that point, the 10% cut is a meaningful recurring cost and Ghost Pro or self-hosted Ghost will save money.

Hashnode

Hashnode solves a specific problem: free, fast, SEO-optimized technical blogging with custom domain support and no strings attached. For indie hackers who blog as a marketing channel rather than a monetization channel, it is hard to beat.

Pricing: The individual plan is completely free. You get unlimited posts, custom domain mapping, a built-in newsletter, AI writing assistance, analytics, automatic GitHub backup, and your content appears in Hashnode's developer community feed. No credit card, no trial period, no "free tier with a catch." Team plans start at $199/month for collaborative workflows, but a solo developer needs nothing beyond the free tier.

What you get over Ghost: Zero cost. Ghost Starter at $15/month costs $180/year. Hashnode is $0/year. For a developer whose blog drives inbound interest in their SaaS rather than subscription revenue, spending $180/year on Ghost when Hashnode does the job for free is hard to justify.

The community feed is a genuine bonus. New posts automatically appear in Hashnode's developer discovery feed, which gives new blogs immediate visibility without any promotion work.

The catch: Hashnode has no paid membership or subscription feature for individual creators. You cannot charge readers directly through Hashnode. If monetizing your audience via subscriptions is part of your plan, Beehiiv or Ghost are the right tools. Hashnode is a publishing platform, not a membership platform.

Design customization is also limited compared to Ghost. You can adjust colors and layout, but you cannot install arbitrary themes or build a highly custom front end without significant effort.

Who should switch: Developers and indie hackers who blog primarily for SEO, personal brand, and developer community visibility, not for subscription revenue. If your blog is a marketing channel for a SaaS rather than a standalone business, Hashnode eliminates Ghost's monthly fee entirely. For a broader look at how Hashnode compares to other newsletter platforms, see the Kit vs Beehiiv vs Mailchimp comparison.

Who should not: Anyone who needs paid memberships, has a highly customized visual identity, or runs a content business where the publication itself is the product.

WordPress Self-Hosted

WordPress powers over 40% of the web. For indie hackers who want full ownership, unlimited plugins, and no platform dependency, self-hosted WordPress remains the most flexible option.

Pricing: WordPress software is free and open source. Hosting costs $6-10/month on Hetzner CX22 or DigitalOcean Droplet. Add a domain ($10-15/year) and SSL (free via Let's Encrypt). For paid memberships, MemberPress starts at $399/year (roughly $200 first year with an intro discount). Total realistic cost for a blog with paid memberships: $80-200/year for infrastructure plus $150-200/year for a membership plugin.

What you get over Ghost: No monthly subscription fee and no subscriber count limit. A WordPress site with 50,000 subscribers costs the same to host as one with 500. Ghost Business at $199/month becomes necessary once you hit 10,000 members. WordPress does not enforce these caps.

The plugin ecosystem is unmatched. SEO, caching, image optimization, forms, e-commerce, course platforms, community features: every tool integrates with WordPress. Ghost's plugin ecosystem is small by comparison.

The catch: WordPress requires server management. Updates, backups, security patches, and performance tuning are your responsibility. Ghost self-hosted is also an option but requires similar DevOps work. If you want managed hosting without thinking about servers, Ghost Pro, Beehiiv, or Substack are simpler.

The editor is also showing its age compared to Ghost's clean writing experience. Ghost is genuinely more pleasant to write in than the default WordPress block editor.

Who should switch: Developers comfortable managing a VPS who want full control, no monthly fees, and access to the WordPress plugin ecosystem. Combined with Cloudflare for CDN and caching, a self-hosted WordPress site can handle significant traffic at VPS cost. For a comparison of hosting platforms that work well with self-hosted setups, see the Framer vs Webflow vs Carrd comparison.

Who should not: Non-technical founders who want a managed solution. The time cost of managing WordPress infrastructure outweighs the monthly savings unless you are already running servers.

How to Choose

If newsletters and paid subscriptions are the core of your business: Beehiiv. The 0% take rate is the deciding factor once you are consistently earning.

If you are just starting and want zero upfront cost: Substack. You pay nothing until readers pay you. Plan to migrate once you exceed $500/month in subscriptions.

If you blog to build SEO and developer brand with no monetization: Hashnode. Free, fast, and developer-community-integrated.

If you want full ownership and can manage a server: WordPress self-hosted. No subscriber caps, no monthly fees, maximum flexibility.

If you are happy with Ghost and the pricing change does not affect your plan, there is no compelling reason to switch. Ghost's editing experience and theme system remain excellent for creators who value those things.

Claude Fable 5 Just Launched: What It Means for Indie Hackers

DevToolsPicks — Wed, 10 Jun 2026 07:32:13 +0000

The model everyone spent two days speculating about is real. Anthropic launched Claude Fable 5 on Tuesday, and it's the most powerful Claude you can actually use. It's also the first model in a new tier the company calls Mythos-class, which sits a step above the Opus line you've been using.

Here's the honest version before the hype carries you off. Fable 5 is a real level up on hard problems. It also costs double Opus 4.8, it burns through rate limits twice as fast, and on a big slice of what indie hackers build day to day, you won't notice the difference. So the real question is not "is it better." It's "is it better at the thing you actually do, by enough to justify twice the bill." Let's get into it.

What Is Claude Fable 5?

Fable 5 is the public release of a model family Anthropic has been sitting on since April. Back then it previewed Mythos, a model so good at finding software vulnerabilities that Anthropic refused to release it publicly and locked it behind a vetted-partner program called Project Glasswing. Mythos could find zero-day exploits on its own. Powerful, and dangerous enough that it stayed private.

Fable 5 is how Anthropic ships that capability to the rest of us. It's the same underlying model as the new Claude Mythos 5, with one difference: Fable 5 has a safeguard layer on top. Mythos 5 stays restricted to Glasswing partners and vetted researchers. Fable 5 is the version you can call from the API today.

What actually shipped:

The API model ID claude-fable-5, live now on the Claude API, the Claude apps (Pro, Max, Team, Enterprise), Claude Code, Amazon Bedrock, Google Cloud, and Microsoft Foundry.
A 1M token context window and up to 128k output tokens per request.
Adaptive thinking always on, plus effort control, task budgets, memory, context editing, and vision.
Built for long-running, asynchronous work. It can grind on a coding or research task for an extended stretch without losing the thread.

How Much Does Claude Fable 5 Cost?

This is where indie hackers need to pay attention. Fable 5 is $10 per million input tokens and $50 per million output tokens. That's exactly double Opus 4.8, which sits at $5 and $25. It's still less than half what the old Mythos Preview cost partners ($25/$125), but next to what you're paying now, it is a real jump.

Two things soften it. Cached input drops to $1 per million, so cache-heavy workloads with long system prompts or repeated context get a lot cheaper. And the Batch API halves the whole thing to $5/$25 for jobs that do not need an instant answer.

Put real numbers on it. Take a solo SaaS making 1,000 API calls a day at 1,500 input and 800 output tokens each. That's roughly 45M input and 24M output tokens a month.

On Opus 4.8: about $825 a month.
On Fable 5: about $1,650 a month.
On Fable 5 through the Batch API: back down to about $825.

So at standard usage you're looking at twice the bill unless you batch or cache hard. You can sanity-check your own workload on the cost calculator.

One more cost most coverage skips: Fable 5 uses about twice the rate-limit allowance of Opus per request. On a Pro or Max plan, you'll hit your ceiling roughly twice as fast. Which brings up the one genuinely great deal here. Fable 5 is free on Pro, Max, Team, and Enterprise until June 22, 2026. After that, usage credits kick in. So for the next couple of weeks you can throw your hardest problems at the best public Claude for nothing.

How Good Is It, Really?

Strong, with an asterisk on the numbers. Anthropic says Fable 5 leads nearly every benchmark it tested and beats Opus 4.8 by more than 10% on some. The headline figures going around: 95% on SWE-bench Verified, 80% on SWE-bench Pro, and the top spot on Cognition's FrontierCode coding benchmark, ahead of both Opus 4.8 and GPT-5.5.

The asterisk: these are early, mostly self-reported or third-party numbers. Anthropic listed the evaluations it ran but has not published the full raw scores on its model page yet. Treat the benchmarks as a strong directional signal, not gospel, until the system card numbers are public.

The partner results are more concrete and more telling. Stripe said Fable 5 did a Ruby migration on a 50-million-line codebase that would have taken a team more than two months, and it finished in about a day. Lovable's CTO said apps that took a hundred prompts a year ago now get one-shotted. That is the jump that matters: not a few benchmark points, but work that used to stall now finishing.

The catch is where those gains live. They are biggest on genuinely hard, long-horizon work: massive refactors, multi-step research, autonomous agent runs that go for hours. On a normal CRUD feature or a routine bug fix, Opus 4.8 lands in the same place. You'd be paying double for headroom you might rarely touch.

When Does Fable 5 Quietly Become Opus 4.8?

This is the part you have to understand before you build on it. Fable 5's safeguard layer isn't a refusal filter. It's a set of classifiers watching for misuse in four areas: cybersecurity, biology, chemistry, and model distillation. When a request trips one, Fable 5 hands that request to Claude Opus 4.8 and tells you the handoff happened. Anthropic says it triggers in fewer than 5% of sessions.

For most builders this never comes up. But if you build anything in those domains, it matters a lot. A security scanner, a pentest helper, a bioinformatics tool, anything that brushes cyber or bio: those requests silently drop to Opus 4.8 quality. You'd be paying Fable 5 prices and getting Opus 4.8 results on exactly the prompts where you wanted the extra power. The fallback is transparent, since you are told it happened, but know your category before you commit.

One more for teams: business and Bedrock users of Mythos-class models get a mandatory 30-day data retention window for safety monitoring. If you have client data or privacy commitments, factor that in.

Should Indie Hackers Use Claude Fable 5?

Here's the straight answer by who you are.

If you build a normal SaaS (auth, CRUD, dashboards, content, the usual): you don't need it as your default. Opus 4.8 handles that work at half the price, and Sonnet 4.6 handles most of it cheaper still. Save Fable 5 for the occasional hard problem. If you're not sure which Claude fits which task, the Sonnet vs Opus vs Haiku breakdown still holds. Just add Fable 5 at the top for the genuinely brutal stuff.

If you do heavy engineering (large legacy codebases, complex migrations, long autonomous agent runs): this is the one case where 2x the price can pay for itself. The Stripe result isn't marketing fluff if your reality is a sprawling codebase nobody fully understands. Test it on your worst refactor and see what happens.

If you're choosing between Claude and OpenAI: Fable 5 now sits at the top of the Claude lineup, above the Opus 4.8 that already traded blows with GPT-5.5. Our Opus 4.8 vs GPT-5.5 comparison is the place to start, and Fable 5 widens Claude's lead on the hardest coding and research tasks, at a price premium.

If you build in security, bio, or chemistry: learn the Opus 4.8 fallback first. You may be paying for a tier you can't fully reach in your own domain.

The move for almost everyone this week is the same. It is free on Pro, Max, and Team until June 22. Point it at the hardest thing on your plate, see if it clears work that Opus 4.8 could not, and let that decide whether it earns a spot in your paid stack. Don't switch your default API calls on benchmark hype alone. Switch because it finished something that was stuck.

The Bottom Line

Claude Fable 5 is the most capable model Anthropic has ever put in public hands, and on hard problems it's a real step up, not a rounding error. It's also double the price, twice as heavy on rate limits, and overkill for the bread-and-butter work most indie hackers ship. Use the free window to find out which camp your work falls into. For everyday building, Opus 4.8 is still the smart default. For the genuinely hard stuff, Fable 5 might just clear your backlog.

Next.js vs Nuxt vs SvelteKit for Indie Hackers in 2026

DevToolsPicks — Wed, 10 Jun 2026 04:45:09 +0000

Choosing a frontend framework for a new SaaS in 2026 comes down to three real options: Next.js, Nuxt 4, or SvelteKit. All three are free, open source, production-ready, and support server-side rendering, static generation, and full-stack API routes.

The choice is not about which one is technically superior. It is about which one fits your background, your team, and your deployment constraints. Here is the honest breakdown.

Quick Verdict

Framework	Best For	Ecosystem	Deployment	Learning Curve
Next.js	React devs, largest community	Huge	Best on Vercel	Medium-High
Nuxt 4	Vue devs, opinionated full-stack	Good	Flexible (Nitro)	Medium
SvelteKit	Solo devs, performance, DX	Growing	Flexible	Low-Medium

What Each Framework Actually Is

Next.js is a React framework built and maintained by Vercel. It adds file-based routing, server-side rendering, static site generation, server components, and API routes on top of React. As of 2026, the App Router is the default, replacing the older Pages Router. Server Components and Server Actions are stable.

Nuxt 4 is to Vue what Next.js is to React. It uses the Nitro server engine for deployments, supports Vue 3 with the Composition API, and is convention-heavy. Nuxt 4 was released through 2025 as an incremental, non-breaking upgrade from Nuxt 3. The current stable release is Nuxt 4.4.x. Nuxt 5 is planned with Nitro v3.

SvelteKit is the full-stack framework for Svelte 5. Svelte is fundamentally different from React and Vue: it is a compiler, not a runtime. Your components compile to vanilla JavaScript at build time with no virtual DOM. The result is smaller bundles, faster hydration, and code that reads closer to plain HTML/JS/CSS than either React or Vue.

Next.js

Next.js is the default choice for most developers in 2026 and it deserves to be. The React ecosystem is enormous, the community is massive, and the tooling (from UI libraries to starter kits) targets Next.js first.

What is genuinely good: The App Router, once you understand the mental model, is powerful. React Server Components let you fetch data at the component level without waterfalls. Server Actions simplify form handling significantly. Image optimization is excellent. Edge middleware is production-grade. And the ecosystem of SaaS starter kits built on Next.js (ShipFast, Supastarter, and others) means you can skip weeks of boilerplate.

The Vercel problem: Next.js is open source and runs anywhere, but some features work better or only on Vercel. Incremental Static Regeneration, optimized Image serving, and certain Edge Runtime behaviors are Vercel-optimized. Self-hosting is possible but you give up some functionality and take on infrastructure management. For an indie hacker shipping a commercial product, Vercel Pro starts at $20/user/month. Not expensive for one developer, but the per-seat model stings as teams grow.

The complexity problem: React Server Components introduced a new mental model that many developers still find confusing. "use client" and "use server" directives, async components, and the distinction between server and client state require careful thinking. If you are working alone and move fast, context-switching between server and client logic adds overhead that does not exist in SvelteKit or Nuxt.

App Router vs Pages Router: If you are starting a new project in 2026, use the App Router. The Pages Router still works but is not where Vercel is investing. The security patches released for Next.js in May 2026 apply to both routers but highlight why staying on a current version matters.

Who should use Next.js: Developers who are already comfortable with React. Teams that need to hire, since the React/Next.js developer pool is the largest. Projects that need specific React-only libraries (three.js, Framer Motion, Radix UI) which may not have Svelte or Vue equivalents. Anyone using a React-based SaaS starter kit.

Who should not: Developers new to JavaScript frameworks who want the fastest path to shipping. Next.js has the most to learn, especially with the App Router mental model. If you are starting fresh with no React investment, there are faster paths.

Nuxt 4

Nuxt 4 is the right answer if you are already a Vue developer. It offers everything Next.js offers in terms of SSR, static generation, and API routes, but built on Vue 3's Composition API and the Nitro server engine.

What is genuinely good: The developer experience in Nuxt 4 is excellent. Auto-imports mean you do not have to manually import Vue composables, Nuxt utilities, or your own components. They just work. The file structure is opinionated and consistent: pages/, composables/, server/api/, middleware/. Nitro makes deployment flexible. You can deploy to Cloudflare Workers, AWS Lambda, Deno Deploy, or a plain Node.js server with the same codebase, without changing code.

Nuxt 4 shipped several meaningful improvements: enhanced data fetching with useFetch and useAsyncData factories, vue-router v5 integration, a built-in accessibility announcer, and a much-improved developer overlay. The migration from Nuxt 3 to 4 was notably smooth compared to the Nuxt 2-to-3 rewrite.

The Vue ecosystem gap: Vue's ecosystem is good but smaller than React's. If you need a specific UI component library, charting tool, or third-party integration, check whether it supports Vue before committing to Nuxt. Most major libraries have Vue support, but newer tools often release their React version first.

The indie hacker community gap: The honest reality is that most indie hacker content, tutorials, and starter kits target React/Next.js. If you get stuck, finding a solution in a r/indiehackers thread is easier with Next.js than Nuxt. This gap matters when you are building solo and cannot afford to spend a day debugging framework-specific issues.

Who should use Nuxt: Vue developers who know the Composition API well and do not want to context-switch into React. Developers who value convention over configuration and want Nitro's deployment flexibility. Teams with existing Vue codebases.

Who should not: Developers with no Vue experience who are picking a framework from scratch. There is no strong reason to choose Vue over React or Svelte if you are starting fresh. Nuxt's advantages are most clear when you already know Vue.

SvelteKit

SvelteKit + Svelte 5 is the most interesting framework pick for indie hackers in 2026. It hit 93% developer satisfaction in the State of JS 2025 survey, which is the highest of any reactive framework.

What is genuinely good: Svelte compiles your components to vanilla JavaScript. There is no virtual DOM and no runtime framework overhead. The output is smaller, hydration is faster, and the resulting JavaScript bundles are consistently leaner than equivalent React or Vue applications.

The syntax is genuinely cleaner. In Svelte 5, reactivity is handled via runes: $state, $derived, and $effect. These read closer to plain JavaScript than React's useState and useEffect hooks. There is no JSX. Your HTML looks like HTML, your CSS stays in the component, and your JavaScript is mostly just JavaScript.

SvelteKit 2 added remote functions in early 2026, which let you define server-side functions alongside your components and call them without writing manual API routes. Server-side error boundaries also landed recently. The framework is actively developed with monthly releases.

Deployment flexibility is strong. SvelteKit adapters support Vercel, Netlify, Cloudflare Workers, Node.js, static hosting, and more. Unlike Next.js, there is no single "preferred" platform. You can host a SvelteKit app on a $6/month Hetzner VPS without giving up any framework features.

The ecosystem gap: This is SvelteKit's real weakness. The React component ecosystem is much larger. Many UI libraries have no Svelte version. If you need a specific complex component (a rich text editor, a date range picker, a complex chart), you may need to build it yourself or use a JavaScript library without native Svelte bindings. The starter kit ecosystem is smaller than Next.js. That said, the gap is narrowing. Svelte-specific UI libraries like Shadcn-Svelte, Skeleton UI, and Flowbite Svelte cover most common patterns. For an indie hacker building a standard SaaS (auth, dashboard, settings, billing), you can build the full UI without leaving the Svelte ecosystem.

The TypeScript story: SvelteKit has excellent TypeScript support. Svelte 5 generates accurate types for all component props, events, and slots. The type inference in load functions and form actions is genuinely good. If TypeScript is a requirement for your project, SvelteKit handles it well.

The hiring risk: If your project grows and you need to bring on developers, the pool of Svelte developers is smaller than React developers. For a solo indie hacker, this does not matter. For a 5-person team, it is a real consideration.

Who should use SvelteKit: Solo developers building a new SaaS who want the fastest development experience and do not have an existing React or Vue investment. Developers who value bundle size and runtime performance. Anyone building a content-heavy site or marketing-plus-dashboard product where Svelte's simplicity shines.

Who should not: Developers deeply invested in the React ecosystem who would need to rebuild their component library and tooling. Teams that need to hire junior developers quickly, since React expertise is far more common.

Head-to-Head on Key Dimensions

Bundle Size and Performance

SvelteKit ships the smallest bundles by a meaningful margin. Svelte components have no runtime overhead. For an indie hacker building a SaaS landing page plus authenticated dashboard, the performance difference is noticeable on mobile and low-bandwidth connections.

Next.js and Nuxt both ship React and Vue runtime code respectively. React's runtime is relatively large. For simple marketing pages, this overhead is real, though React Server Components help by shifting rendering work to the server. In practice, a well-optimized Next.js app performs well. The gap shows most clearly for sites with many small interactions where Svelte's compiled output avoids re-render overhead entirely.

Learning Curve

SvelteKit is the easiest to learn for most developers coming from plain HTML/CSS/JS. The mental model is straightforward. Nuxt 4 is also approachable if you know Vue. Next.js App Router has the steepest curve of the three in 2026 due to the server/client component distinction. Many developers who have been writing React for years still find the "use client" boundary confusing in production apps with complex data requirements.

Ecosystem and Third-Party Libraries

Next.js wins clearly. The React ecosystem has more UI libraries, more SaaS starter kits, more tutorials, and more Stack Overflow answers than Nuxt and SvelteKit combined.

Deployment Flexibility

Nuxt (Nitro) and SvelteKit are both more flexible than Next.js. Both run well outside their "native" platforms. For self-hosting on a VPS, either is easier to work with than Next.js.

Community and Hiring

Next.js wins by a large margin. React developers are everywhere. SvelteKit is growing rapidly but the pool is smaller. Nuxt is in the middle.

My Pick for Indie Hackers

If you are building a new SaaS solo in 2026 and have no prior framework commitment: SvelteKit. The development experience is the best of the three, the deployment is flexible, and the performance is genuine. You trade ecosystem breadth for a faster, cleaner development loop.

If you are a React developer with an existing codebase or component library: Next.js. The investment is sunk. The App Router is powerful once learned, and the ecosystem advantage is real.

If you are a Vue developer: Nuxt 4. It is excellent, actively maintained, and the Nitro deployment flexibility is a genuine advantage.

The framework you will actually ship with matters more than the technically optimal choice. Pick the one you already know, or SvelteKit if you are starting fresh.

One more thing worth saying: framework decisions are not permanent. A SaaS landing page and marketing site can be migrated in a weekend. A complex app with years of custom components is a real migration. If you are in early stages, framework flexibility is high. Once you have 50+ components and a team that knows the codebase, the switching cost rises. Choose with your current situation in mind, not an imagined future where scale forces the decision for you. At indie hacker scale, all three frameworks perform well enough that none will be the bottleneck.

Best Tailscale Alternatives for Indie Hackers in 2026

DevToolsPicks — Tue, 09 Jun 2026 05:45:11 +0000

Tailscale is the easiest way to connect your devices and servers into a private mesh network. For a solo developer, the free Personal plan (up to 6 users, unlimited devices) is generous enough that you may never need to pay. But once you need to share access with more users, the per-user pricing on Standard ($8/user/month) and Premium ($18/user/month) adds up fast. A team of 5 on Premium costs $90/month just for networking.

If you are hitting the user limit, looking for a self-hosted option, or want to avoid depending on Tailscale's proprietary control plane, here are four alternatives worth considering.

Quick Verdict

Tool	Best For	Free Tier	Starting Price
NetBird	Full Tailscale replacement, self-hostable	5 users, 100 machines	$5/user/mo (Team)
ZeroTier	Simple mesh networking, small teams	10 devices, 3 networks	$5/mo flat (Essential)
Headscale	Self-hosted Tailscale control server	Free (self-hosted only)	Free
Cloudflare Tunnel	Exposing local services publicly	Up to 50 users	$7/user/mo

NetBird

NetBird is the most direct Tailscale alternative in 2026. It is fully open source (BSD-3 license), built on WireGuard, and the self-hosted version has zero per-user fees or device limits. The cloud-hosted version includes a free tier and competitive paid plans.

Pricing: Cloud free plan covers 5 users and 100 machines. The Team plan costs $5/user/month (or about $4.25/user/month billed annually) and supports unlimited users with SSO, SCIM provisioning, and audit logging. The Business plan at $10/user/month adds device posture checks, MDM integration, and traffic event logging. Self-hosted is completely free.

What you get over Tailscale: Full control. The entire control plane (management server, signal server, relay) is open source and can run on your own infrastructure. Since February 2026 (v0.65), a Unified Server Binary packages everything into a single Docker container, making self-hosting genuinely practical rather than a weekend project. No dependency on a third-party control plane.

The catch: Self-hosting means you manage the infrastructure. Updates, uptime, and monitoring are your responsibility. The cloud free tier is limited to 5 users, which is less generous than Tailscale's 6-user Personal plan. The admin interface is functional but less polished than Tailscale's.

Who should switch: Teams that need more users than Tailscale's free plan allows but want to avoid per-seat costs at scale. Any indie hacker with GDPR or data residency concerns who cannot have network topology data in a US-hosted control plane. Developers already comfortable running Docker who want to eliminate a recurring VPN bill.

Who should not: Solo developers on Tailscale's free Personal plan. If you have fewer than 6 users and unlimited devices already, Tailscale's free tier beats NetBird on simplicity with no server to maintain.

ZeroTier

ZeroTier is one of the oldest and most widely used mesh networking tools. It predates Tailscale and takes a slightly different approach: rather than a coordination server model, ZeroTier uses a distributed virtual networking layer where devices communicate over ZeroTier's planet/moon infrastructure (or your own moons for self-hosted control).

Pricing: The Basic plan is free for up to 10 devices and 3 networks. The Essential plan costs $5/month flat plus $2/device for each device over 10. Commercial plans offer volume pricing for larger deployments.

What you get over Tailscale: Simpler pricing for small setups. $5/month covers a solo developer's full infrastructure regardless of how many teammates or contractor accounts you add, up to 10 devices. No per-seat fees until you hit the device limit. ZeroTier also has a self-hosting option via ZeroTier moons that lets you run your own network controller.

The catch: ZeroTier's interface is more technical than Tailscale's. There is no equivalent of Tailscale's MagicDNS (automatic DNS names for your devices) without extra configuration. The recent Essential pricing change (November 2025) made the paid tier simpler, but the free Basic tier now restricts commercial use, which catches out developers using it for work projects.

It is also worth noting that ZeroTier's architecture is slightly different from Tailscale and NetBird. Tailscale and NetBird create peer-to-peer encrypted tunnels directly between devices using WireGuard. ZeroTier uses its own virtual networking protocol. In practice both approaches work well, but WireGuard has a stronger security track record and is easier to audit.

Who should switch: Solo developers connecting fewer than 10 devices who want a flat monthly rate instead of per-user pricing. Homelab users who already know ZeroTier and want to stay on the platform.

Who should not: Anyone who needs the onboarding simplicity of Tailscale. ZeroTier's setup is still more manual than Tailscale's single-login-and-go experience. If you value the admin console and MagicDNS, Tailscale is worth the per-user cost.

Headscale

Headscale is not a separate network tool. It is an open-source reimplementation of the Tailscale coordination server, which means you can run your own control plane while still using the official Tailscale client apps on each device.

Pricing: Free. Headscale itself is MIT-licensed open source. You pay only for the server to run it, which is typically a $5-6/month VPS. A basic Hetzner CX11 or DigitalOcean Droplet handles the control plane load for dozens of connected devices without breaking a sweat.

What you get over Tailscale: Zero recurring fees. The Tailscale client experience (same apps, same MagicDNS, same key exchange) without paying Tailscale. For a solo developer connecting personal machines and servers, this is Tailscale's full mesh networking experience at VPS cost.

The catch: Headscale does not support every Tailscale feature. Tailscale Funnel (exposing services to the public internet), Tailscale SSH, and the web admin console are not available. There is no official support. Setup requires running a server and pointing your Tailscale clients at your Headscale instance rather than Tailscale's coordination server. It is a project maintained by the community, not a commercial product. If the project stalls or breaks compatibility with Tailscale client updates, you are on your own.

Who should switch: Developers who want the Tailscale client experience with no monthly cost and are comfortable managing a small server. Great for personal infrastructure: connecting your laptop, a home server, and one or two VPS instances.

Who should not: Anyone who needs Tailscale's advanced features (Funnel, SSH, ACL policies, admin console). Teams where non-technical users need to join the network. The setup friction is real. For anything business-critical, a supported commercial product is the safer choice.

Cloudflare Tunnel

Cloudflare Tunnel is not a Tailscale replacement in the mesh networking sense. It is worth including because it solves a problem that often comes up alongside Tailscale: exposing a local service (dev server, internal tool, webhook endpoint) to the public internet without opening firewall ports.

Pricing: Cloudflare Zero Trust free plan covers up to 50 users. The Teams plan costs $7/user/month. No bandwidth charges; traffic goes through Cloudflare's edge for free.

What you get over Tailscale: Public HTTPS access to a local service in under five minutes. Run cloudflared tunnel and your localhost:3000 gets a public HTTPS URL through Cloudflare's global edge network. No dynamic DNS, no port forwarding, no SSL certificate to manage. For exposing dev environments or internal dashboards to clients or collaborators who are not on your private network, this is far simpler than any mesh networking solution. If you are already running MCP servers or AI agents on local infrastructure, Cloudflare Tunnel is the fastest way to expose them, as covered in the guide to self-hosted Claude agents and MCP tunnels.

The catch: It is not a private mesh network. Traffic routes through Cloudflare, which means Cloudflare can see it (though HTTPS encryption protects content). Not suitable for sensitive internal communications between your own services. You are also adding a dependency on Cloudflare's infrastructure for service availability.

Who should switch: Developers who do not need a full mesh network but want to expose local services publicly without firewall gymnastics. Complementary to Tailscale, not a replacement.

Who should not: Anyone who needs device-to-device private networking. Cloudflare Tunnel is one-directional (local to public) and does not create a private network between your machines. For connecting your VPS, laptop, and home server privately, use Tailscale, NetBird, ZeroTier, or Headscale.

How to Choose

If you want to eliminate Tailscale's per-user costs entirely and can manage a server: Headscale for small personal setups, NetBird self-hosted for anything team-scale.

If you want a hosted alternative with a simpler pricing model: ZeroTier Essential at $5/month flat for small device counts, NetBird Team at $5/user/month for larger teams where SSO and audit logs matter.

If you just need to expose a local service publicly: Cloudflare Tunnel. It is free for up to 50 users and takes five minutes to set up.

If you have fewer than 6 users and do not need public tunneling: stay on Tailscale Personal. It is free and excellent. The reason to switch is either cost at scale or data sovereignty concerns. For more on managing infrastructure costs as a solo developer, the Vercel vs Hetzner breakdown covers where hosting decisions actually matter at different revenue stages.

Turso vs Neon vs Supabase for Indie Hackers in 2026

DevToolsPicks — Mon, 08 Jun 2026 03:20:30 +0000

Three databases that keep coming up in indie hacker conversations in 2026: Turso, Neon, and Supabase. They are not really competing for the same user. Once you understand what each one actually is, the choice becomes obvious.

This comparison will save you from picking the wrong one and migrating later.

Quick Verdict

Tool	Engine	Free Tier	Starting Price	Best For
Neon	Serverless Postgres	0.5 GB, scale-to-zero	$5/mo	Solo devs who want standard Postgres
Turso	SQLite (libSQL)	100 databases, 5 GB	$4.99/mo	Multi-tenant apps, edge, SQLite-first
Supabase	Postgres + platform	500 MB, 7-day pause	$25/mo	Full backend platform for MVPs

What Each One Actually Is

Before comparing features and pricing, the engine difference matters.

Neon is serverless Postgres. Pure, standard PostgreSQL with a serverless billing model that scales to zero when your database is idle. You can use every Postgres extension, every ORM, every tool in the Postgres ecosystem. If you know Postgres, there is nothing new to learn. Neon was acquired by Databricks in May 2025, which reduced pricing 15-25% and added SOC2 and HIPAA eligibility to the Scale plan.

Turso is a managed cloud service built on libSQL, a fork of SQLite. It is not Postgres. SQLite compatibility means your existing SQLite code works, but Postgres tooling does not. The core innovation is running hundreds or thousands of small databases cheaply, each one in a separate isolated file, with multi-region replication and the ability to embed a local replica directly inside your application for zero-latency reads. For the right use case, this architecture is genuinely powerful.

Supabase is a backend platform that includes Postgres, but the database is not the whole product. Supabase gives you auth (magic links, OAuth, JWT), file storage, realtime subscriptions, and edge functions alongside a managed Postgres database. If you think of Supabase as "just a database," you are underusing it and overpaying compared to Neon.

Pricing Compared

Free Tiers

Feature	Neon	Turso	Supabase
Storage	0.5 GB	5 GB	500 MB
Databases	1 project	100 databases	2 projects
Compute	100 CU-hours/mo	Unlimited	Shared (pauses)
Idle behavior	Scale-to-zero	Always on	Pauses after 7 days
Credit card required	No	No	No

Turso has the biggest free tier on paper. 5 GB and 100 databases beats Neon and Supabase on raw numbers. But the 100-database limit matters less unless you are building a multi-tenant app. Neon's free tier is more practical for a typical single-database SaaS: real Postgres, no pausing, scale-to-zero.

Supabase's 7-day inactivity pause is a real friction point. Your free project goes to sleep and takes several seconds to wake up when someone visits. For anything you demo to potential customers, this is an embarrassing first impression.

Paid Plans

Neon: Launch plan starts at $5/month minimum. Usage-based: compute at $0.14/CU-hour, storage at $0.35/GB-month. A typical small SaaS with moderate traffic runs $15-50/month. The Scale plan at $0.26/CU-hour adds read replicas, SOC2 Type 2, and HIPAA eligibility. No fixed monthly fee beyond the minimum.

Turso: Developer plan at $4.99/month unlocks unlimited databases and 9 GB storage. Scaler at $24.92/month adds 24 GB, team features, and 2,500 active databases per month. Pricing is flat-rate rather than usage-based, which makes budgeting easy.

Supabase: Pro plan at $25/month. Includes 8 GB database storage, 100 GB file storage, 50,000 monthly active users on auth, and no inactivity pausing. The fixed monthly price covers everything. Add-ons (compute upgrades, point-in-time restore, extra storage) are priced separately.

Feature Comparison

Database Branching

Neon has Git-style database branching built in. Create a branch of your production database in seconds with full copy-on-write isolation. Test schema migrations, run CI against real data, then apply. This is one of Neon's genuine differentiators.

Turso does not have branching in the same sense. Each database is its own isolated SQLite file, which provides natural isolation between environments, but not a Git-branch metaphor.

Supabase has branching in preview as of 2025. It works but is less mature than Neon's implementation.

Connection Model

Neon is serverless. Compute spins up when a query arrives and down when idle. Cold start latency is typically well under a second. A pooled PgBouncer connection string is provided for high-concurrency environments. For Laravel or other persistent-process frameworks, use the pooled connection string.

Turso is always-on for paid plans. Free databases on the free tier are also kept warm, unlike the old Hobby plan. SQLite embedded replicas run locally inside your application for sub-millisecond reads, which is a different architecture from any server-hosted database.

Supabase runs Postgres continuously on paid plans. No cold starts on Pro. The free plan pauses after 7 days of inactivity.

Ecosystem and Extensions

Neon supports all Postgres extensions available in standard Postgres. pgvector for AI embeddings, PostGIS for geolocation, uuid-ossp, pg_stat_statements, and anything else in the Postgres ecosystem work out of the box.

Turso is SQLite-compatible. Most SQLite extensions work, but the Postgres extension ecosystem is not available. No pgvector on Turso without building your own solution.

Supabase ships with a curated set of Postgres extensions pre-enabled. pgvector is included by default, which makes Supabase popular for AI-powered applications.

Real-World Cost Scenarios

Numbers on a pricing page are not always useful. Here is what each tool costs for three realistic indie hacker situations.

Scenario 1: Side project, 500 active users, low traffic

Neon: Free tier. 0.5 GB covers most small apps at this scale. $0/month.
Turso: Free tier. 100 databases, 5 GB, 500M row reads easily covers this. $0/month.
Supabase: Free tier, but your database pauses after 7 days of inactivity if traffic is light. Plan for the awkward wake-up or upgrade to Pro at $25/month.

Scenario 2: Growing SaaS, 5,000 active users, steady traffic

Neon: Launch plan. Estimated $15-30/month depending on query volume and storage growth. Scale-to-zero helps during off-hours.
Turso: Developer plan at $4.99/month if using a single database. If multi-tenant with one DB per user, still $4.99/month up to unlimited databases on 9 GB total. Very cost-effective for this pattern.
Supabase: Pro plan at $25/month flat. Includes 8 GB storage and all platform features. If you are using auth, storage, and realtime, this is better value than paying Neon plus separate services.

Scenario 3: Multi-tenant SaaS, 200 customers each with isolated data

Neon: Challenging. Neon gives you one database per project on the free tier, and running 200 separate Postgres instances gets expensive fast. Row-level security on a single database is the practical Neon approach.
Turso: Built for this. Developer plan at $4.99/month handles unlimited databases. 200 isolated SQLite databases with per-customer isolation is exactly the use case Turso optimizes for.
Supabase: Row-level security is Supabase's approach to multi-tenancy. It works well but keeps all customers in one database, which means one customer's heavy queries affect others. Supabase is not designed for database-per-tenant at scale.

Performance Considerations

Cold Start Latency

Neon scales to zero, which means the first query after an idle period wakes the compute. Cold start latency is typically under 100ms. For most web apps, this is imperceptible on the first request. For APIs where the first query is on the critical path of a response, consider keeping the connection warm or using the pooled connection string.

Turso paid databases are always-on. No cold start. For embedded replicas running inside your application process, reads are sub-millisecond because the database runs locally.

Supabase Pro is always-on. No cold starts. Free plan wakes from pause in several seconds, which is user-visible.

Write Throughput

SQLite handles concurrent writes differently from Postgres. SQLite uses write locking at the database level, which means only one write can happen at a time. For most SaaS apps with typical write patterns, this is never a bottleneck. But if your app has many concurrent writes (live collaboration, high-frequency events, auction-style bidding), Postgres on Neon or Supabase handles this more gracefully.

Neon and Supabase both use standard Postgres write handling. Row-level locking, multi-version concurrency control, and all the standard Postgres patterns work as expected.

Read Performance

For read-heavy apps on Turso with embedded replicas, read performance is unmatched. The database lives in the same process as your application. No network round trip at all.

Neon and Supabase both make network round trips for every query. Neon's edge network is designed to minimize latency, and read replicas on the Scale plan allow you to distribute reads. Supabase also offers read replicas on paid plans.

Developer Experience

Schema Migrations

All three support standard migration workflows. Neon's branching is the standout feature here: create a branch, run your migration against a copy of production data, verify it works, then apply. No risk to production. No spinning up a separate test database.

Supabase has a migration system built around their CLI and dashboard. It works well but is more opinionated about workflow than Neon.

Turso uses standard SQLite migration tooling. If you use Drizzle ORM or Prisma with SQLite support, migrations work the same way they would locally.

Local Development

Neon gives you a free branch for local development. Your local environment connects to a real cloud database without needing Docker or a local Postgres install. Branch-per-developer or branch-per-PR is a natural pattern.

Turso local development uses the Turso CLI to create local databases that sync with the cloud. The embedded replica feature means you can develop entirely offline and sync when you reconnect.

Supabase has the best local development story of the three. The Supabase CLI spins up a full local stack: Postgres, auth, storage, realtime, and edge functions all running locally via Docker. Local changes can be applied to production via migration scripts. This is genuinely good developer experience for teams using the full Supabase platform.

Prisma and ORM Support

All three work with Prisma. Neon and Supabase use the standard Postgres provider. Turso requires the Prisma SQLite adapter or the libSQL driver.

All three work with Drizzle ORM, which has first-class support for all three in its documentation.

For Laravel developers: Neon and Supabase both work with Eloquent via the standard Postgres PDO driver. Turso has a PHP/Laravel adapter maintained by the community, but it is less battle-tested than the Postgres path.

Use Neon if:

You are building a standard Postgres SaaS and want the cheapest serverless option. You need database branching for your CI/CD workflow. You want Postgres without the cognitive overhead of a full platform. You are migrating from PlanetScale after they removed the free tier.

Neon pairs well with Laravel, Django, Rails, or any framework with first-class Postgres support. For a deeper breakdown of what PlanetScale users should consider, see the best PlanetScale alternatives post.

Use Turso if:

You are building a multi-tenant SaaS where each customer has their own isolated database. You want a database-per-tenant architecture without the cost of running hundreds of Postgres instances. You are building an edge application and need SQLite embedded replicas for zero-latency reads. You are comfortable with SQLite and do not need Postgres extensions.

The key question is whether your app design genuinely benefits from many small isolated databases. If yes, Turso is purpose-built for this. If you have a single database with a users table and row-level security, Postgres on Neon or Supabase is simpler.

Use Supabase if:

You are building an MVP and want auth, file uploads, realtime, and a database in one platform. You want to ship a complete backend in a weekend without setting up Auth0 or Clerk separately. You are building an AI app and want pgvector ready out of the box. You do not mind the $25/month minimum once your project needs production reliability.

Supabase is the right call when the platform features matter, not just the database. If you only use the Postgres part of Supabase, you are paying $25/month for what Neon provides at $5-10/month. The best Supabase alternatives post covers what to consider if you outgrow the platform.

My Pick

For a solo developer building a typical SaaS in 2026, Neon is my pick. Real Postgres, free tier that does not pause, usage-based pricing that stays cheap while your app is small, and database branching that improves your deployment workflow. The Databricks acquisition means it is not a startup-risk bet anymore.

If you are building an MVP and want to avoid setting up auth separately, Supabase is worth the $25/month once you are past the free tier. It replaces several services at once.

Turso is the right choice in a narrow but real set of situations: multi-tenant architecture with database-per-tenant, edge applications, or any use case where SQLite's simplicity and embedded replicas matter more than Postgres compatibility.

Best PlanetScale Alternatives for Indie Hackers in 2026

DevToolsPicks — Sun, 07 Jun 2026 03:05:30 +0000

PlanetScale removed its free Hobby tier in April 2024. If you were using PlanetScale because it offered a free MySQL database with solid developer tooling, that option is gone. The cheapest plan is now $5/month for a single-node Postgres database, and a production-ready HA setup starts at $15/month.

PlanetScale also pivoted significantly in 2024-2025, moving from a MySQL/Vitess-only offering to adding PlanetScale Postgres. So if you were on PlanetScale for MySQL compatibility, the product has changed too.

That said, $5-15/month is still reasonable for a production database. The reason to look at alternatives is either the missing free tier for development databases, or a need for a different feature set: a full backend platform, edge SQLite, or distributed SQL at hyperscale. Here are four options worth considering.

Quick Verdict

Tool	Best For	Free Tier	Starting Price
Neon	Serverless Postgres, side projects	0.5 GB, scale-to-zero	$5/mo (usage-based)
Turso	SQLite, multi-tenant apps, edge	100 databases, 5 GB	$4.99/mo
Supabase	Full backend platform + Postgres	500 MB, pauses after 7 days	$25/mo
CockroachDB	Distributed SQL, high availability	$400 trial + $15/mo credit	Usage-based

Neon

Neon is the most direct replacement for PlanetScale in 2026. It is serverless Postgres with a real free tier, scale-to-zero billing, and database branching that works like Git branches for your schema.

Pricing: The free tier includes 0.5 GB of storage, 100 compute-unit hours per month, and scale-to-zero always active. No credit card required. The Launch paid plan starts at $5/month minimum, with compute billed at $0.14 per CU-hour and storage at $0.35 per GB-month. The Scale plan at $0.26/CU-hour adds read replicas, SOC2 Type 2, and HIPAA eligibility.

Neon was acquired by Databricks in May 2025 for approximately $1 billion. That acquisition reduced compute pricing 15-25% and cut storage pricing from $1.75 to $0.35/GB-month. If you evaluated Neon before mid-2025, the pricing is now meaningfully cheaper.

What you get over PlanetScale: A free tier, which PlanetScale no longer offers. Scale-to-zero means development databases and staging environments cost nothing when idle. Database branching lets you clone your entire database in seconds for testing schema migrations without affecting production.

The catch: Neon's free tier has a hard limit of 0.5 GB storage. For a growing SaaS with real user data, you will hit this quickly. The Launch plan's usage-based billing means monthly costs vary, which makes budgeting less predictable than PlanetScale's flat-rate plans. A typical small SaaS with moderate traffic runs $15-50/month on Launch, which is still cheaper than PlanetScale's $15/month HA entry point but harder to predict upfront.

One practical gotcha: frontend polling patterns (React Query intervals, WebSocket keepalives, health checks) can prevent scale-to-zero from activating. If cost optimization matters, audit what is keeping connections alive.

Who should switch: Solo developers and indie hackers building Postgres-based apps who need a free development database and want scale-to-zero economics for side projects with variable traffic.

Who should not: Teams with predictable, always-on production databases may find flat-rate pricing easier to budget. PlanetScale's $15/month HA setup is simpler to reason about than Neon's usage-based model.

Turso

Turso offers the most generous free tier of any database in 2026. You get 100 databases, 5 GB of storage, and 500 million row reads per month at no cost. The key difference from the other options: Turso is not Postgres. It is built on libSQL, a fork of SQLite.

Pricing: Free tier includes 100 databases, 5 GB storage, 500 million rows read per month, and 10 million rows written per month. The Developer plan costs $4.99/month and unlocks unlimited databases with 9 GB of storage. The Scaler plan at $24.92/month adds 24 GB and support for 2,500 active databases per month.

What you get over PlanetScale: The free tier is real and generous. The SQLite compatibility means your existing SQLite code, ORMs, and tools work without changes. Turso supports multi-region replication and embedded replicas, which place a local SQLite copy inside your application process for sub-millisecond read latency.

The catch: Turso is SQLite, not MySQL or Postgres. If your app depends on Postgres-specific extensions, functions, or tooling, Turso is not a drop-in replacement. SQLite also handles concurrent writes differently than traditional client-server databases, which can be a constraint for write-heavy workloads.

Who should switch: Developers building multi-tenant SaaS apps (database-per-tenant pattern fits perfectly with Turso's unlimited databases), edge applications, or local-first software where SQLite compatibility is an advantage. If you are building something like a note-taking tool, a developer CLI, or an app where each user has their own isolated dataset, Turso is built exactly for this pattern.

Who should not: Anyone whose app is tightly coupled to Postgres or MySQL and cannot move to SQLite. The database engine difference is not trivial to abstract away.

Supabase

Supabase is more than a database. You get Postgres plus authentication, file storage, realtime subscriptions, and edge functions in one platform. If you were using PlanetScale alongside a separate auth service and storage bucket, Supabase consolidates all of that.

Pricing: The free tier includes 500 MB of database storage, 1 GB of file storage, 50,000 monthly active users for auth, and up to 2 projects. Free projects automatically pause after 7 days of inactivity and take a few seconds to resume. The Pro plan costs $25/month with 8 GB database, 100 GB file storage, and no inactivity pausing.

What you get over PlanetScale: A complete backend platform. Auth, storage, realtime, and edge functions are all included. For solo developers building an MVP, Supabase can replace several services at once.

The catch: The free plan's 7-day inactivity pause is a real problem for side projects you check in on occasionally. Visiting your own app after a week of inactivity produces a slow first load while the database wakes up. This has caught out many indie hackers who demoed their app to a potential customer after a break and had an awkward 10-second wait. The Pro plan at $25/month removes this, but that is more expensive than Neon Launch or Turso Developer for a database-only need.

Supabase also does not scale to zero. Your Postgres compute runs continuously once you are on Pro. Good news: no cold starts. Less good news: you pay for compute all the time.

Who should switch: Indie hackers who want auth, storage, and realtime alongside their database and are happy to pay $25/month once their project needs production reliability. For a full overview of what to compare, the best Supabase alternatives post covers the full range of options in this category.

Who should not: Developers who only need a database. For a plain Postgres replacement, Supabase's additional platform features are overhead you do not need to pay for.

CockroachDB

CockroachDB fills a different gap. PlanetScale's Vitess product offered MySQL at hyperscale with horizontal sharding and multi-region high availability. CockroachDB is the closest alternative for that use case, though it is PostgreSQL-compatible rather than MySQL-compatible.

Pricing: The Basic plan offers a $400 trial credit and an ongoing $15/month in free resource utilization for pay-as-you-go accounts. Usage is billed based on Request Units (RUs) and storage per GB-month. The Standard and Advanced plans add dedicated resources and higher SLA guarantees.

What you get over PlanetScale: A free tier (PlanetScale has none), distributed SQL with multi-region deployment, and strong consistency guarantees across nodes. CockroachDB is built for the scenario where you need your database to survive datacenter failures without downtime.

The catch: CockroachDB is engineered for enterprise-scale problems. The pricing model (Request Units) is harder to reason about than flat-rate plans, and production costs can reach $500 to $5,000 per month depending on transaction volume. For an indie hacker building a typical SaaS app, CockroachDB is overkill. Neon or Supabase are the right tools; CockroachDB is relevant only if distributed SQL or multi-region compliance is an actual requirement.

Who should switch: Teams running MySQL on PlanetScale Vitess who need horizontal sharding, multi-region deployment, or survive-anything availability guarantees, and can move to a PostgreSQL-compatible interface.

Who should not: Solo developers building standard SaaS apps. The learning curve and pricing model are designed for engineering teams, not individuals.

How to Choose

If you just need to replace PlanetScale's free tier: Neon. Free tier, real Postgres, scale-to-zero, no credit card required.

If you are building a multi-tenant app or edge application and SQLite works for your stack: Turso. Most generous free tier in this category.

If you want auth, storage, and realtime alongside your database: Supabase. More expensive for database-only use, but replaces multiple services at once.

If you were on PlanetScale Vitess for distributed MySQL at scale: CockroachDB. Not a perfect swap (Postgres, not MySQL), but the closest alternative for high-availability distributed SQL.

For a deeper look at how Neon, Turso, and Supabase compare head to head on performance and developer experience, see the Supabase vs Firebase comparison for context on how the broader database-as-a-service market has evolved.

Best Netlify Alternatives for Indie Hackers in 2026

DevToolsPicks — Sat, 06 Jun 2026 03:05:27 +0000

Netlify moved to credit-based billing in September 2025 and updated pricing again in April 2026. The Pro plan is now $20/month with unlimited team members, which sounds good until you realize that credits are consumed by deploys, bandwidth, functions, and compute at different rates. Predicting your monthly bill has gotten harder.

The free tier still works well for personal projects (300 credits/month, one team owner), and the Personal plan at $9/month adds enough headroom for small production sites. But the moment you scale, the credit math becomes a puzzle. Credits are consumed by deploys, bandwidth, and serverless functions at different rates. If you are running a SaaS with moderate traffic, you can burn through 3,000 Pro credits faster than you expect.

If you are looking for something simpler, cheaper, or better suited to your stack, here are four alternatives worth considering.

Quick Verdict

Tool	Best For	Starting Price	Free Tier
Vercel	Next.js and React apps	$20/user/mo	Yes (personal only)
Cloudflare Pages	Static sites on a budget	$5/mo (Workers Paid)	Yes (unlimited bandwidth)
Railway	Full-stack apps with databases	$5/mo (Hobby)	Trial only ($5 credit)
Render	Predictable plan-based hosting	$7/mo per service	Yes (static sites + 750h)

Vercel

Vercel is Netlify's closest competitor and the default choice if you build with Next.js. The company literally created Next.js, so the integration is tighter than anything Netlify can offer.

Pricing: The Hobby plan is free for personal, non-commercial projects. Pro costs $20 per user per month and includes 1TB of bandwidth and $20 in usage credits. Enterprise is custom priced.

What you get over Netlify: Faster edge network performance for Next.js apps, tighter framework integration (incremental static regeneration works natively), and preview deployments that are slightly faster. If you are building with Next.js specifically, Vercel handles features like ISR and middleware better out of the box.

The catch: The Hobby plan cannot be used for commercial projects. That means the moment your side project earns its first dollar, you need Pro at $20/user/month. Per-seat pricing adds up fast for teams. A 5-person team pays $100/month before any bandwidth overages. Bandwidth overages apply after the 1TB included, and Vercel charges for all traffic including DDoS attacks unless you layer a separate CDN.

Who should switch: Indie hackers building Next.js apps who want the tightest possible framework integration and can stomach per-seat pricing. If you already use Vercel's preview deployments workflow, switching back to Netlify would feel like a downgrade.

Who should not: Anyone running a commercial project solo who wants to stay on a free plan. Netlify's free tier allows commercial use. Vercel's does not.

Cloudflare Pages

This is the most underrated hosting option for indie hackers in 2026. Cloudflare Pages offers unlimited bandwidth on every plan, including the free tier. That alone makes it worth considering over both Netlify and Vercel.

Pricing: The free tier includes unlimited bandwidth, 500 builds per month, one concurrent build, and a global CDN with 330+ edge locations. The Workers Paid plan at $5/month adds more build concurrency and access to Workers, KV, D1, and R2 for server-side logic and storage.

What you get over Netlify: Unlimited bandwidth means no surprise bills. Netlify's credit system makes it difficult to predict costs when traffic spikes. With Cloudflare Pages, a viral blog post or Product Hunt launch will not generate an unexpected invoice.

The catch: Cloudflare Pages is strongest for static sites and JAMstack apps. If your project relies heavily on serverless functions, you will need to learn Cloudflare Workers, which has a different API and execution model than Netlify Functions. The developer experience for dynamic features is not as polished as Netlify or Vercel. Build times can also be slower, and the build environment is more limited in terms of supported frameworks and build configurations.

One more thing to consider: the Cloudflare ecosystem is deep but fragmented. KV, D1, R2, Durable Objects, and Workers each solve different problems, but figuring out which combination you need takes time. Netlify wraps everything into one dashboard. With Cloudflare, you are assembling pieces.

Who should switch: Indie hackers hosting static sites, documentation, marketing pages, or blogs who are tired of worrying about bandwidth costs. If you already use Cloudflare for DNS (and you probably should), adding Pages to your stack is seamless.

Who should not: Teams building complex full-stack apps with heavy serverless function usage. The Workers ecosystem is powerful but has a steeper learning curve than Netlify Functions.

Railway

Railway is a different kind of alternative. Where Netlify and Vercel are frontend-first platforms, Railway handles your entire stack: web services, databases, background workers, and cron jobs. If you have outgrown the JAMstack model, Railway is worth a serious look.

Pricing: The Hobby plan costs $5/month and includes $5 in usage credits. Pro is $20/seat/month with $20 in credits. Usage beyond the credits is billed per second for CPU, RAM, storage, and network egress. A typical Node.js app with a small database runs about $10-15/month on Hobby.

What you get over Netlify: A complete hosting platform. Netlify can host your frontend and serverless functions, but if you need a persistent database, a background job runner, or a long-running process, you end up paying for Netlify plus a separate database service plus a separate worker service. Railway handles all of that in one place with one bill.

The catch: No permanent free tier. The trial gives you a one-time $5 credit, and after that you need the Hobby plan at minimum. Usage-based billing means your costs can vary month to month if traffic is unpredictable. And Railway is a younger company (founded 2020), which is a legitimate concern for long-term infrastructure decisions.

Who should switch: Solo developers and indie hackers building full-stack SaaS apps who currently use Netlify for the frontend and bolt on external services for everything else. If you are paying for Netlify plus PlanetScale plus a worker service, Railway can likely host all of that for less.

Who should not: Anyone who just needs static site hosting. Railway is overkill for a blog or documentation site. Use Cloudflare Pages instead.

Render

Render sits between the frontend-first platforms (Netlify, Vercel) and the full-stack platforms (Railway). It offers plan-based pricing that is easier to predict than usage-based models, plus a permanent free tier for static sites.

Pricing: Static sites are free forever. Web services start at $7/month per service. The Hobby workspace is free with compute costs on top. Pro workspace costs $19/user/month (Render removed per-seat fees for the base workspace in 2026, but Pro still charges per user). PostgreSQL starts at $6/month after a free 90-day trial.

What you get over Netlify: Native support for backend services, databases, and background workers alongside your frontend. Render's plan-based compute pricing (starting at $7/month per service) is easier to budget than Netlify's credit system or Railway's per-second billing. If you want to know exactly what you will pay before the bill arrives, Render delivers that.

The catch: The free PostgreSQL database expires after 90 days with no grace period. If you forget to upgrade, your data is gone. Web services on the free tier spin down after inactivity, causing cold starts of 30+ seconds. And once you add multiple services (API, worker, database, staging), costs add up. A typical full-stack app with a 3-person team, a web service, a background worker, and a database can reach $80-120/month on Pro. That is competitive with Railway but not cheap.

Who should switch: Indie hackers who want full-stack hosting with predictable, plan-based pricing and dislike usage-based surprises. If your project needs a backend but you find Railway's billing model confusing, Render is the simpler option.

Who should not: Anyone looking to save money on static site hosting. Render's free static hosting works, but Cloudflare Pages does it better with unlimited bandwidth and a faster global CDN.

How to Choose

If your project is a static site, blog, or documentation: Cloudflare Pages. Unlimited bandwidth for free. Nothing else competes on price.

If you are building with Next.js specifically: Vercel. The framework integration is unmatched. Accept the per-seat cost as the price of the best Next.js developer experience.

If you need a backend, database, and workers in one platform: Railway if you want the most modern developer experience and can handle usage-based billing. Render if you prefer predictable plan-based costs.

If Netlify's credit system is the only thing bothering you: check whether staying on Netlify with a clearer understanding of credit consumption makes more sense than migrating. The Vercel alternatives roundup covers more hosting options if none of these four fit. For a deeper look at full-stack deployment, the Railway vs Render vs Fly.io comparison breaks down the differences in detail.

When to Use Make.com vs Zapier vs n8n for Indie Hackers in 2026

DevToolsPicks — Fri, 05 Jun 2026 07:16:12 +0000

You already know Make.com, Zapier, and n8n exist. The question is which one to use for your specific situation.

I covered the full feature-by-feature comparison separately. This guide is different. It is organized by scenario, not by tool. Find your situation below, and you will know which one to pick.

Quick Decision Table

Your Situation	Best Pick	Why
Want the fastest setup, don't care about cost	Zapier	Largest app library, easiest interface
Need multi-step workflows on a budget	Make.com	10,000 credits for $9/mo vs Zapier's 750 tasks for $20/mo
Want full control and self-hosting	n8n	Free Community Edition, unlimited executions
Running fewer than 100 automations/month	Make.com	Free plan gives 1,000 credits (10x Zapier's free tier)
Non-technical, need it working in 10 minutes	Zapier	Nothing else onboards this fast
Complex branching workflows with loops	Make.com	Visual builder handles branching natively
Developer who wants to write custom logic	n8n	JavaScript/Python nodes, full code access

When Zapier Is the Right Call

You need the widest integration library. Zapier connects to 9,000+ app connections. Make.com covers 3,000+, and n8n has 500+. If your workflow depends on a niche app that only Zapier supports, the choice is made for you.

You want zero learning curve. Zapier's trigger-action model is the simplest of the three. Pick a trigger, pick an action, turn it on. If you are non-technical or just want something running in under 10 minutes, Zapier wins here.

You are running simple, low-volume automations. A two-step Zap that sends Stripe payments to a Google Sheet, or posts new blog entries to Slack. If your workflows are linear and you stay under 750 tasks/month, the Professional plan at $19.99/month (billed annually) is fine.

You need your team onboarded quickly. The Team plan at $69/month supports 25 users with shared workspaces and SSO. For small teams that need collaboration features without a steep learning curve, Zapier is the fastest path.

When Zapier is NOT the right call

Your workflows have more than 3-4 steps. Every action step counts as a task, so a 5-step workflow running 200 times per month burns 1,000 tasks. At that rate, you will outgrow the Professional plan within a month and face bills climbing toward $300/month or more.

When Make.com Is the Right Call

You need complex workflows without breaking the bank. Make.com gives you 10,000 credits on the Core plan for $9/month (billed annually). Zapier gives you 750 tasks for $19.99/month. The math is clear.

But there is a catch most guides skip: Make counts every module execution as one credit. A 5-module scenario running once uses 5 credits. A similar Zapier workflow might use 4 tasks (Zapier doesn't count the trigger). The real savings are roughly 3x, not the 10x the headline numbers suggest.

You want a visual workflow builder. Make's drag-and-drop canvas lets you see every connection, branch, and loop in your automation. If your workflows have conditional paths ("if payment is over $100, send to Slack AND update CRM, otherwise just log it"), Make handles this more intuitively than Zapier's path feature.

You are a solo developer automating SaaS operations. New user signs up, gets a welcome email via Resend, gets added to your CRM, triggers an onboarding drip sequence, and logs the event to your analytics. That is 5 modules per signup. At 500 signups per month, you are using 2,500 credits. Still well within Core.

You want webhooks and HTTP modules on a budget. Make includes webhooks and custom HTTP requests on every plan, including the free tier. Zapier locks webhooks behind the Professional plan.

When Make.com is NOT the right call

You need a specific app that only Zapier supports. Check Make's integration directory before committing. The gap is shrinking, but 3,000 apps is still less than half of Zapier's library.

When n8n Is the Right Call

You are a developer who wants full control. n8n is open source. You can read the code, extend it, and customize it however you want. Write JavaScript or Python directly in workflow nodes. No vendor lock-in.

You want to self-host for free. The Community Edition is completely free with unlimited executions, unlimited workflows, and access to every integration. Install it on a $5/month VPS via Docker, and your only cost is the server. For an indie hacker running 50+ workflows, this saves hundreds of dollars per year compared to Zapier or Make.

You have complex workflows where per-step billing would crush you. n8n counts one execution per workflow run, regardless of how many steps are inside. A 10-step workflow running 1,000 times per month? That is 1,000 executions on n8n, 10,000 credits on Make, and roughly 9,000 tasks on Zapier.

Over a year, those same workflows cost roughly $60 on self-hosted n8n (just server costs), $108 on Make.com Core, and $300+ on Zapier Professional.

You are already managing infrastructure. If you run your SaaS on a VPS and handle your own deployments, adding n8n to the stack is straightforward. A basic Docker install takes about 15 minutes.

When n8n is NOT the right call

You do not want to manage a server. n8n Cloud exists (starting at €20/month for 2,500 executions), but at that price point you lose the main cost advantage over Make.com. If you prefer hosted solutions and are not running extremely complex workflows, Make.com Core at $9/month gives you more value per dollar.

You also need a wider integration catalog out of the box. n8n supports 500+ apps natively, which covers the big ones but may miss niche tools. You can build custom integrations with HTTP nodes, but that takes developer time.

How Much Does Each Tool Actually Cost?

Here is a real scenario: you run 5 workflows with an average of 4 steps each, triggering 500 times per month total.

Tool	Monthly Usage	Plan Needed	Monthly Cost (Annual)
Zapier	~2,000 tasks	Professional (slider to 2,000)	~$49/mo
Make.com	~2,000 credits	Core (10,000 included)	$9/mo
n8n Cloud	500 executions	Starter (2,500 included)	€20/mo
n8n Self-hosted	500 executions	Community (unlimited)	~$5/mo (VPS only)

The gap widens as complexity increases. At 10,000 tasks/month, Zapier can hit $600/month. Make.com stays at $9/month if you are within 10,000 credits. Self-hosted n8n stays at $5/month regardless.

What About AI Features?

All three tools added AI capabilities in 2025-2026. Zapier has Copilot for building and troubleshooting Zaps. Make.com has AI Agents and an AI Toolkit that lets you connect your own API keys from OpenAI or Anthropic. n8n added native AI nodes for Claude, GPT, and Gemini, plus vector store integrations.

For indie hackers, the practical difference is small. The AI features help you build workflows faster, but they do not fundamentally change which tool fits your situation. Pick based on pricing and complexity needs first. The AI features are a nice bonus, not a deciding factor.

My Recommendation

If you are an indie hacker building a SaaS solo, start with Make.com Core at $9/month. It handles complex workflows at a price point that does not scale out of control, and the visual builder is genuinely good for mapping out multi-step business logic.

If you are a developer comfortable with Docker and VPS management, self-host n8n. The cost savings are real and compound over time, and the execution-based billing means you never get punished for building complex workflows.

Use Zapier only when you need an integration it exclusively supports, or when onboarding speed matters more than long-term cost. It is the most expensive option at scale, but nothing else gets a non-technical person from zero to working automation faster.

For the full feature breakdown with benchmarks, check the complete Zapier vs Make vs n8n comparison. If you have already decided to leave Zapier, here are the best Zapier alternatives for solo developers.

Best Linear Alternatives for Indie Hackers in 2026 (Honest Picks)

DevToolsPicks — Thu, 04 Jun 2026 03:00:33 +0000

Linear's free plan sounds generous until you hit the 250-issue limit. Most active development projects reach it within a few weeks. After that, you are looking at $10/user/month for Basic or $16/user/month for Business. For a solo founder who is also the only developer, that is a real recurring cost for a tool that is primarily for managing your own backlog.

The alternatives have matured significantly. Plane is now a genuine like-for-like replacement. GitHub Issues covers simple workflows at no cost. Jira's free tier is more capable than most developers realize.

Here is what each one actually offers.

Quick Verdict

Tool	Best For	Price	Free Tier
Plane	Open-source, self-hosted, full Linear replacement	Free / $6/seat/month	Yes (unlimited self-host)
GitHub Issues	Solo devs, code-integrated workflow	Free	Yes (always)
Jira	Teams needing enterprise-grade workflows	Free up to 10 users / $7.75/user/month	Yes (10 users)
Shortcut	Product-focused teams, cleaner than Jira	Free up to 10 users / $8.50/user/month	Yes (10 users)
Linear	Fast UI, keyboard-driven, opinionated workflow	Free (250 issues) / $10/user/month	Yes (limited)

Plane

Plane is the open-source alternative built specifically to compete with Linear. The interface is fast, the workflow is similar (issues, cycles, modules, kanban), and the Community Edition is free with no user limits and no issue caps.

Pricing:

Community Edition (self-hosted): Free forever. Unlimited users, unlimited issues. No expiry.
Cloud Free: Free tier available with core features.
Pro/Commercial: $6/seat/month. Adds time tracking, custom issue types, SSO, and advanced features.
Enterprise: Custom pricing.

What it does well: Plane self-hosted is the strongest free option for a team that wants Linear-style issue tracking without paying. The Docker Compose deployment takes under 10 minutes. Plane also includes a built-in Wiki, which replaces the need for a separate Confluence or Notion for team documentation. Cycles (sprints), modules (project groupings), and intake (feature request capture) are all present.

The cloud Pro plan at $6/seat/month is 40% cheaper than Linear Basic at $10/user/month. For a 10-person team, that is $720/year on Plane versus $1,200 on Linear for similar features.

Plane also includes GitHub, GitLab, and Slack integrations, so the workflow connects to where developers actually work.

What it does not do well: The UI is polished but not quite at Linear's level. Linear's keyboard navigation and speed are hard to match. Plane's documentation has gaps compared to Linear's, and the community is smaller if you need help with edge cases.

Who should use Plane: You want a full Linear replacement with no cost. You care about data sovereignty and want to self-host. You are price-sensitive and the $6/seat/month versus $10/seat/month difference matters to your business.

Who should NOT use Plane: You value the absolute best UI and fastest keyboard shortcuts in a project management tool. You need enterprise compliance features and want a vendor SLA.

GitHub Issues and Projects

For solo developers building a SaaS, GitHub Issues is already in the stack. Every commit, pull request, and code change lives on GitHub. Tracking the work alongside the code in the same place has a low cognitive overhead that no external tool can match.

Pricing:

GitHub Free: Unlimited public repositories, unlimited issues, unlimited private repositories with up to 3 collaborators.
GitHub Pro: $4/month for individuals. Adds advanced insights and unlimited collaborators on private repos.
GitHub Team: $4/user/month. Organization-level features.

What it does well: Zero additional tool. If you already pay for GitHub, issues cost nothing. GitHub Projects (the newer interface) supports kanban views, table views, sprint-like iterations, and automation rules that cover most solo development workflows. Issues link directly to pull requests and commits, which means your task list and your code history are connected without any integration setup.

For a solo indie hacker with a small backlog, this is genuinely sufficient. No $10/month subscription for a tool that just needs to track what you are working on.

What it does not do well: GitHub Issues lacks Linear's opinionated workflow: no cycles with velocity tracking, no triage mode, no team health metrics. For anything beyond basic issue management, GitHub Projects feels like a spreadsheet with extra steps rather than a proper project management tool.

Who should use GitHub Issues: You are a solo developer or a two-person team. You want zero additional cost and zero context switching. Your backlog is simple and does not need sophisticated sprint tracking.

Who should NOT use GitHub Issues: You have a product team with designers and non-technical members who need a proper PM tool. You need velocity tracking, estimation, or cycle burndown charts. Your workflow has more complexity than a basic kanban board handles.

Jira

Jira is the project management tool most professional developers have used at some point. The free tier is more generous than most developers realize in 2026: unlimited issues, 2GB storage, and up to 10 users at no cost.

Pricing:

Free: Up to 10 users, unlimited issues, 2GB storage, community support.
Standard: $7.75/user/month (annual). Unlimited storage, project roles, audit logs.
Premium: $15.25/user/month (annual). Advanced roadmaps, AI features, admin insights.
Enterprise: Custom pricing.

What it does well: The free plan genuinely covers most small team needs. Unlimited issues with no cap means you can run active development on the free tier indefinitely as long as your team stays under 10 people. Jira's workflow customization is the deepest of any tool in this list: custom issue types, custom workflows, automation rules, and 3,000+ integrations in the marketplace.

If your SaaS eventually needs to onboard enterprise clients, they will likely recognize and accept a Jira-integrated workflow. That compatibility has practical value when selling to larger organizations.

What it does not do well: Jira is complex by design. Setting up a project correctly, configuring workflows, and navigating the admin settings takes significantly more time than Linear or Plane. For a solo developer who wants to track their backlog quickly, Jira adds overhead. The interface is slower and more cluttered than Linear.

Who should use Jira: You are targeting enterprise clients who expect Jira-compatible workflows. Your team has more than 10 people and you need the Standard tier's admin controls. You want the deepest workflow customization available.

Who should NOT use Jira: You are a solo developer or small team who wants to move fast without configuration overhead. You find Jira's interface slow and want something closer to Linear's speed. You are not targeting enterprise clients who require Jira integration.

Shortcut

Shortcut (formerly Clubhouse) is a product management tool positioned between Linear's developer-first simplicity and Jira's enterprise complexity. It targets product teams where engineers and product managers share the same workspace.

Pricing:

Free: Up to 10 users, core features, unlimited stories.
Teams: $8.50/user/month (annual). Removes user cap, adds advanced reporting.
Business: Custom pricing for larger teams.

What it does well: Shortcut's epic structure (stories inside epics inside milestones) fits product planning workflows well. The free tier at 10 users with unlimited stories is among the most generous available. The reporting and velocity tracking on the Teams plan are stronger than Plane's at a comparable price point.

The interface is clean and loads quickly. For teams where product managers use the same tool as engineers, Shortcut avoids the developer-first skew that makes Linear harder for non-technical team members.

What it does not do well: Shortcut does not have a self-hosted option. You are fully dependent on their cloud infrastructure. The tool is also less opinionated than Linear, which means teams sometimes end up with inconsistent workflows without clear guidance on how to structure their work.

Who should use Shortcut: You are building a product with both technical and non-technical team members who need to share a project tracking tool. You want the structure of Jira without Jira's complexity. Your team is under 10 people and the free tier covers your needs.

Who should NOT use Shortcut: You want the fastest keyboard-driven workflow (Linear wins here). You need self-hosted data control (Plane is the only option). You are a solo developer who does not need product management features.

How to Choose

Solo developer managing your own SaaS: GitHub Issues free tier. No cost, already in your stack, sufficient for a solo backlog.

Small team (2-5 people) wanting a Linear replacement without the cost: Plane free cloud or self-hosted. Full workflow without the per-seat cost.

Team needing enterprise-grade features on a budget: Jira free tier if under 10 users, or Jira Standard at $7.75/user/month. The customization depth justifies the learning curve at team scale.

Product + engineering team needing a clean shared workspace: Shortcut free tier up to 10 users, then Teams at $8.50/user/month.

Staying on Linear: If the 250-issue free limit is not a constraint and the UI speed matters to you, Linear Basic at $10/user/month is still defensible. The Linear vs Jira vs ClickUp comparison covers how Linear stacks up on features and pricing in more detail.