DEV Community: DevToolsPicks

GPT-5.5 vs Claude Opus 4.7 for Indie Hackers in 2026: Which Flagship Is Actually Worth It?

DevToolsPicks — Mon, 25 May 2026 02:55:12 +0000

You are building a SaaS. You need an AI model behind it. The two flagships staring back at you are GPT-5.5 (launched April 23, 2026) and Claude Opus 4.7 (launched April 16, 2026).

Both cost real money. Both are good. And every comparison you find online reads like a benchmark leaderboard with zero mention of what it actually costs to run 1,000 API calls a day from your Laravel backend.

Here is the comparison I wish I had found when I was making this decision. Real pricing, real cost math, real trade-offs for someone shipping a product solo.

My pick: Claude Opus 4.7 for most indie hacker use cases. It is cheaper on output tokens, stronger on agentic coding tasks, and the 1M context window handles large codebases without truncation. GPT-5.5 wins on speed and ecosystem breadth, but you pay a 20% premium on every response for it.

Quick Verdict

	Claude Opus 4.7	GPT-5.5
Input price	$5 / million tokens	$5 / million tokens
Output price	$25 / million tokens	$30 / million tokens
Context window	1M tokens	1.05M tokens
Cached input	$0.50 / million tokens	$0.50 / million tokens
Batch discount	50% off	50% off
SWE-bench Verified	~93%	~89%
Best for	Code quality, long tasks	Speed, ecosystem tools
Subscription	Claude Pro $20/mo	ChatGPT Plus $20/mo

How Much Does Each Model Actually Cost for a SaaS?

Every comparison leads with benchmarks. I am going to lead with the number that actually matters: your monthly bill.

Here is a realistic indie hacker scenario. Your SaaS makes 1,000 API calls per day. Each request sends about 1,500 input tokens (a system prompt plus user query) and receives about 800 output tokens back.

Monthly cost with Claude Opus 4.7:

Input: 1,500 tokens x 1,000 calls x 30 days = 45M tokens = $225
Output: 800 tokens x 1,000 calls x 30 days = 24M tokens = $600
Total: $825/month

Monthly cost with GPT-5.5:

Input: 1,500 tokens x 1,000 calls x 30 days = 45M tokens = $225
Output: 800 tokens x 1,000 calls x 30 days = 24M tokens = $720
Total: $945/month

That is $120 per month more for GPT-5.5 at the same usage. Over a year, $1,440 extra. For a bootstrapped SaaS pulling in $3K MRR, that gap matters.

And this is before accounting for the tokenizer issue.

The Tokenizer Gotcha Nobody Talks About

Claude Opus 4.7 ships with a new tokenizer. The sticker price stayed the same as Opus 4.6, but the new tokenizer converts the same text into roughly 35% more tokens. So "same price" is misleading. Your per-request cost goes up even though the rate card did not change.

GPT-5.5 has a different trade-off. OpenAI doubled the per-token price compared to GPT-5.4 ($2.50/$15 became $5/$30), but claims the model produces roughly 40% fewer output tokens for the same task. So the effective cost increase is closer to 20%, not 100%.

Both companies are playing the same game: pricing looks flat, but the real cost shifts underneath.

For an indie hacker, the takeaway is simple. Run your actual prompts through both models and count the tokens. Do not trust the rate card alone. Your real bill depends on how many tokens each model consumes for your specific workload.

How Does Each Model Handle Coding Tasks?

This is where most indie hackers will feel the difference.

Claude Opus 4.7 leads on SWE-bench Verified with roughly 93%, compared to GPT-5.5 at about 89%. SWE-bench tests whether a model can resolve real GitHub issues in real codebases. That 4-point gap sounds small, but it translates to Opus catching more edge cases and breaking fewer things during multi-step coding sessions.

Where Opus really pulls ahead is instruction adherence on long tasks. If you give it a 15-step refactoring plan across multiple files, it tends to follow through without drifting or reinterpreting your goals halfway through. This matters when you are using Claude Code as your primary coding partner.

GPT-5.5 is faster. Noticeably faster. It also produces shorter, more concise outputs, which means fewer tokens billed per response. For tasks where speed matters more than depth, like generating API response templates or quick utility functions, GPT-5.5 feels snappier.

But GPT-5.5 has a weakness that trips up solo developers. It is more confident when it is wrong. Opus 4.7 tends to flag uncertainty ("I'm not sure about this import path, you should verify"). GPT-5.5 is more likely to just write the wrong import and move on. When you are working without a code review partner, that difference in honesty saves hours.

I covered the Claude Sonnet 4.6 vs Opus 4.7 trade-off separately if you are deciding between Claude tiers rather than across brands.

What About Subscriptions? Claude Pro vs ChatGPT Plus

Not every indie hacker needs the API. If you are using AI as a personal coding assistant (not embedded in your product), the subscription comparison matters more.

Both Claude Pro and ChatGPT Plus cost $20/month. What you get is very different.

Claude Pro ($20/month):

Access to Opus 4.7, Sonnet 4.6, and Haiku 4.5
Claude Code included (terminal-based coding agent)
Projects for persistent context
5x usage over the free tier

ChatGPT Plus ($20/month):

Access to GPT-5.5
Codex (cloud-based coding agent)
DALL-E image generation
Sora video generation
Deep Research (10 runs/month)
Agent Mode and app connectors

ChatGPT Plus gives you more tools in one subscription. Claude Pro gives you a sharper coding experience. If your day is mostly writing and debugging code, Claude Pro is the better $20. If you also need image generation, video, or research tools, ChatGPT Plus covers more ground.

For the full breakdown of subscription tiers across both platforms, I compared ChatGPT Pro $100 vs Claude Max vs Cursor in a separate post.

How to Cut Your API Bill in Half

Both Anthropic and OpenAI offer the same two cost levers, and most indie hackers ignore both of them.

Prompt caching saves up to 90% on input tokens. If your system prompt stays the same across requests (and it usually does), cached input costs $0.50 per million tokens instead of $5. For a SaaS sending the same 1,000-token system prompt on every call, that drops your input cost from $150/month to $15/month.

Batch processing saves 50% on everything. If your workload does not need real-time responses (think: nightly data processing, bulk content generation, email drafts queued overnight), batch pricing cuts both input and output rates in half.

With both levers applied to the scenario above:

	Opus 4.7 (optimized)	GPT-5.5 (optimized)
Input (cached)	~$15/mo	~$15/mo
Output (standard)	$600/mo	$720/mo
Total	~$615/mo	~$735/mo

Or with batch processing on a non-real-time workload:

	Opus 4.7 (batch)	GPT-5.5 (batch)
Input	$112.50/mo	$112.50/mo
Output	$300/mo	$360/mo
Total	~$412/mo	~$472/mo

These are savings most AI pricing guides skip because they are focused on enterprise buyers. For a solo developer watching every dollar, the difference between $945/month and $412/month is whether your SaaS stays profitable.

When Should You Pick GPT-5.5 Instead?

Opus 4.7 is my default recommendation, but GPT-5.5 wins in three specific scenarios.

You need the OpenAI ecosystem. If your SaaS already uses Codex, DALL-E, or Whisper, staying on OpenAI avoids the overhead of managing two API providers. One billing dashboard, one SDK, one set of rate limits.

Speed is your competitive advantage. GPT-5.5 returns responses noticeably faster. If your product's UX depends on sub-second AI responses (chatbots, autocomplete, real-time suggestions), the speed difference is worth the 20% output premium.

Your team is already on ChatGPT Pro. If you are paying $100-$200/month for ChatGPT Pro and using Codex daily, switching to Claude means relearning workflows and losing features like Agent Mode and Sora. The switching cost is real.

When Should You Pick Claude Opus 4.7?

Coding is your primary use case. Higher SWE-bench scores, better instruction adherence on long tasks, and Claude Code as a dedicated terminal agent. For a solo developer shipping features daily, this combination is hard to beat.

You are cost-sensitive on output tokens. The $5/MTok gap on output adds up fast at scale. If your SaaS generates long AI responses (detailed reports, code reviews, document analysis), Opus 4.7 saves you real money.

You value honesty over confidence. Opus 4.7 is more likely to say "I'm not sure" than GPT-5.5. When you are the only person reviewing AI-generated code before it ships to production, you want the model that flags its own uncertainty.

Can You Use Both?

Yes, and many indie hackers do. The practical setup looks like this:

Route complex coding tasks to Opus 4.7 (quality matters, speed does not)
Route fast customer-facing responses to GPT-5.5 (speed matters, cost is secondary)
Use OpenRouter to switch between models with a single config change

This is not overengineering. It is basic cost optimization. The same way you would not use a $50/month database for a job queue, you should not use a $25/MTok model for tasks that a $3/MTok model handles fine.

If you are considering a cheaper Claude tier instead of Opus, check whether Sonnet 4.6 at $3/$15 covers your needs. For most indie SaaS features, it does.

Final Verdict

For an indie hacker building a SaaS in 2026, Claude Opus 4.7 is the better default. It costs less on output tokens, scores higher on coding benchmarks, and the Claude Code integration gives you a complete coding workflow from one provider.

GPT-5.5 is the right choice if you are already deep in the OpenAI ecosystem, need the fastest possible response times, or rely on tools like Codex, DALL-E, and Sora that Anthropic does not offer.

The real answer for most solo founders: use Sonnet 4.6 or GPT-5.4 for 90% of your API calls, and save the flagship models for the 10% of tasks that genuinely need them. That is how you keep your AI bill under control while shipping a competitive product.

Anthropic Academy: Which Free AI Courses Are Worth Taking for Indie Hackers in 2026?

DevToolsPicks — Sun, 24 May 2026 05:45:34 +0000

Anthropic launched Anthropic Academy on March 2, 2026. Seventeen courses, all free, with official completion certificates hosted on Skilljar. No subscription required to enroll.

A community post about it spread widely this week, which is how most people found out. Anthropic did not run a marketing campaign. The community surfaced it.

Here is which courses are worth your time as an indie hacker, which to skip, and what order to take them in.

The Two Paths

Anthropic Academy splits naturally into two tracks. Which you take depends on one question: do you write code?

The Developer Path

Claude Code 101

Start here, not with the API course. Claude Code 101 covers the practical setup, core commands, and the mental model for working with Claude Code as a coding assistant rather than just a chatbot. It was added in April 2026 as a direct on-ramp for developers new to the tool.

Time: roughly 1-2 hours. Worth it before anything else.

Building with the Claude API

The most valuable course in the Academy for an indie hacker building AI-powered products. It covers authentication, request handling, response parsing, streaming, tool calling, and prompt engineering in depth. The course was co-developed with practical SaaS use cases in mind.

This is the 8+ hour investment. Take it seriously. The API course covers things that were scattered across docs and GitHub repos before the Academy existed, now structured into one place with exercises.

The course walks you through authentication (API keys, managing rate limits), request construction (messages, system prompts, tool definitions), and response handling (streaming, stop sequences, token counts). The tool calling section alone is worth the time investment for anyone building a product that routes between multiple functions or external APIs.

If you are building a product that calls Claude in any way, this course is the one that matters.

Claude Code in Action

This course covers AI-assisted coding workflows in the terminal: how to set up Claude Code, how to write effective prompts for large refactors, how to handle multi-file edits, and how to debug Claude-generated code. If you have been using Claude Code by feel, this course fills in the gaps. For the full picture on mobile Claude Code workflows, see the vibe coding from phone setup post.

Introduction to MCP

Take this course only if you are building something that integrates with Claude Code via the Model Context Protocol, specifically if you want to build your own MCP server or connect Claude to custom data sources. It is not required for most indie hackers using Claude as a coding assistant.

For those building tools on top of Claude Code, this course is where things get genuinely interesting. For context on how Anthropic has been expanding the Claude Code ecosystem, see the Claude Code agent view launch post.

Skip for Most Indie Hackers

MCP Advanced Topics: Only useful once you have shipped an MCP server and hit its limits. Start with Introduction to MCP first.

Introduction to Subagents: Worth taking if you are building multi-agent workflows where Claude delegates tasks to isolated sub-agents. If you are just using Claude Code for a solo SaaS, skip it for now.

Claude on Amazon Bedrock / Claude on Google Vertex AI: Both courses cover enterprise cloud deployment. Unless you are specifically building on AWS or GCP and need Claude integrated into that infrastructure, these are not relevant for indie hackers.

The Non-Technical Founder Path

Claude 101

Everyone should start here regardless of technical level. Claude 101 covers how to interact with Claude effectively: framing requests, using context windows well, handling document-heavy tasks, and avoiding common failure modes. It teaches you to work with the model rather than against it.

Time: 2-3 hours. Works with a free Claude account.

AI Fluency: Framework and Foundations

This course shifts the lens from tool use to strategic thinking. It covers how to evaluate where AI genuinely saves time versus where it adds overhead, and how to build AI habits that compound over weeks rather than burning out in the first month.

It was co-developed with professors from Ringling College and University College Cork and released under a Creative Commons license. The academic quality shows. Topics include how to frame tasks for AI, how to review and verify outputs, when to stop iterating on a prompt and rewrite the task entirely, and how to think about AI as a collaborator rather than an autocomplete engine.

For a non-technical founder who is not sure how to integrate AI into daily work beyond chatting, this course gives a practical framework.

Introduction to Claude Cowork

The most underrated course in the entire Academy. Claude Cowork is a desktop tool that lets non-technical founders automate file and task management workflows using Claude without writing any code. The course is short (1-2 hours) and covers practical use cases: batch document processing, automated folder organization, multi-step task pipelines.

For a solo founder who is not a developer, this is more immediately useful than anything in the developer track.

Skip for Most Non-Technical Founders

AI Fluency: Your Work, Transformed and AI Fluency: Thinking Like an Innovator are both solid but more relevant to people in larger organizations running AI adoption initiatives. For an indie hacker, Claude 101 and AI Capabilities and Limitations cover the same ground more efficiently.

Is the Certificate Worth It?

It depends on your goal. The Anthropic name carries weight in developer circles in 2026, particularly after Claude Code crossed $1B ARR. If you work with clients, pitch to investors, or do consulting, having Anthropic certifications on LinkedIn signals genuine familiarity with the toolchain.

The certificates do not unlock API credits, discounts, or early access to new features. They are credential signals, not access tokens.

One practical note: the certificates are generated on Skilljar and include your name and the course title. They are shareable as PDFs and as LinkedIn credentials. The process is automatic once you complete the course quizzes. No manual request needed.

For a solo founder building internal tools, the courses themselves matter more than the certificates. Take them for the knowledge, not the badge.

How to Enroll

Sign up at the Anthropic Academy on Skilljar. An email address is all you need. No Claude subscription required. All 17 courses are available immediately and you can start any of them without completing the others first, though the paths above give you the fastest route to practical skills. For related decisions on the Claude Code toolchain, see the best Claude Code alternatives if you are still evaluating whether Claude Code is the right fit for your workflow.

Vibe Coding Your SaaS From Your Phone: The Claude Code Mobile Setup Indie Hackers Are Using in 2026

DevToolsPicks — Sat, 23 May 2026 05:59:05 +0000

A 10-year software engineer has been shipping all his side projects from his phone using Claude Code without reading any of the code. Around the same time, Pieter Levels posted about his VPS-Tmux workflow for coding from anywhere.

This is not a gimmick. Anthropic shipped a feature called Remote Control in February 2026 that makes it genuinely practical. Here is how the mobile Claude Code setup actually works, what it costs, and where it breaks down.

Why Now

The timing of this trend is not a coincidence. Claude Code Remote Control launched on February 24, 2026. Before that, getting your phone to interact with a running Claude Code session required SSH tunnels, tmux, ngrok proxies, or fragile custom setups. None of them were fast to configure or reliable to maintain.

Remote Control changed the equation. One command, one QR code, zero port forwarding.

Approach 1: Claude Code Remote Control (Official)

This is the setup most developers using Claude Code on mobile are reaching for.

How it works: Claude Code keeps running on your laptop or desktop. Your phone becomes a remote window into that session. Code never leaves your machine. Only encrypted chat messages and tool approval prompts flow through Anthropic's relay servers.

Setup:

Make sure you are on Claude Code version 2.1.52 or later
In your terminal, run claude rc (or claude remote-control)
A QR code appears
Open the Claude app on your phone and scan it
Your phone is now connected to your local session

From your phone you can read what Claude is doing in real time, approve or reject file changes, send new instructions, and monitor multiple sessions simultaneously. The session auto-reconnects if your laptop sleeps and wakes.

The cost: Claude Max, which starts at $100/month. Remote Control is a Claude Code feature, and Claude Code requires Max. If you are on Pro ($20/month), this does not apply to you.

The workflow this enables:

The key insight is what comes next: the developer is not reviewing the code line by line. They are reading Claude's summary of what changed, approving if it sounds right, and trusting the CI pipeline to catch errors. That is a workflow choice, not a Claude Code constraint.

Approach 2: SSH + Tailscale + tmux (Phone-First)

This is closer to what Pieter Levels describes for his nomad setup. Instead of connecting your phone to a laptop session, you connect your phone to a VPS that is always running.

How it works:

Run Claude Code inside a tmux session on a VPS or cloud server
Install Tailscale on both the server and your phone for secure access
SSH into the server from your phone using Termius or Blink Shell
Reattach to the tmux session and continue from wherever you left off

The advantage: Your laptop does not need to be on. The session is always there. You can disconnect and reconnect from any device. This is true cloud-first mobile coding, not remote supervision.

The cost: A $6-10/month VPS (Hetzner CX22, DigitalOcean Droplet, Railway). Tailscale free plan covers personal use. Termius costs around $20-30/year for the iOS/Android app.

The trade-off: You are working in a raw terminal on a phone keyboard. This is genuinely uncomfortable for long writing sessions. Approving multi-file changes in a tmux pane on a 6-inch screen requires patience. Most developers use this approach for monitoring and quick interventions, not primary development.

What Actually Works and What Does Not

Works well:

Starting a long-running task on your laptop, then supervising from your phone during meetings, commutes, or lunch
Approving simple, well-described changes where Claude's summary is enough to understand the change
Monitoring test runs and build output while away from your desk
Pushing hotfixes from a coffee shop without opening a laptop

Does not work well:

Reviewing complex refactors on a small screen where the diff spans dozens of files
Writing long prompts with precise technical requirements on a touch keyboard
Debugging unfamiliar errors that require reading through stack traces
Anything requiring a proper code editor view rather than a terminal window

Who Should Actually Try This

If you have a Claude Max subscription and find yourself frequently stepping away from your desk mid-task, Remote Control is worth setting up. The QR code flow takes under two minutes and the phone supervision experience is genuinely usable.

If you want to code while genuinely away from your laptop (traveling, commuting, phone-only), the SSH plus VPS setup is the more reliable choice.

If you are on Claude Pro and not ready to upgrade to Max, the Codex mobile workflow covers a similar approach that works at a lower price point.

For the broader question of which AI coding tools work best for indie hackers building solo, the best Claude Code alternatives post covers the full comparison.

This workflow gets one thing right: the bottleneck is no longer the tool. It is your willingness to trust the output enough to approve it without reading every line. That is a separate decision from the setup.

OpenAI Codex Gets Appshots and Remote Mac Control: What Indie Hackers Need to Know

DevToolsPicks — Fri, 22 May 2026 09:19:27 +0000

OpenAI has established a weekly shipping cadence called Codex Thursday. Every Thursday they push updates to Codex. Yesterday's drop was the most significant one yet.

Three features shipped: Appshots for macOS, remote locked Mac access from iPhone, and Goal mode reaching general availability. Here is what each one actually does and whether it changes your workflow.

What Just Shipped on Codex Thursday

Appshots: Context Without Copy-Pasting

The friction point that every developer hits with AI coding tools is context. You are looking at an error in your browser. You switch to Codex. Now you have to describe the error, copy the stack trace, paste the URL, explain what you were doing. Every switch between tools bleeds context.

Appshots eliminates that friction. Press both Command keys to send the frontmost app window to Codex with a screenshot and available text, so Codex can work from context in another app without you copying, pasting, or describing it manually.

The keyboard shortcut is Command+Command (both Command keys simultaneously). Codex receives a full screenshot of the frontmost window plus any available text content. If you are looking at a browser error, a terminal output, a design file, or a GitHub PR, one keypress gives Codex everything it needs to understand the task.

You can also configure a custom hotkey in Codex preferences if Command+Command conflicts with something in your setup.

What this changes in practice: The round-trip between your working context and Codex drops from 30-60 seconds of manual explanation to a single keystroke. For developers who context-switch dozens of times per day between their editor, browser, and terminal, this compounds into real time savings.

The limitation: Appshots arrived as part of Codex app build 26.519 and is currently Mac-only. Windows and Linux developers cannot use this yet.

Remote Mac Control: Codex While Your Screen is Off

This one is genuinely new territory. Codex can now continue using desktop apps even after a Mac has been locked. You trigger and monitor this from Codex Mobile on your iPhone.

The practical scenario: you start a long Codex task before leaving your desk. Your Mac screen locks after a few minutes of inactivity. Previously, Codex would pause or lose context. Now it keeps working. You check in from your phone, review what it has done, approve the next steps, and keep moving.

OpenAI explains that Codex scopes locked use to active, trusted computer use turns and includes safeguards such as short-lived authorization, covered displays, relock on local input, and manual-unlock fallback.

The security model is careful. Short-lived authorization means the locked access window expires automatically. Covered displays means the screen stays dark while Codex works. Relock triggers when you physically interact with the machine. These are not afterthoughts.

Setup involves updating both the ChatGPT mobile app and the Codex Mac app, then pairing the two by scanning a QR code. Once paired, you get full Codex monitoring from your phone.

What this changes in practice: Long autonomous tasks no longer require your Mac to stay awake and unlocked. For indie hackers running overnight test suites, large refactors, or multi-step build processes, this removes a real constraint.

The limitation: Remote locked access is Mac-only. Support for connecting your phone to Codex on Windows is coming soon but is not available today.

Goal Mode is Now GA

Goal mode is no longer an experimental feature and is available in the Codex app, IDE extension, and CLI. With Goal mode, you can have Codex drive toward a specific objective for hours or even days.

The previous /goal command was experimental and limited. GA means it is production-ready and available everywhere: the desktop app, the IDE extensions (VS Code, JetBrains), and the CLI. The behavior is unchanged: you set a goal, Codex works until it reaches it. What changes is the reliability and the availability across all entry points.

You can check in and steer, and even pause Codex along the way. Pro tip: start side chats to understand the work that has been done so far without having to interrupt the main task.

Side chats are underrated here. You can ask "what have you done so far?" or "why did you make this decision?" in a separate thread while Goal mode keeps running in the main thread. No interruption, full visibility.

What This Means for Codex vs Claude Code

The honest assessment: these features are meaningful but Mac-specific.

If you develop on Mac, Appshots and remote locked access are genuinely useful additions that Claude Code does not have equivalents for today. The context capture workflow with Appshots is faster than anything Claude Code currently ships. The locked Mac access enables autonomous task patterns that were not previously reliable.

If you develop on Windows or Linux, nothing in this Codex Thursday update applies to you yet. Claude Code is cross-platform. Codex's best new features are not. That is a real competitive gap that matters for non-Mac developers until OpenAI ships Windows parity.

Goal mode GA affects all platforms equally and is the update most relevant to developers regardless of OS. The Codex /goal command comparison with Claude Code agents covers the autonomous task approach in detail if you want the deeper breakdown.

For the broader question of whether Codex or Claude Code is the right fit for your stack, the Codex vs Claude Code comparison and the Codex mobile launch breakdown from last week are worth reading alongside this update.

OpenAI is shipping fast. Codex Thursday gives them a predictable cadence to announce features, build community anticipation, and compete week-by-week with Anthropic's Claude Code releases. For indie hackers tracking which AI coding tool to invest in, paying attention to that cadence is worth the few minutes it takes each Thursday.

Namecheap vs Porkbun vs Cloudflare Registrar vs GoDaddy for Indie Hackers in 2026

DevToolsPicks — Fri, 22 May 2026 05:03:08 +0000

GoDaddy changed its Terms of Service in February 2026 and reclassified all 21 million customers as "Business Customers." That change stripped EU and UK consumer protections that previously applied to individual users and added mandatory arbitration clauses. Multiple independent registrar review sites now explicitly say they no longer recommend it.

This makes the domain registrar decision more clear-cut than it has ever been. Three genuinely good options remain: Cloudflare for cheapest renewal, Porkbun for the best all-round experience, and Namecheap for lowest first-year cost.

Here is the full comparison.

Quick Verdict

Registrar	.com First Year	.com Renewal	WHOIS Privacy	SSL
Cloudflare Registrar	$10.44	$10.44	Free	Free (Let's Encrypt)
Porkbun	$11.06	$11.06	Free	Free
Namecheap	$5.98	$13.98	Free	Free (Let's Encrypt)
GoDaddy	$2-5 (promo)	$21.99	Paid extra	Paid extra

The cost difference compounds fast. On a single .com domain over 10 years:

Cloudflare: $104.40
Porkbun: $110.60
Namecheap: $131.80 ($5.98 first year + $13.98 × 9 renewals)
GoDaddy: $199.92 ($2 first year + $21.99 × 9 renewals, before adding WHOIS privacy)

That is a $95 difference between Cloudflare and GoDaddy on a single domain. Multiply by 10 domains and the math becomes obvious.

Cloudflare Registrar

Cloudflare charges at cost. The wholesale price for a .com is $10.26 (Verisign) plus the $0.18 ICANN fee, totaling $10.44. Cloudflare adds exactly zero markup. That first-year price is also the renewal price, forever.

What Cloudflare does well:

Pricing transparency is unmatched. You will pay exactly $10.44 per .com per year with no surprises. The DNS infrastructure is Cloudflare's core product. Registering your domain here means your DNS resolves through the fastest, most reliable DNS network in the world. DNSSEC, CAA records, and advanced DNS record types come included without extra configuration or fees.

For developers, the Cloudflare dashboard is genuinely useful. All your DNS records, SSL certificates, page rules, and domain management sit in one place. If you are already using Cloudflare CDN or Workers, consolidating your domain here removes an integration step.

WHOIS privacy is included free on all domains.

What Cloudflare does not do well:

Cloudflare does not sell domains for new registrations on all TLDs. You have to transfer an existing domain in from another registrar. Some less common TLDs are not supported at all. The interface assumes you know what DNS records are. There is no hand-holding for beginners.

Cloudflare also requires you to use Cloudflare's nameservers. If you want to manage DNS entirely elsewhere, Cloudflare Registrar is not the right choice.

Who should use Cloudflare Registrar: You already use Cloudflare or plan to. You want the absolute lowest renewal price. You are comfortable with DNS configuration. You are in the EU and want a registrar whose services comply with consumer protection standards (Cloudflare was unaffected by the GoDaddy ToS issue).

Who should NOT use Cloudflare Registrar: You want to register a brand-new domain without transferring first. You need a registrar-agnostic DNS setup where you control nameservers independently. You are a beginner who wants a simple guided experience.

Porkbun

Porkbun is an ICANN-accredited registrar operating since 2010 with over 2 million domains under management. The name is unusual by design. The pricing is not.

At $11.06 per year for a .com, Porkbun is only $0.62 more than Cloudflare and comes with a better interface, more TLD support, and fewer dependencies. The price for new registrations equals the renewal price equals the transfer price. No promotional tricks.

What Porkbun does well:

Free SSL certificates are bundled with every domain, not just pointed to Let's Encrypt separately. WHOIS privacy is free. The dashboard is clean and navigates intuitively. For a developer registering their third or tenth domain, Porkbun does not require learning a new system. It behaves like you expect a domain registrar to behave.

TLD support is broad. Porkbun covers the major TLDs and a wide range of niche extensions including .app, .dev, .io, .ai, and hundreds more, all at competitive pricing. If you register multiple domains across different extensions, Porkbun handles them in one place without surprise pricing on the less common ones.

Customer support has a strong reputation specifically among indie hackers and developers. Unlike GoDaddy and Namecheap, Porkbun does not optimize the checkout process for upsells.

What Porkbun does not do well:

Porkbun's DNS tooling is not as powerful as Cloudflare's. If you need Cloudflare-level DDoS protection, CDN, or Workers at the registrar level, you would still need to integrate with Cloudflare separately. The Porkbun API exists and is functional, but is less mature than Cloudflare's for programmatic domain management at scale.

Who should use Porkbun: You want the simplest path to a domain at a fair price with no renewals surprises. You want one registrar for many different TLDs. You are a developer who registers a few domains per year and wants a registrar that does not fight you.

Who should NOT use Porkbun: You need enterprise-grade DNS and DDoS protection baked into the registrar. You register hundreds of domains per month programmatically and need the most mature API available.

Namecheap

Namecheap's first-year .com price of $5.98 is the lowest of the four. The renewal at $13.98 is where the comparison changes. Over time, that $8 annual increase per domain adds up compared to Cloudflare or Porkbun.

What Namecheap does well:

The $5.98 first-year price is legitimately useful if you register domains speculatively or want to park a name while validating an idea. You are not committing to a $10+ annual payment until you know whether the domain is worth keeping. If you kill the project after year one, you spent $5.98 not $11.

WHOIS privacy (WhoisGuard) is free and included on every domain. The dashboard is well-documented and beginner-friendly. Namecheap supports a wide range of TLDs and has been operating since 2000 with a long reliability track record.

The API is mature and supports programmatic domain management, which makes Namecheap the default for agencies or developers managing large domain portfolios via automation.

What Namecheap does not do well:

The renewal hike from $5.98 to $13.98 is a significant percentage increase and catches first-time buyers off guard. It is still well below GoDaddy's $21.99, but it makes Namecheap more expensive than both Cloudflare and Porkbun over a three-year horizon. DNS management is competent but slower than Cloudflare's infrastructure.

Who should use Namecheap: You register domains to test ideas and often do not renew them. You want the lowest first-year cost with a safety net of deleting non-keepers. You value a mature, well-documented dashboard with strong API access.

Who should NOT use Namecheap: You keep domains for more than two years and want predictable flat pricing. You want the absolute lowest long-term cost.

GoDaddy

GoDaddy remains the largest domain registrar in the world by market share. For indie hackers, that is no longer a reason to use it.

The February 2026 ToS change: GoDaddy updated its Terms of Service to reclassify all 21 million customers globally as "Business Customers." For individual users in the EU, UK, and other jurisdictions with strong consumer protection laws, this classification strips access to statutory consumer protections that previously applied, including the right to cancel under EU consumer regulations, mandatory dispute resolution through local courts, and specific data rights under consumer law. The ToS also added mandatory arbitration clauses that limit individual legal recourse.

Multiple independent domain registrar review sites, including DomainDetails, now explicitly state they no longer recommend GoDaddy as a result of this change.

.com renewal at $21.99: Even before the ToS issue, GoDaddy's renewal pricing was the most expensive of the four. At $21.99 per year versus Cloudflare's $10.44, you pay an $11.55 annual premium per domain. The first-year promotional pricing ($2-5) exists to acquire customers who then face the full renewal cost.

WHOIS privacy costs extra. SSL certificates for business plans cost extra. Checkout consistently presents upsells for add-ons most developers do not need.

Who should use GoDaddy: At this point, the main reason to stay is migration inertia. You have many domains already registered and the transfer cost and friction outweighs the annual savings. If that describes you, it is worth running the math on whether transferring to Cloudflare or Porkbun pays back within 12 months. For most portfolios it does.

Who should NOT use GoDaddy: Anyone registering a new domain today. The pricing is the highest of the four, the ToS change is a real concern for EU-based founders, and the alternatives are straightforwardly better.

How to Choose

Lowest long-term cost: Cloudflare Registrar at $10.44/year. No markup, no surprises.

Best all-round experience: Porkbun at $11.06/year. The slightly higher price gets you a better interface, free SSL, and no DNS lock-in.

Lowest first-year cost: Namecheap at $5.98 for year one. Good for domains you are testing. Switch to Cloudflare or Porkbun on renewal if you plan to keep them.

Avoid: GoDaddy. The renewal cost is highest, the February 2026 ToS change is a real issue for EU founders, and the alternatives are cheaper and less friction-heavy.

For a broader list of domain registrar options including bulk-buying tools and reseller programs, the Best Domain Registrars for Indie Hackers post covers more alternatives in depth.

Figma Just Launched a Design Agent: What Indie Hackers Need to Know

DevToolsPicks — Thu, 21 May 2026 04:50:40 +0000

Figma has been letting other AI tools into its canvas for months. Claude Code can read and write Figma files via MCP. Codex has the same access. Third-party plugins handle everything from layout generation to content replacement.

Yesterday, Figma shipped its own AI agent. Not a plugin. Not a third-party integration. Something built directly into the collaborative canvas that 690,000 paying teams already work in every day.

Here is what it does and whether it changes anything for solo devs building SaaS.

What Figma Design Agent actually is

The agent lives in the Figma Design sidebar. You describe what you want in natural language (generate a dashboard layout, add a modal component, restyle this section to match the dark mode variant) and the agent makes changes directly on the canvas.

A few things that make this different from a floating AI chatbox:

It respects your design system. If you have defined tokens, components, and styles in your Figma file, the agent uses them rather than generating generic placeholders. That matters for anyone who has spent time building a coherent component library.

It works in the multiplayer canvas. Multiple AI assistants can run simultaneously while your team is present. The design process stays in one place instead of bouncing between a chat interface and the canvas.

It handles the repetitive work. Generating variations of the same component at different sizes, replacing placeholder content across multiple frames, applying a style change consistently. The kind of work that eats 30 minutes of focused design time and produces nothing interesting.

The Figma agent is rolling out gradually in beta over the coming weeks. During beta, the agent will not consume credits. Once it reaches general availability, standard AI credits will apply.

Who gets access and when

The beta is available to Full seat users on Professional, Organization, and Enterprise plans. Collab and Dev seats can use the agent in drafts.

You will know you have access when you receive an email and see a prompt in your Figma Design files pointing to the new Agents item in the sidebar. If you want to move up the queue, the waitlist is at figma.com/join-waitlist, though joining does not guarantee a spot.

If you are on the free Figma plan, this does not apply yet.

Why Figma is doing this now

The competitive context is real. Canva, which now claims 220 million users globally, launched its AI 2.0 platform in March with a proprietary foundation model built for design. Adobe's Firefly holds 41 per cent business adoption. And a crop of AI-native startups, including Flora, Krea, and Dessn, are chasing the same audience of designers who want to move faster without sacrificing craft.

Figma's answer is the canvas itself. Every competitor is building AI features that work adjacent to where design happens. Figma's bet is that the most defensible AI product is one that lives where the work already lives.

More than 690,000 paying teams already use it as their collaborative workspace.

The financial position supports the push. Figma reported $333.4 million in Q1 2026 revenue, up 46% year on year. This is not a struggling company making a defensive move. It is a growing company accelerating into a market it already controls.

What changes for indie hackers specifically

If you use Figma for SaaS mockups, the Design Agent is worth trying during the free beta. Generating layout variations, applying your design tokens consistently, and speeding up the repetitive parts of product iteration are all genuinely useful.

If you use Figma mainly for static marketing page designs and then hand off to a developer (or do it yourself), the impact is more modest. The agent helps with the design side. It does not close the design-to-code gap on its own.

The more interesting question is what this means for your tool stack. If you currently use Claude Design or Lovable for front-end generation, the Figma Design Agent does not replace those tools. Lovable and Claude Design generate deployable code from scratch. Figma Design Agent generates design frames inside Figma. They operate at different layers of the stack and can coexist without conflict.

What Figma Design Agent does do is make staying on Figma more defensible. If you were considering switching to a lighter tool like Canva or a newer AI-native design tool, the native agent gives Figma a meaningful answer in the AI features category it did not have two weeks ago.

The honest take for solo builders

This is worth your attention if you are on a paid Figma plan. Join the waitlist, try it during the free beta, and form your own view. The agent is still beta with a gradual rollout. There will be rough edges.

If you are on the free Figma plan and this feature sounds useful, it is worth knowing that access requires Professional at $12/seat/month (annual). That is a real cost consideration for a bootstrapped founder.

And if you are not on Figma at all, this does not change the calculus for switching. The Design Agent is a reason to stay on Figma, not a reason to start. For a full picture of what Figma competes with for solo devs, the vibe coding tool comparison covers the build-side of the design-to-product workflow.

Gemini 3.5 Flash vs Claude Sonnet 4.6 for Indie Hackers in 2026: Which Should You Use?

DevToolsPicks — Wed, 20 May 2026 04:59:42 +0000

Google dropped Gemini 3.5 Flash this morning at Google I/O 2026. It is the strongest model the Flash line has ever shipped and, based on the benchmarks, it is a genuine threat to the mid-tier models it used to lose to by default.

That puts Claude Sonnet 4.6 directly in the crosshairs.

Sonnet 4.6 has been my go-to for coding since February. Good reasoning, honest about what it does not know, and the price-to-quality ratio is hard to argue with. Gemini 3.5 Flash is coming in 40% cheaper and is claiming to beat Gemini 3.1 Pro on agentic and coding tasks. That is worth taking seriously.

Here is what I actually found after going through both.

Quick Verdict

Model	Best For	Input Price	Output Price	Context
Gemini 3.5 Flash	Agentic workflows, high-volume tasks	$1.50/1M	$9.00/1M	1M tokens
Claude Sonnet 4.6	Code quality, interactive dev, Claude Code	$3.00/1M	$15.00/1M	1M tokens

Both models have a 1M token context window. Neither is free for API use.

Gemini 3.5 Flash

Google released Gemini 3.5 Flash on May 19, 2026, as part of Google I/O. The headline is unusual for a Flash model: it beats Gemini 3.1 Pro on most coding and agentic benchmarks while running about 4x faster and costing less than half as much.

The benchmark numbers that matter for indie hackers:

MCP Atlas: 83.6%. Leads the entire field, including Claude Opus 4.7 (79.1%) and GPT-5.5 (75.3%). This tests multi-step agentic tool use across real tasks.
Terminal-Bench 2.1: 76.2%. Coding automation in a terminal environment.
CharXiv Reasoning: 84.2%. Multimodal reasoning and chart understanding.

The pitch has changed. Flash models used to mean "cheaper if you can tolerate worse." Gemini 3.5 Flash is framed as frontier intelligence at Flash latency and price. On the agentic benchmarks, that claim holds up.

Where Gemini 3.5 Flash wins

Speed is the obvious one. Google claims roughly 4x output tokens per second versus comparable frontier models. For agents that loop through many steps, that gap compounds. If you are running background jobs or pipelines that call a model dozens of times per task, Gemini 3.5 Flash finishes faster and costs less.

Price is the other one. At $1.50/$9 per million tokens, it is meaningfully cheaper than Sonnet 4.6. For a solo dev running an agentic workflow that generates 10 million output tokens a month, that is $90 versus $150. Not enormous, but it adds up when you are bootstrapped.

The agentic tool-use score is a real differentiator. Gemini 3.5 Flash ranks #3 overall on agentic benchmarks, above Opus 4.7 and GPT-5.5 on MCP Atlas specifically. If your SaaS relies on MCP-driven agents calling multiple tools in sequence, this is the model to test first.

Where Gemini 3.5 Flash falls short

Pure reasoning tasks still go to Pro-tier models. Gemini 3.1 Pro beats Gemini 3.5 Flash on Humanity's Last Exam (44.4% vs 40.2%) and long-context retrieval at 128k tokens (84.9% vs 77.3%). If your workload involves dense document analysis or complex multi-step reasoning in a single turn, the Flash model gives up some ground.

The knowledge cutoff is January 2026, which means it does not know about things that happened in the last few months. For a coding assistant, that is usually fine. For anything requiring current events or recent library updates, worth keeping in mind.

Gemini 3.5 Flash also does not have a native coding environment equivalent to Claude Code. You access it through the Gemini API or Google AI Studio. There is no built-in terminal integration or filesystem access out of the box.

Who should use Gemini 3.5 Flash

You are running agentic pipelines with high token volume. You want the best MCP tool-use performance available. You are cost-sensitive and the 40% price difference matters for your workload. You are already using Google Cloud or Vertex AI.

Who should NOT use Gemini 3.5 Flash

You rely on Claude Code for interactive development. You need the best possible code quality on complex bugs. You want a model that has been through Anthropic's extended safety and reliability testing for production coding use.

Claude Sonnet 4.6

Sonnet 4.6 launched in February 2026 and has been Anthropic's daily driver recommendation since. Priced at $3/$15 per million tokens, it sits between Haiku 4.5 ($1/$5) and Opus 4.7 ($5/$25) in both cost and capability.

The improvements over Sonnet 4.5 that actually show up in practice:

Better context comprehension on long codebases. It reads existing code more carefully before making changes.
Reduced overengineering. Ask for a simple fix, get a simple fix.
Fewer false success claims. Earlier models would say "done" when they had not actually finished the task.

Developers preferred Sonnet 4.6 over Sonnet 4.5 about 70% of the time in Claude's own testing, and preferred it over Opus 4.5 (the previous flagship) 59% of the time.

Where Claude Sonnet 4.6 wins

Code quality on real-world tasks. On SWE-Bench Pro, Claude Opus 4.7 leads the field with 64.3%. Sonnet 4.6 does not publish a direct SWE-Bench Pro number, but it is the recommended model for Claude Code, which is built specifically for agentic coding. The Anthropic team's internal preference for Sonnet 4.6 over Opus 4.5 on coding tasks tells you a lot.

Claude Code integration. If you use Claude Code for your development workflow, Sonnet 4.6 is the model it runs on by default. The whole system is tuned around Anthropic's models. You do not get that with Gemini 3.5 Flash.

Reliability and predictability. Sonnet 4.6 has been in production for several months. Its behavior on coding tasks is well-documented and relatively stable. Gemini 3.5 Flash launched hours ago. There will be rough edges.

Prompt caching. Repeated context gets 90% cheaper. For agents that pass the same system prompt and codebase context on every call, this cuts your effective cost dramatically. Sonnet 4.6 at $3/$15 with caching enabled often ends up costing less than Gemini 3.5 Flash on real workloads.

Where Claude Sonnet 4.6 falls short

Price, full stop. $3/$15 versus $1.50/$9. No discount brings Sonnet 4.6 below Gemini 3.5 Flash on raw token cost before caching kicks in.

Speed. Sonnet 4.6 is not slow, but it is not claiming 4x output throughput either. For high-volume agentic loops where latency matters, Gemini 3.5 Flash has a real edge.

Who should use Claude Sonnet 4.6

You use Claude Code for daily development. You want the model with the longest production track record for coding tasks. Code quality matters more than cost for your use case. You are building something where false success claims or overengineering are costly mistakes.

Who should NOT use Claude Sonnet 4.6

Your workload is primarily high-volume agentic pipelines where MCP tool-use performance is what matters. You are on Google Cloud and the Vertex AI integration is important to you. Budget is tight and the 40% price difference is real money at your scale.

How to Choose

The honest answer is that these are different models for different parts of the stack.

Use Gemini 3.5 Flash when:

You are building background agents that loop many times per task
MCP tool-use performance is the primary metric you care about
You want the cheapest capable model for high-volume inference
You are on Google Cloud

Use Claude Sonnet 4.6 when:

You are doing interactive coding in Claude Code
You need reliable, well-tested production behavior
Code quality and reduced hallucination matter more than throughput
You use prompt caching heavily and the effective cost gap narrows

Many solo devs will end up using both. Gemini 3.5 Flash for the agentic backend tasks, Sonnet 4.6 for the interactive development work where the quality bar is higher. That is not a compromise. It is just routing tasks to the right tool.

One thing worth watching: Gemini 3.5 Pro is coming in June 2026. If it brings the reasoning improvements the Pro tier usually delivers, the competitive picture shifts again. For now, Gemini 3.5 Flash is the one to actually test.

For a broader look at how these models fit into your AI subscription choices, see my Claude Pro vs ChatGPT Plus comparison and the Claude Sonnet 4.6 vs Opus 4.7 breakdown if you are deciding between Anthropic tiers.

If you are mostly evaluating AI coding tools rather than raw API models, the Cursor vs GitHub Copilot vs Claude Code comparison covers the tool layer rather than the model layer.

Anthropic Launches Self-Hosted Claude Agents: What Indie Hackers Need to Know

DevToolsPicks — Wed, 20 May 2026 04:46:22 +0000

Anthropic held its Code with Claude London event on May 19, 2026, and shipped two new features for Claude Managed Agents: self-hosted sandboxes in public beta and MCP tunnels in research preview. Here is what they actually are and who needs them.

What Is Claude Managed Agents

Before getting into the new features, a quick frame: Claude Managed Agents is Anthropic's hosted infrastructure for running long, tool-heavy agentic sessions. It handles the agent loop, which includes orchestration, context management, and error recovery. Today's updates change where some of that work runs, specifically tool execution and private network access.

What Self-Hosted Sandboxes Actually Do

By default, when Claude Managed Agents runs tools (executes code, browses files, calls external services) that execution happens inside Anthropic-managed cloud containers. Self-hosted sandboxes move that tool execution layer into infrastructure you control.

Your files, code, and network egress stay inside your environment. You keep your own network policies, audit logging, and security tooling applied. You also control the compute: resource sizing, runtime image, and capacity for long builds or intensive tasks.

Supported providers at launch:

Cloudflare: microVMs and lighter isolates, good for short stateless tasks
Modal: GPU-ready sandboxes, suited for compute-heavy agentic work
Vercel: low-latency VM sandboxes with tight network injection
Daytona: long-lived VMs, better for sessions that run over time
Your own infrastructure: bring any container environment you control

This is where the important caveat lives: the agent loop itself does not move. Orchestration, context management, and error handling still run on Anthropic's servers. Orchestration metadata still flows through Anthropic even when tool execution stays local. Self-hosted sandboxes are not fully on-premise deployment. If your compliance requirement is that nothing touches external infrastructure at all, this does not fully solve that problem yet.

Two additional limitations to know upfront: self-hosted sandboxes are not yet available on the Claude Platform on AWS, and Memory is not yet supported in self-hosted sessions.

What MCP Tunnels Do

MCP tunnels solve a different but related problem. If you have MCP servers running inside your private network (a private database, an internal API, a knowledge base, a ticketing system) and you want Claude agents to call those servers as tools, the standard approach requires making those servers publicly accessible. Most companies do not want that.

MCP tunnels create a secure path without public exposure. A lightweight gateway runs in your environment and opens a single outbound connection to Anthropic's routing infrastructure. No inbound firewall rules. No public endpoints. Traffic is encrypted end to end. Claude reaches your private MCP server through that tunnel.

The setup is managed through workspace settings in the Claude Console by organization admins. MCP tunnels work with both Claude Managed Agents and the Messages API, so they are not limited to the agentic product.

MCP tunnels are in research preview, not public beta. You need to request access to try them. The documentation uses explicit "as-is" language, so treat it as an early program rather than a production-ready feature.

What This Means for Indie Hackers

For most indie hackers building early-stage SaaS products, neither feature is immediately necessary.

Self-hosted sandboxes become relevant when you start winning enterprise clients who have security review processes, when you handle regulated data that cannot leave a network boundary, or when you build for industries like healthcare, finance, or government where compliance frameworks restrict where code executes.

MCP tunnels are more immediately useful for developers at any stage who want to connect Claude agents to a private development database or internal API without a public endpoint. If you have been avoiding connecting Claude to internal services because of the exposure requirement, MCP tunnels change that calculus.

The practical question to ask: does your product handle data that needs to stay in a specific network boundary, or do you need Claude to reach services you cannot make public? If yes to either, read through the documentation on platform.claude.com. If no, Anthropic-managed execution remains the simpler path.

For context on how this fits with the broader changes Anthropic has been making to how Claude subscriptions and agent usage are billed, we covered the June 15 subscription split and the earlier Claude Platform on AWS launch. The self-hosted sandboxes are part of the same enterprise build-out.

The Honest Take

This is a genuine step toward enterprise readiness for Claude agents. Moving tool execution into a customer's own infrastructure is a meaningful architectural decision that addresses real compliance blockers that have been stopping some companies from adopting Claude agents at all.

The honest limitation is that the agent loop stays on Anthropic. For the strictest compliance requirements, that matters. For most enterprise use cases, tool execution in your perimeter is enough to clear procurement and security review.

For solo founders at early stage, this is worth bookmarking rather than acting on today. If you are building something that will eventually need to pass a security review or handle regulated data, the fact that this option now exists matters for your roadmap. If you are currently using Claude Code or other alternatives and debating the Claude ecosystem, this strengthens the case for building on Claude's platform long-term.

Cursor Composer 2.5 Just Launched: What Indie Hackers Actually Need to Know

DevToolsPicks — Tue, 19 May 2026 05:44:42 +0000

Cursor shipped Composer 2.5 on May 18, 2026. Here is what actually matters beyond the hype.

What Composer 2.5 Is

Composer 2.5 is Cursor's in-house AI coding model, an agent designed to drive long, tool-heavy sessions inside the Cursor editor and CLI. It reads files, runs terminal commands, edits across multiple files, executes tests, and iterates. This is not a general chat model. It was built and benchmarked specifically for software engineering tasks.

The base checkpoint is the same as Composer 2: Moonshot AI's open-source Kimi K2.5. Cursor was transparent about this from the start, having faced community criticism in March 2026 when Composer 2's Kimi base was discovered without being clearly disclosed. This time, Cursor named it in the opening paragraph of the announcement.

What changed is the training. 85% of the total compute budget went to Cursor's own reinforcement learning pipeline and post-training work. That included 25x more synthetic coding tasks, targeted RL with textual feedback at the specific trajectory steps where the model was failing, and deliberate reward-hacking research to improve robustness on long unattended sessions.

What the Benchmarks Actually Show

The numbers from the official announcement, with the important caveat that Cursor notes: Opus 4.7 and GPT-5.5 use self-reported scores for public evaluations.

SWE-Bench Multilingual: Composer 2.5 at 79.8%. Opus 4.7 at 80.5%. GPT-5.5 at 77.8%. Composer 2.5 beats GPT-5.5 and is within 0.7 points of Opus 4.7 on this benchmark.

Terminal-Bench 2.0: Composer 2.5 at 69.3%. GPT-5.5 at 82.7%. Opus 4.7 at 69.4%. GPT-5.5 leads by 13 points. This is the benchmark where the model falls short, and Cursor's own documentation flags it: if your workflow is heavily shell-driven, GPT-5.5 still has a measurable advantage.

CursorBench v3.1 (harder tasks): Composer 2.5 at 63.2%. Opus 4.7 at 64.8% max. GPT-5.5 at 64.3%. Essentially on par with both frontier models.

The honest read: Composer 2.5 is frontier-competitive on agentic coding tasks at a price point well below frontier. It is not definitively better than Opus 4.7 across the board, but it is close enough that the cost difference changes the math.

The Pricing Is the Real Story

This is where indie hackers should pay attention.

Composer 2.5 standard tier: $0.50 per million input tokens, $2.50 per million output tokens. Fast tier (the default for interactive use): $3.00 input, $15.00 output.

For comparison: Claude Sonnet 4.6 costs $3/$15 per MTok. Claude Opus 4.7 costs $5/$25. GPT-5.5 costs $5/$30. Composer 2.5 standard is one-tenth the cost of Opus 4.7 per token.

For an indie hacker running a long Claude Code session on a complex refactor, the token bill on Opus 4.7 through the API can hit $20-50 per session. The same session through Composer 2.5 standard would cost $2-5. For subscription Cursor users, this runs against included usage. The economics matter when you hit limits and overflow to per-token billing.

Cursor is also doubling included usage of Composer 2.5 for the first week after launch, through approximately May 25, 2026.

The SpaceXAI Announcement Is About a Future Model

A lot of the Twitter thread energy was around the SpaceXAI partnership. To be clear: that is not Composer 2.5. Cursor announced they are training a significantly larger model from scratch with xAI, using Colossus 2's million H100-equivalents and 10x more total compute. No release date. This is an announcement of intent for a future product.

Composer 2.5 is the model that ships today. The SpaceXAI model is what comes later.

What This Means for Indie Hackers Using Cursor

If you are already on Cursor, switch to Composer 2.5 as your default agent model and test it on your actual codebase this week. The double usage promotion means this week is the right time to run heavy sessions and form a real opinion before committing.

The practical workflow most developers are settling on: Composer 2.5 as the default for routine feature development, file editing, and test runs. Opus 4.7 or GPT-5.5 routed in for complex architectural decisions or terminal-heavy tasks where the benchmark gap is more relevant.

One caveat worth noting before you rely on it for production workflows: Cursor explicitly flagged increasingly creative reward-hacking behaviors observed during Composer 2.5 training. In practice, this means the model may occasionally find unexpected shortcuts on long unattended runs. Monitor agent traces on anything critical before trusting it fully.

If you want the broader context on how Cursor's model fits in the current AI coding tool space, we covered Cursor vs Windsurf vs Zed for indie hackers and the full three-way comparison of Cursor vs GitHub Copilot vs Claude Code. The Composer 2.5 launch makes Cursor's cost position considerably stronger against both Copilot and Claude Code for subscription users who overflow to per-token billing. We also covered the Cursor 3 agents window launch earlier this year.

The Honest Take

Composer 2.5 is a real upgrade. Frontier-competitive benchmarks at one-tenth the API cost is a genuinely useful development for developers who run heavy agentic sessions. The Terminal-Bench gap versus GPT-5.5 is real and worth knowing. The Kimi K2.5 base from Beijing is still a factor for anyone in regulated industries or with federal-adjacent work.

For most indie hackers building SaaS products in the open: try it this week during the double usage promo, run it against your real codebase, and make the call based on your own output quality. That is more useful than any benchmark table.

Claude Pro vs ChatGPT Plus for Indie Hackers in 2026: Honest $20/Month Comparison

DevToolsPicks — Tue, 19 May 2026 05:17:59 +0000

Both cost $20 a month. After that, they are very different products aimed at different kinds of work.

Here is the honest breakdown.

Quick Verdict

	Claude Pro	ChatGPT Plus
Price	$20/month ($17/month annually)	$20/month (no annual option)
Default model	Sonnet 4.6	GPT-5.5
Context window	200K tokens	~256K tokens
Claude Code CLI	Yes, included	No
Coding benchmark (SWE-Bench)	Opus 4.7: 64.3%	GPT-5.5: 58.6%
Image generation	No	Yes (DALL-E + Images 2.0)
Voice mode	No	Yes (Advanced Voice)
Video generation	No	Yes (Sora, limited)
Deep Research	No	Yes (10 runs/month)
Annual billing	Yes	No
Best for	Coding-first indie hackers	Multimodal creative work

What Claude Pro Actually Gives You at $20 a Month

Claude Pro's headline inclusion for developers is Claude Code CLI. This is the terminal-based coding agent that can read entire codebases, plan multi-file changes, run tests, and iterate autonomously. It is included in the $20/month Pro plan, not gated behind a higher tier. For an indie hacker who wants to use Claude as a full development partner rather than a chat assistant, this is the most important line in the comparison.

The default model on Pro is Sonnet 4.6. You also get access to Opus 4.7, though rate-limited. On the Sonnet 4.6 vs Opus 4.7 breakdown we published recently, the honest finding is that Sonnet 4.6 handles most routine coding tasks on par with Opus. You are unlikely to feel the Opus absence on standard feature development.

Context window is 200K tokens. Projects are unlimited. Google Workspace integration (Docs, Gmail) is included. Cowork, Anthropic's agentic feature for multi-step autonomous tasks, is included.

What is missing is striking once you see the ChatGPT Plus list. No image generation, no voice mode, no video, no Deep Research equivalent. Claude is a text and code tool. It does not try to be a creative media suite.

The usage model runs on a 5-hour rolling window. Token consumption resets on that cycle, which means back-to-back heavy Claude Code sessions can deplete limits mid-session. It is worth running a week on Pro before committing to confirm the limits are comfortable for your actual workflow.

One critical flag for June: starting June 15, Anthropic is separating programmatic and agentic API usage into a separate credit pool billed at full API rates. If you run automated pipelines or third-party tools that connect to Claude, that usage will no longer draw from your subscription. We covered the full breakdown in the Anthropic subscription split post. Claude Code usage through the subscription plan itself is unaffected, but the change matters if you use Claude via the API on top of your subscription.

Pricing: $20/month. $17/month equivalent on annual billing ($200/year billed upfront). No mid-tier option between $20 and $100.

What ChatGPT Plus Actually Gives You at $20 a Month

ChatGPT Plus is genuinely multimodal in a way Claude is not. The default model is GPT-5.5, launched April 23, 2026. Image generation through DALL-E and the new ChatGPT Images 2.0 is included, with Thinking Mode (which adds reasoning and character consistency across image sets) available at Plus level. Sora video generation is included in limited form. Advanced Voice Mode gives you real conversational back-and-forth without a keyboard.

Deep Research is included at 10 runs per month. Each run does extended web research and synthesis on a topic, similar to hiring an analyst for a few hours on a question. For market research, competitive analysis, or technical due diligence before building a feature, 10 runs per month is genuinely useful.

Custom GPTs let you build specialized assistants with your own instructions, knowledge files, and tool integrations. Memory keeps context across conversations. The combination of these two features means ChatGPT Plus can gradually become tuned to your workflow and product context in a way Claude Pro does not replicate at this tier.

The context window on Plus is roughly 256K tokens, which covers most practical workloads. Not quite at Claude's 200K level, though the difference between 200K and 256K is rarely perceptible in daily use.

What is missing is Claude Code's terminal depth. ChatGPT Plus includes Codex, which is capable, but it is a different kind of tool and a different workflow. If you have built around Claude Code's approach (running the CLI, loading directories, committing changes) switching to Codex is not a drop-in swap.

One pricing note worth knowing: OpenAI does not offer annual billing for Plus. Claude Pro at $200/year works out to $16.67/month, saving $40 per year. Over two years that is $80. Small but worth noting if budget efficiency matters.

Pricing: $20/month. No annual option. No discount. Has held at $20/month since February 2023.

Head-to-Head: Where Each Plan Wins

Coding and development

Claude Pro wins here for most indie hackers. Claude Code CLI included at $20/month is genuinely one of the best values in AI tooling in 2026. The SWE-Bench benchmark gap (64.3% for Opus 4.7 versus 58.6% for GPT-5.5) is meaningful on complex refactors and multi-file reasoning tasks. On simple feature additions and bug fixes, both are close.

The more important difference is workflow. Claude Code runs in your terminal. You point it at a directory and it reads the actual files. It can run tests, check the output, iterate, and commit changes to Git. The entire coding loop happens without leaving your terminal. For a backend developer working on a Laravel or Node.js project, this means Claude Code understands the real structure of your codebase, not a description of it.

Codex on ChatGPT Plus works differently. It runs in a sandboxed cloud environment, not directly on your files. You push tasks to it and it works on them in parallel, which is powerful for certain workflows, but the integration with your local development environment requires more setup. Codex is excellent for greenfield features and isolated tasks. Claude Code is better when you want an agent that understands your existing codebase deeply and makes changes directly.

If you primarily want an AI pair programmer that understands your full codebase and can make coordinated changes autonomously, Claude Pro is the right pick.

Writing and long documents

Claude Pro has an edge on long-form writing quality. The model follows complex instructions carefully, handles nuanced tone requirements well, and maintains consistency across long documents. The 200K context window means it can hold an entire manuscript or technical document in context.

ChatGPT Plus is also strong at writing, especially with the Deep Research feature filling in factual gaps. For short to mid-length content, the quality gap is small.

Images, voice, and video

ChatGPT Plus wins decisively. Claude Pro has nothing in this space. If any part of your work involves generating images, creating short videos, or using voice-based interaction, ChatGPT Plus is the only option between the two.

For indie hackers building tools that require visual assets, marketing materials, or content with media, this matters a lot.

Projects vs Memory

Both plans offer ways to maintain context across sessions, but they work differently.

Claude Pro includes Projects. A Project is a container where you set custom instructions and share documents, and every conversation inside that project has access to that context. For an indie hacker working on a specific product, you create a project with your tech stack, your coding conventions, and your product description, and every coding session starts with that background already loaded. Projects are organized and deliberate.

ChatGPT Plus includes Memory. Memory is automatic and cross-conversation. As you use ChatGPT, it builds up facts about you and your work that persist across all conversations. You can view and edit what it remembers. The advantage is seamlessness: you do not need to set up a project, the context just accumulates. The trade-off is less control over what is remembered and less ability to scope context to a specific project versus another.

For indie hackers working on multiple products simultaneously, Claude's Projects approach is cleaner. For people who want a single assistant that gradually learns their style and preferences, ChatGPT's Memory is more convenient.

Research and information synthesis

ChatGPT Plus wins on Deep Research. Ten extended research runs per month is a real feature for anyone who regularly needs comprehensive literature reviews, market analyses, or technical summaries. Claude Pro has no equivalent.

For quick one-off searches and summaries, both handle web search similarly. The Deep Research advantage shows on tasks that need multi-source synthesis over an extended session.

API and programmatic use

Neither subscription includes API credits. Both charge separately for API usage. If you are building products that call Claude or GPT programmatically, your subscription plan does not affect that billing at all.

The API pricing comparison matters if you are building on top of either model. Sonnet 4.6 costs $3 per million input tokens and $15 per million output tokens. Opus 4.7 costs $5 input and $25 output. GPT-5.5 costs $5 input and $30 output, making it more expensive on output than Opus 4.7.

For a product making 500,000 API calls per month with an average 1,000 input tokens and 500 output tokens each: Sonnet 4.6 runs roughly $5,250 per month. GPT-5.5 runs roughly $10,000 per month. If your product can use Sonnet 4.6 instead of GPT-5.5, the savings are significant at any meaningful scale.

The one nuance: the June 15 Anthropic change means third-party tools using Claude will no longer draw from your subscription. The ChatGPT API is unaffected by any similar change.

Which Plan Is Right for You

You code every day and want the best terminal-based coding agent at $20: Claude Pro. Claude Code CLI is the reason. Annual billing makes it $17/month.

You need image generation, voice, or video as part of your workflow: ChatGPT Plus. Claude Pro offers none of these.

You do research-heavy work and need Deep Research: ChatGPT Plus. Ten runs per month of extended research synthesis is a real feature.

You write long-form content or process large documents: Slight edge to Claude Pro for context handling and instruction following quality.

You use both already and are cutting to one: run the trial on whichever plan you use less. Both have genuine strengths and the $20 price point means the cost of being wrong is low.

If you want the comparison for the $100/month tier, where ChatGPT Pro and Claude Max compete directly, we covered that in the ChatGPT Pro $100 vs Claude Max vs Cursor breakdown.

The honest summary: Claude Pro is an exceptional developer tool. ChatGPT Plus is an exceptional multimodal creative tool. They overlap meaningfully but are aimed at different kinds of work.

Best Webflow Alternatives for Indie Hackers in 2026

DevToolsPicks — Mon, 18 May 2026 11:56:36 +0000

Webflow updated its pricing on May 13, 2026. The CMS and Business Site plans were merged into a new Premium plan at $25 per month annually. The Basic plan increased from $14 to $15 per month. A new Team plan launched at $2,500 per month for larger organizations.

For most indie hackers, Webflow was already on the expensive side for what they actually needed. The May 2026 changes gave a good reason to compare alternatives properly.

Here are five honest picks across different use cases and budgets.

Quick Verdict

Tool	Best For	Price	Closest to Webflow?
Framer	SaaS landing pages, modern design	From $10/month	Yes
Carrd	Simple one-page sites	$19/year	Partial
Ghost	Content + newsletter + memberships	From $15/month	No
Squarespace	Polished sites without complexity	From $16/month	Partial
WordPress	Maximum flexibility, lowest cost	~$5-10/month hosting	No

Is Framer the Right Switch From Webflow?

Framer is where most indie hackers and SaaS founders land after leaving Webflow. It is designed for building visually polished landing pages quickly, the AI-assisted layout tools work well for standard SaaS page structures, and the pricing is significantly lower than Webflow for a solo project.

The Basic plan at $10 per month annually gives you a custom domain, up to 30 pages, and 1 CMS collection. That covers the vast majority of SaaS landing pages. The Pro plan at $30 per month expands to 150 pages and 10 CMS collections, adds staging, and unlocks advanced analytics.

One honest limitation: Framer's CMS is less powerful than Webflow's for genuinely content-heavy sites with complex data structures. If you were using Webflow's CMS for a blog with 100 posts and multiple content types, Framer Pro handles it but you will notice the ceiling.

For the Webflow versus Framer versus Carrd head-to-head on features, we have a full comparison of all three if you want the detailed breakdown.

Who should use Framer: Indie hackers building SaaS landing pages, developers who want a design tool that does not require a front-end developer, and anyone who wants a clean modern site fast.

Who should not use Framer: Teams that need deep CMS capabilities or complex multi-site management at the agency level. Also: the Scale plan at $100 per month can sneak up on high-traffic sites.

Pricing: Free (Framer subdomain, Framer branding). Basic $10/month annually. Pro $30/month annually. Scale $100/month annually.

Is Carrd Still Worth It for Indie Hackers?

Carrd is the simplest and cheapest website builder that will have you live in under an hour. Pro Standard at $19 per year, which works out to $1.58 per month, is the plan most people need. It gives you custom domains, forms, analytics, and access to all premium templates.

The constraint is obvious: Carrd is strictly one-page. There is no blog, no multi-page navigation, and no CMS for dynamic content. Within that constraint it is exceptional. A clean SaaS pre-launch page, a personal profile, a link-in-bio page, an upcoming product announcement. All of these work perfectly on Carrd.

When to consider Carrd: you are launching a product in the next few weeks and need a clean page with an email capture form. You want the lowest possible annual cost with zero maintenance overhead. You are not planning to add a blog or multiple pages.

Who should use Carrd: Solo founders at the pre-launch stage, developers who need a personal site or product page without ongoing content, anyone who wants the lowest possible cost and fastest setup.

Who should not use Carrd: Anyone who needs a blog, multiple pages, or a CMS. Carrd is not designed for these and will frustrate you within a month if you try.

Pricing: Free (3 sites, .carrd.co subdomain). Pro Lite $9/year. Pro Standard $19/year. Pro Plus $49/year.

Is Ghost the Right Alternative if You Write?

Ghost is purpose-built for publishing. It handles blog content, email newsletters, and paid memberships in one platform, with 0% transaction fees on subscriptions beyond Stripe's standard processing fees.

The Starter plan at $15 per month gives you a clean managed hosting setup for up to 1,000 members. The Publisher plan at $29 per month adds paid subscription capability and three staff seats. Both plans include unlimited email delivery, SSL, CDN, and automatic backups, which is a better value than assembling those pieces separately.

If you are a developer and want to go further, Ghost is open source. Self-hosting on a $6 per month VPS like DigitalOcean, which has a one-click Ghost installer, keeps your total monthly cost under $15 including the domain. The trade-off is maintenance time.

Ghost is not a Webflow replacement in the design sense. The templates are polished but limited in creative control compared to Webflow. If visual design flexibility matters more than publishing workflow, Ghost is not the right call.

Who should use Ghost: Developers who write regularly and want a newsletter or paid membership layer. Indie hackers building a content-first audience. Anyone who wants to own their publishing infrastructure without platform fees.

Who should not use Ghost: Developers who need a fully custom SaaS landing page with complex design. Ghost templates are good but not flexible enough for highly custom marketing sites.

Pricing: Self-hosted free (hosting ~$6-12/month separately). Starter $15/month annually. Publisher $29/month annually.

Is Squarespace Worth Considering?

Squarespace is the most polished out-of-the-box website builder. The templates are genuinely beautiful, the editor is simpler than Webflow, and the Basic plan at $16 per month annually covers most use cases for a clean marketing site.

The trade-off is the opposite of Webflow: where Webflow gives you total design control, Squarespace limits customization to keep things accessible. If you want a pixel-perfect landing page, Squarespace will eventually frustrate you. If you want a clean, professional site up in a day without design decisions, Squarespace delivers.

For indie hackers building service businesses, consulting sites, or product landing pages where design control matters less than polish, Squarespace is a sensible pick. For SaaS builders who want full creative control over their landing page, it is too restrictive.

Who should use Squarespace: Service business owners, consultants, and anyone who wants a polished site without spending time on design. Also good for non-technical co-founders who need to maintain the site themselves.

Who should not use Squarespace: Developers who want to customise deeply, or anyone building a content-heavy site with complex CMS needs.

Pricing: Basic $16/month annually. Core $23/month annually. Plus $39/month annually. Advanced $99/month annually.

Is Self-Hosted WordPress Still Relevant?

For developers comfortable with server management, self-hosted WordPress remains the lowest-cost, highest-flexibility option in 2026.

A $5 to $10 per month VPS from Hetzner or DigitalOcean, a lightweight theme like Kadence or Blocksy, and a basic set of plugins gives you a fully functional marketing site and blog for under $15 per month total. No platform fees, no CMS limits, no bandwidth constraints.

The cost is maintenance. WordPress updates need applying, security needs monitoring, and plugin compatibility can break things at inconvenient times. For a developer building a product, this maintenance overhead is real and ongoing.

The sweet spot for self-hosted WordPress in 2026 is a developer who wants a content-heavy site with maximum flexibility and is comfortable handling server administration as part of their workflow.

Who should use WordPress: Developers who want maximum flexibility and lowest long-term cost. Also anyone with existing WordPress experience who does not want to learn a new platform.

Who should not use WordPress: Developers who want zero maintenance overhead. The hourly cost of keeping WordPress healthy is real, and for a solo founder, that time is often better spent on the product.

Pricing: Software free. Hosting $5-10/month (Hetzner, DigitalOcean, Cloudflare Pages).

How to Choose

If you are a solo developer building a SaaS product and just need a clean landing page: Framer at $10/month. Fastest to design, looks great out of the box, cheapest paid tier.

If you are pre-launch and want the absolute cheapest option for a one-page site: Carrd at $19/year. Nothing else comes close on price for what it does.

If you write regularly and want to build an audience with a newsletter: Ghost. The self-hosted option at under $15/month total is compelling if you are comfortable with a VPS.

If you want a polished site with minimal design effort and no dev background needed: Squarespace at $16/month. Templates are excellent, editor is simple.

If you want full control and do not mind maintenance: Self-hosted WordPress. Cheapest long-term, most flexible, highest maintenance.

None of these are bad choices. The right one depends on whether you are optimising for design flexibility, cost, content features, or maintenance simplicity.

Claude Sonnet 4.6 vs Opus 4.7 for Indie Hackers in 2026: Which Model Is Worth It?

DevToolsPicks — Mon, 18 May 2026 04:18:06 +0000

The question developers have been asking since Opus 4.7 launched: is it actually worth the price jump?

Pieter Levels pays $200 a month for Claude Max 20x and still ran into slowdowns loud enough to go viral last week. That is the context for this comparison. Opus 4.7 is the most capable model Anthropic ships publicly, but capable does not automatically mean worth it for solo developers building SaaS products on nights and weekends.

Here is the honest breakdown.

Quick Verdict

	Claude Sonnet 4.6	Claude Opus 4.7
Best for	Daily coding, writing, research	Complex architecture, deep reasoning
Plan required	Pro ($20/month)	Max 5x ($100) or Max 20x ($200)
API cost (input)	$3 per MTok	$5 per MTok
API cost (output)	$15 per MTok	$25 per MTok
Speed	Faster	Slower
Routine task quality	Excellent	No clear advantage over Sonnet
Complex reasoning	Good	Better
My pick	Most indie hackers	Heavy Claude Code power users

What Is Claude Sonnet 4.6?

Sonnet 4.6 is Anthropic's mid-tier model and the default choice for most Claude users. It sits between Haiku (fast and cheap) and Opus (most capable and expensive). In practice, it handles the overwhelming majority of tasks indie hackers throw at it: writing and refactoring code, debugging, drafting copy, summarising documents, answering technical questions, and running longer agentic workflows.

The 1 million token context window is available at standard pricing through the API, which matters for Claude Code sessions that load large codebases. Speed is faster than Opus, which compounds over a full day of work. You feel the difference in iteration pace.

Who Sonnet 4.6 is for: Solo developers building SaaS products, side-project founders, anyone using Claude for general coding and writing tasks, and developers who want a predictable $20/month bill.

Who should not use Sonnet 4.6 as their primary model: Developers running all-day Claude Code sessions with heavy Opus usage, anyone doing complex architectural design across large codebases where reasoning depth visibly matters, and teams that have already validated Opus delivers better output for their specific workflow.

Pricing: Claude Pro at $20/month gives you Sonnet 4.6 as the primary model with roughly 40 to 80 hours of Sonnet use per week. The API charges $3 per million input tokens and $15 per million output tokens.

What Is Claude Opus 4.7?

Opus 4.7 is Anthropic's public flagship model. It brings higher reasoning depth, 3x vision resolution compared to Sonnet, an xhigh effort mode for maximum thinking depth, task budgets for long agentic runs, and priority queue access during peak hours. Those last two matter if you have been hitting slowdowns during weekday working hours.

The honest positioning from Anthropic: Opus is for tasks where the quality ceiling of Sonnet is not enough. Complex multi-step software architecture, novel reasoning problems, tasks where you need the model to genuinely think rather than pattern-match.

Who Opus 4.7 is for: Full-time developers using Claude Code as their primary IDE for 6 to 8 hours daily, developers working on genuinely complex architectural problems, and anyone who has measurably validated that Opus output quality justifies the cost for their specific workflow.

Who should not use Opus 4.7: Indie hackers doing standard feature development, bug fixing, and writing tasks. Developers who have not hit the ceiling of Sonnet 4.6. Anyone on a tight budget who has not done the math on whether the quality delta is worth $80 to $180 more per month.

Pricing: Meaningful Opus access requires Claude Max 5x at $100/month (roughly 15 to 35 hours of Opus use weekly) or Max 20x at $200/month (roughly 24 to 40 hours weekly). On Pro at $20/month, Opus access is available but so rate-limited that most users default to Sonnet anyway. Via API: $5 per million input tokens, $25 per million output tokens.

Head-to-Head: What Actually Matters for Indie Hackers

Is the quality difference real?

For complex reasoning tasks, yes. Ask both models to design a system architecture from scratch, reason through a tricky edge case, or work through a genuinely novel problem and Opus 4.7 shows its depth.

For routine coding tasks, the difference is smaller than the price gap suggests. Our own regression analysis found Opus 4.7 performing no better than Sonnet 4.6, and sometimes worse, on standard coding tasks. The community one month post-launch has reached similar conclusions. Routine bug fixes, feature additions, refactors, and boilerplate generation are tasks where Sonnet holds up fine.

The honest read: Opus 4.7 is better at the top of the capability range. But most indie hacker work does not live at the top of the capability range.

Speed and interruption cost

Sonnet 4.6 is faster. Over a full coding session, that compounds. The time spent waiting for Opus responses adds up.

Opus 4.7 also comes with higher exposure to slowdowns during peak hours. The @levelsio situation, paying $200/month for Max 20x and still seeing minute-plus waits, illustrates the ceiling on what a subscription buys you when infrastructure is under load. Sonnet 4.6 is not immune to slowdowns, but it processes at a lower cost per token, which means Anthropic's systems are less constrained on it.

API economics for builders

If you are building a product that calls Claude via API rather than using the subscription, the pricing gap matters directly.

Sonnet 4.6 at $3/$15 per MTok. Opus 4.7 at $5/$25 per MTok. For a product making one million API calls per month with an average of 1,000 input tokens and 500 output tokens each: Sonnet costs roughly $10,500/month. Opus costs roughly $17,500/month. That is a $7,000/month difference before any discounts.

Prompt caching changes the math significantly. Cached input reads cost 10% of standard, meaning repeated context like system prompts and project files costs almost nothing after the first call. Both models benefit equally from caching, so the relative difference stays the same but the absolute numbers drop substantially.

For most indie hackers building products, Sonnet 4.6 is the right API default. Route to Opus only when you have validated that specific task types produce meaningfully better output.

The June 2026 agentic billing change

Starting June 15, programmatic usage through the Agent SDK, automated pipelines, and third-party tools moves to a separate credit pool billed at full API rates. This affects both models but hits Opus users harder because the per-token cost is higher.

If you run overnight agentic workflows, Sonnet 4.6 becomes an even more practical default. The quality difference on autonomous tasks rarely justifies the cost premium when the model is executing autonomously rather than reasoning in a conversation. We covered the full implications of the June 15 changes in our Anthropic subscription split breakdown.

The Regression Problem

This is the part most comparison posts skip.

When Opus 4.7 launched, our independent review found it performing worse than Sonnet 4.6 on routine tasks. We called it a regression. The New Stack cited the same analysis under the term "AI shrinkflation." The theory: Opus 4.7 may be running at lower precision than Opus 4.6 ran at launch, meaning you are paying the Opus premium for a model that is not delivering full Opus output on standard tasks.

A month post-launch, developer community consensus broadly agrees. Opus 4.7 is the right choice for tasks at the top of the capability range, but it does not reliably outperform Sonnet 4.6 on the everyday tasks that make up most of a solo dev's workload.

You can read our full regression analysis at Claude Opus 4.7 Is a Regression if you want the details before making a plan upgrade decision.

My Pick by Situation

Building a SaaS side project on nights and weekends: Sonnet 4.6 on Pro at $20/month. You will not hit the ceiling. The $80 you save goes toward your actual product.

Using Claude Code as your daily driver, coding 4 to 6 hours a day, hitting rate limits every week: Sonnet 4.6 on Max 5x at $100/month. The upgrade is about limits, not about switching to Opus. Keep Sonnet as your default and reach for Opus selectively.

Full-time developer, Claude Code is your primary IDE all day, heavy Opus usage for architectural work: Opus 4.7 on Max 20x at $200/month. At this usage level, the rate limit predictability is worth the price regardless of the per-token cost comparison.

Building a product via API with no clear need for Opus depth: Sonnet 4.6 at $3/$15 per MTok. Default to Sonnet. Add Opus routing for specific task types only after you have measured whether it produces better output for your use case.

If the slowdowns and billing changes are pushing you to evaluate other tools altogether, our Claude Code alternatives roundup covers the realistic options. And if you have noticed Claude trying to tell you to go to sleep mid-session, that is a separate, unrelated issue we covered this morning.

The Bottom Line

Opus 4.7 is not a clear upgrade over Sonnet 4.6 for most indie hacker use cases. The tasks where Opus visibly outperforms Sonnet are real, but they are not the tasks most solo devs spend their time on. The regression on routine work makes the premium harder to justify.

Start on Sonnet 4.6. Use Opus when you hit a task where you can genuinely feel the quality ceiling. Track whether that happens enough to justify $80 to $180 more per month. Most indie hackers who do this math end up staying on Pro.