@levelsio opened Cloudflare’s Email Sending API yesterday and posted a six-word side-comment: “Resend is literally just SES with a 500% markup.” One sentence reframed an entire vendor category.
Resend’s CEO already conceded in 2024 that this entry was inevitable. Now it’s here, and SaaS-pricing-on-an-AWS-wrapper margins are about to compress for a lot more vendors than just one.
In today’s indie hacker news:
- 📧 Cloudflare’s Email API undercut Postmark; Levels migrated in a day
- ⚡ Maryland billed every household $345 for out-of-state data centers
- 🖨️ Bambu Lab C&D’d a dev who restored their own AGPL code
- 💻 A dev scrapped 30 weekends of AI code; METR says he’s right
- 🛒 First Dollar: a SaaS founder closed his first $29 customer
TOP STORIES
RESEND JUST GOT SES’D
Cloudflare Email Sending hit public beta and Levels published the price table that gutted Postmark.
The story: Cloudflare’s Email Sending public beta opened in April: $5/mo Workers Paid plus 3,000 free emails, then $0.35 per 1,000 after. Levels’ migration thread hit 1.5M views with the comparison nobody had run publicly: $354/mo on Cloudflare versus $1,206 on Postmark Platform at 1M emails. He finished migrating his transactional stack the same day. SPF, DKIM, DMARC and the suppression list auto-configure.
The details:
- AWS SES at the same volume sits at $100 if you hand-roll bounce handling. Resend Scale lands around $650 (Postmark pricing, Cloudflare pricing)
- No bounce webhooks. Monitoring requires polling the GraphQL Analytics API, not push events
- No batch endpoint. Single-send REST or a Workers binding (
env.EMAIL.send(message)). Painful for digest sends - Spamhaus SBL listings on Cloudflare infra fell from 1,201 in 2024 to roughly 47 in 2026
Why builders care: High-volume transactional senders on Postmark or Resend are leaving $150-$850/mo of margin on the table. Caveats: don’t move magic-link login to a service this fresh, and polling-only bounce data hurts digest workflows.
Work from any WiFi like it's your home network. NordVPN's Meshnet runs a free private mesh between your laptop, dev box, and home server. SSH from a café without exposing a port, the way you'd use Tailscale. The paid VPN on top lets you test geo-fenced Stripe checkouts or feature flags from any country.
We get a cut if you sign up. Only added for tools we use ourselves.
PAY VIRGINIA’S POWER BILL
Maryland regulators are passing $1.6B in grid costs to ratepayers for data centers built in another state.
The story: PJM Interconnection, the grid operator covering 13 states and 67M people, approved $22B in regional transmission upgrades and assigned $2B of the bill to Maryland for upgrades primarily serving Northern Virginia’s Loudoun County data centers. Pass-through math: $345 per residential customer over a decade, $673 per commercial, $15,074 per industrial. Maryland’s Office of People’s Counsel filed a FERC complaint May 8 calling the allocation unjust, citing 660% MWh growth in Virginia data center load since 2013.
The details:
- Data centers drove 63% of the price spike in PJM’s 2025/2026 capacity auction, adding $9.3B recovered from customers across the region
- Virginia handed data centers $3.6B in tax exemptions (FY2022-2025), then exported the grid bill to neighbors via PJM allocation rules
- January 2027: Virginia’s 85% demand-charge floor for data centers takes effect. First state to legislate direct cost assignment instead of socializing it
Why builders care: The AI infra bubble is landing on a residential meter, and the pass-through hits anyone on East Coast colo or us-east-1. Virginia’s 2027 cost-assignment law will get copied. Cloud-pricing geography turns into a real moat as it spreads.
SUED OVER YOUR OWN CODE
Bambu Lab cease-and-desisted the dev who restored OrcaSlicer cloud printing using Bambu’s own AGPL source. Rossmann pledged $10K.
The story: Paweł Jarczak’s OrcaSlicer-bambulab fork restored direct cloud printing on Bambu printers, killed by January 2025 Bambu Connect firmware. The fork was built entirely on Bambu’s own publicly published source. Jarczak got a private cease-and-desist alleging impersonation and reverse engineering, was barred from publishing the correspondence, and shut the project down. Louis Rossmann posted a video titled “I’ll put up $10,000 to teach Bambu Labs a lesson,” pledging to cover Jarczak’s legal fees if Bambu escalates.
The details:
- “User-Agent is not authentication. It is only self-declared client metadata.” Jarczak, rebutting the impersonation claim
- OrcaSlicer crossed 1M+ downloads in March 2024. It’s a fork of Bambu Studio, which forked PrusaSlicer. Everything in the lineage shares the same copyleft license
- 16 months elapsed between the firmware that killed the feature and the legal threat against the dev who restored it
- Rossmann founded the Fulu Foundation in 2025 to fund exactly this kind of fight. HN thread: 503 points in 13 hours
Why builders care: Manufacturer ships under a permissive license, kills a feature via firmware, then uses a private threat to suppress the fork that restored it. Jarczak folded because cost asymmetry made fighting irrational for a solo dev. Rossmann’s pledge flips that math. Question for indies shipping copyleft on someone else’s hardware: does the license actually protect you when the original author is the one suing?
THE METR SLAP
A dev scrapped 30 weekends of vibe-coded TUI; the METR study says experienced devs are slower with AI.
The story: shvbsle’s k10s.dev post hit HN with 234 commits and 30 weekends of evidence: a vibe-coded Kubernetes TUI that produced a 1,690-line model.go wrapping 110 switch/case branches in one Update function. He’s rewriting in Rust by hand. The data backs the rant. METR’s July 2025 randomized controlled trial on 16 experienced open-source developers found AI tools made them 19% slower across 246 real issues. The same developers believed AI made them 20% faster.
The details:
- “AI writes features, not architecture. The longer you let it drive without constraints, the worse the wreckage gets.” shvbsle
- Same day, the RPCS3 PS3 emulator team asked contributors on X to stop submitting AI-generated PRs: “You can’t possibly handwrite the type of shit AI slop we have been seeing”
- Xu et al. (Jan 2026): experienced devs reviewed 6.5% more code post-Copilot but showed a drop in original-code productivity
- James Shore: “If you double your output and your cost of maintaining that output, two times two means you’ve quadrupled your maintenance costs”
Why builders care: The senior tax (review, refactoring, architectural firefighting) gets absorbed upstream by experienced devs. That’s why agents accelerate juniors and slow seniors. Solo founders ARE the senior. AI on greenfield features is fine. AI steering architecture compounds debt exponentially. shvbsle’s fix (write a CLAUDE.md spec first, THEN generate) is what the research already prescribes.
TRENDING TODAY
🧠 Local AI is having a moment. unix.foo argued the case to 725 HN points: “You took a UX feature and turned it into a distributed system that costs you money.” Companion proof: an r/LocalLLaMA thread ran Qwen3.6 35B A3B on a single RTX 4060 (8GB VRAM) at 37-40 tokens/sec with 190K context. Cloud-only AI features in 2026 are a design choice now, not a constraint.
🛡️ GrapheneOS torched hardware attestation as a monopoly enabler, 1,046 HN points. Argument: remote attestation is being weaponized to gate banking, streaming, and basic services behind Apple/Google-approved devices. Run a custom ROM, get exiled. For indie builders, the next platform fight isn’t App Store rules. It’s the runtime checking whether your app is allowed to exist on the user’s hardware.
🔒 Tony Dinh ran an AI security audit on his own codebase for $70. 100+ flagged issues, dozens of PRs merged after manual review. 155K views, 606 likes. Pattern becoming a category: solo builders running adversarial audits with token budgets that fit on a credit card.
DRAMA
THE SIX-WORD COMPRESSION
Levels’ SES-markup takedown of Resend stuck, and the CEO didn’t reply.
Within hours of the tweet: 1,371 likes, 187 replies, 618 bookmarks. Subthreads picked it up asking whether email-as-a-service is a real product or a margin business. Zeno Rocha’s last public position on this critique was in 2024: “Email is not a winner-takes-all kind of market.” He hadn’t responded by press time.
Why builders care: When your moat is API ergonomics on top of someone else’s commodity, one viral framing compresses it overnight. If your pitch deck has a slide explaining why your wrapper is worth multiples of the underlying, somebody with 800K followers will eventually compress that slide into one sentence.
FIRST DOLLAR
THE $29 DOUBLE-POST
u/DrJonah345 closed his first paying customer on phaysr.com, then posted the same emotion to two subreddits.
Same builder cross-posted to r/indiehackers (9 upvotes, 31 comments) and r/SaaS (102 upvotes, 32 comments) within seven minutes. The double-post is the tell: the first-paying-customer moment hits hard enough that a rational person publishes it twice. Two weeks of building, one viral tweet as inspiration, $29 on the board. The full circle to $1K MRR runs through this exact dopamine loop.
STACK OF THE DAY
✉️ Cloudflare Email Sending (public beta)
Cloudflare Email Sending. Builder checklist if you’re wiring it up tomorrow. Enable Workers Paid, point your domain at Cloudflare, hit the REST endpoint from anywhere or use the binding (env.EMAIL.send(message)) on the edge. Pin a budget alert before sending production traffic. Daily caps for new accounts are undisclosed.
Not sponsored. We just feature tools builders would actually use.
BOOKMARKED TODAY
📦 Show HN: Kheeper, a registry for bootable images. Container-style registry purpose-built for bootable OS images. For homelab and immutable-infra builders tired of duct-taping OCI registries.
🧰 Show HN: Agent Postmortem Skill. A Claude Code / Codex skill that forces agents to produce verifiable evidence (tests, screenshots, repro steps) before claiming a task is done. If you’ve ever caught an agent reporting “fixed!” on a bug it didn’t touch, this is for you.
Curated by AI, built by a human.