--- title: Your free tier now has a claim step canonical: https://thebeat.dev/issues/2026-W37/ published: 2026-09-14 updated: 2026-09-17 covers_from: 2026-09-07 period: weekly covers: 2026-W37 week: 2026-W37 tags: - pricing - dx - plg collection: issues site: https://thebeat.dev/ license: https://creativecommons.org/licenses/by/4.0/ --- # Your free tier now has a claim step > An agent can now build on your product before anyone signs up. Neon lets one create a Postgres database with no account, and the signup moves to the end, where a person claims what the agent built. ## 1. Let the agent build first, then cap what it holds Neon shipped [Claimable Neon](https://neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later) 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](https://workos.com/auth-md) and lists fifteen adopters, but Neon is the one whose [case study](https://workos.com/blog/neon-claimable-postgres-auth-md-case-study) 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](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing) 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](https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/): 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](/threads/how-ai-features-get-priced) 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.](https://stackoverflow.blog/2026/09/10/re-introducing-developer-story)** 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.](https://posthog.com/blog/irl-events)** 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.](https://vercel.com/changelog/protect-production-deployments-for-free-on-every-plan)** 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.](https://developer.hashicorp.com/hcp/docs/vagrant/hcp-vagrant-eol)** 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`](https://workos.com/auth-md) 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](https://github.blog/changelog/2026-09-03-reopening-copilot-business-and-enterprise-signups), so search GitHub Community and Hacker News for "Copilot bill": one public story means GitHub shipped the meter without Atlassian's cap. ## Sources - [Neon — Claimable Neon: provisioned by agents, claimed by humans](https://neon.com/blog/an-agent-provisions-a-neon-backend-a-human-claims-it-later) - [WorkOS — How Neon made Postgres claimable for agents with auth.md](https://workos.com/blog/neon-claimable-postgres-auth-md-case-study) - [Atlassian — Atlassian's usage-based pricing: AI value with predictability and control](https://www.atlassian.com/blog/company-news/expanded-usage-based-pricing) - [Atlassian Support — How is my automation usage calculated](https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/) - [Stack Overflow — (Re)introducing Developer Story](https://stackoverflow.blog/2026/09/10/re-introducing-developer-story) - [PostHog — From 1 to 100 IRL events in a year](https://posthog.com/blog/irl-events) ## Related - [Last week — Your docs are production now](https://thebeat.dev/issues/2026-W36/) --- Part of [The Beat — developer marketing, on the record](https://thebeat.dev/). Content license: CC BY 4.0 — quote it, link the canonical page.