Your free tier now has a claim step

1. Let the agent build first, then cap what it holds

Neon shipped Claimable Neon (opens in a new tab) on Thursday. A coding agent reads neon.com/auth.md, runs neon claim create, and gets a Postgres project. No account, no card, no human. When it is done it hands the person a claim link. They sign in, the project moves into their organization, and every pre-claim credential is rotated.

The unclaimed project is small on purpose: 100 MB of storage, 1 GB of transfer, gone in 72 hours. The claim link lasts 15 minutes.

Railway did the human version in August: deploy with no account, 60 minutes to claim. Neon did it for the agent, on an open protocol. WorkOS publishes auth.md (opens in a new tab) and lists fifteen adopters, but Neon is the one whose case study (opens in a new tab) describes the anonymous flow.

Am I affected? If an agent can call your API and your first step is “create an account”, yes. What does the agent get for free? Not a card. A cap and a clock. What do you get? Neon says it plainly: it wants to see which agents find the file and how far they get. A signup form counts people. A claim counts agents.

The trade-off is real. Anonymous provisioning is an abuse surface, and the caps are the abuse control. Set them as a pricing decision, not a security afterthought.

Your move:

• Write the unclaimed tier in three numbers: storage, transfer, hours. Put them on the pricing page.
• Publish what an agent may do with no key. /auth.md if you can, a paragraph in llms.txt if you cannot.
• Count discovered, created and claimed as one funnel. Claimed is the activation.

Takeaway: for a human the signup was the front door. For an agent it is the exit. Move it to after the first success.

2. Ship the cap three months before the meter

Atlassian added two meters (opens in a new tab) on September 1: automation steps and AI agent resolutions. Billing starts December 3. The admin tools shipped now: live usage per team, and limits an admin sets. The allowance and the overage are in the docs (opens in a new tab): a Jira Standard seat includes 400 steps a month, and extra usage costs $0.50 per 1,000 steps.

An automation step is not an AI feature. It is the first non-generative unit to reach a usage meter since the pricing thread opened in July. The meter is a billing habit now, not a pass-through of model cost.

A cap on by default costs you overage revenue. It buys you the signup and the renewal. Atlassian chose admin-set limits over a hard stop, which is the honest middle.

Your move:

• If you meter anything in the next two quarters, date the bill and ship the usage page first.
• Put the included allowance and the overage price in the same eyeline as the meter.

Takeaway: a meter announced with its cap is pricing. A meter announced alone is a surprise with a date on it.

Quick hits

• Stack Overflow brought back Developer Story, and said why. (opens in a new tab) Chatbots answer the questions now, so it is selling a record of who answers them, though the verified part is still a promise.
• PostHog went from 1 to more than 100 in-person events in a year. (opens in a new tab) No mandate and no speaker training: the events team proposes the slot and pays travel, and more than half the company has demoed somewhere.
• Vercel made deployment protection free on every plan. (opens in a new tab) It was a $150-a-month add-on, so a paid line item is now a reason to start on the free tier.
• HashiCorp’s Vagrant registry shuts on December 31. (opens in a new tab) Our August deep dive recorded June 2027, a date no HashiCorp page carries today, and the ledger is corrected.

Open questions

1. Does a third vendor ship a claim-later tier by October 31? Fetch /auth.md (opens in a new tab) from Supabase, PlanetScale and Vercel and look for the word “anonymous”: a third makes claim-later the category’s agent free tier, none means Neon ran an experiment.
2. Does the first Copilot bill-shock post land by October 31? From October 1 every Copilot Business and Enterprise seat is billed up front (opens in a new tab), so search GitHub Community and Hacker News for “Copilot bill”: one public story means GitHub shipped the meter without Atlassian’s cap.