A year into its pledge to make every feature available to every plan, Cloudflare has published a progress report. The headline commitment: the company now says it will introduce no new Enterprise-only features, with carve-outs only for inherently enterprise-oriented products like Cloudflare for Government. That is a structural change worth paying attention to, not just a feature list.
The problem it fixes
Cloudflare’s Enterprise tier originally existed for procurement, not capability: invoices, custom contracts, dedicated support. Over time, though, a two-tier system emerged where some of the most advanced features were locked behind an Enterprise contract. If you have ever prototyped on a free plan and hit a wall that only money could move, you know how that shapes which tools builders choose.
The stated philosophy from Cloudflare is simple: build for the most demanding customers, then make those capabilities available to everyone. Where plans differ, the difference should be how much you can use, not what you can use.
What actually changed
Per the Cloudflare update, every GA feature launched this week that exists on an Enterprise plan is now available to Pay-as-you-go customers, and most are on the free tier. The concrete items:
- Logpush and Logpush Transformers are now on all plans, with self-service pricing. Transformers adds SQL-based filtering, redaction, and enrichment before log delivery, so you can skip running a separate ETL pipeline.
- RBAC is now available across nearly all products at account and zone level, and at the individual resource level for Workers, R2, and Access.
- A New Account button lets anyone create additional, independently billed accounts for team or project segmentation. Thousands of customers are doing this weekly, per Cloudflare.
- Organizations group accounts under a single analytics and configuration surface, in beta for Enterprise now and rolling out to free accounts in early 2027.
- Higher limits: Workers can now use 1 second of startup time, 32 MiB WebSocket messages, 1 million subrequests per request, and 64 MiB uncompressed sizes. Containers jumped to 6 TiB of memory and 1,500 vCPU per account.
Cloudflare also shipped a billable usage dashboard and API with budget alerts on by default, and is prototyping hard spending caps with early availability in Q4 2026.
The operational pattern worth stealing
The most useful part of the post is not the feature list but how Cloudflare runs its own platform on these tools. Each team gets an account per team or per service, managed through Terraform so changes are peer-reviewed and auditable. Narrow account scope means broader per-engineer permissions without a large blast radius. Everything rolls up into one organization so the security team has unified visibility.
This maps closely to what I covered in Cloudflare turning telemetry into something agents can query: the platform is converging on a model where fine-grained access, audit trails, and queryable data are table stakes for everyone, not enterprise add-ons. If you are designing multi-tenant infrastructure, that account-per-service plus Terraform pattern is a solid default.
Limits and next steps
Cloudflare is candid that the goal is not yet met. Enterprise customers still cannot use the billable usage dashboard (expected 2027), Organizations are not self-serve for enterprises yet, and tags are not yet usable for billing or access control. If you are on a free or paid plan, the practical move is to re-audit which features you previously assumed were out of reach — Logpush and resource-level RBAC alone may change how you architect logging and team access. This progress also fits the broader pattern from Birthday Week launches I wrote about in 46 launches and what they mean for your stack: the free tier keeps getting closer to what used to require a contract.