Cloudflare Advances Pledge to Make Enterprise Features Accessible Across All Plans

Cloudflare Advances Pledge to Make Enterprise Features Accessible Across All Plans One year after announcing its initiative to eliminate enterprise-exclusive capabilities, Cloudflare has expanded several former Enterprise-tier features—including Logpush, multi-account organization, and identity tools—to free and pay-as-you-go customers, while pledging to introduce no new Enterprise-only features. Logpush, Transformers, and Custom Dashboards are now available across all customer plans, providing self-serve log routing and SQL-based formatting. Cloudflare expanded access management with resource-level RBAC, a self-service 'New Account' button, and an Organizations feature rolling out to free tiers in 2027. Moving forward, Cloudflare committed to introducing no new Enterprise-only features, differentiating plans by usage volume rather than capability access. Non-Enterprise customers received billing transparency tools including usage dashboards, an API, default budget alerts, and upcoming hard spending caps. Data and Logging Transitions Cloudflare expanded previously Enterprise-only data features to all tiers. Logpush is now available to Free, Pro, and Business plans on a pay-as-you-go basis, supporting datasets like firewall events and post-quantum visibility. Alongside it, Transformers reached general availability, enabling customers to filter, redact, and reformat logs using SQL before export without maintaining a standalone ETL pipeline, and Custom Dashboards became accessible to all tiers. Account Structure and Identity Controls To solve organizational bottlenecks tied to single-account management, Cloudflare introduced a self-service dashboard button that lets customers generate additional free, independently billed accounts. Fine-grained Role-Based Access Control (RBAC) was extended to individual resources such as Workers, R2, and Access. To unify disparate accounts, the new Organizations management surface entered beta for enterprises and is planned to roll out to free accounts in early 2027. Commitment Against Feature Gating and Billing Safeguards As part of its deployment updates, Cloudflare committed to creating no new Enterprise-only features, reserving exceptions only for inherently enterprise offerings such as Cloudflare for Government. Where plans still vary, Cloudflare intends to limit differences to usage allowances rather than feature sets. Additionally, non-Enterprise accounts received a billable usage API, dashboard, and default budget alerts, with hard spending caps targeted for prototyping in Q4 2026.

Cloudflare 公布功能平民化承诺进展：多项企业级功能向全量用户开放 在 Cloudflare CTO 提出“让每项功能对所有人可用”承诺一周年之际，Cloudflare 宣布多项曾仅限企业版（Enterprise）的功能现已向所有客户开放，并承诺未来不再推出新的企业专有功能，不同套餐的差异将集中在使用额度而非功能权限上。 Logpush、Transformers 与自定义仪表板等日志分析和可视化功能全面开放给免费及按量付费客户。 推出控制台直接创建新账户按钮，并启动 Organizations（组织）功能以实现多账户集中管理。 承诺未来不再新增企业专属功能（政府专用等特殊场景除外），并按流量分群优先向免费客户灰度部署。 上线计费使用情况仪表板、API 与预算提醒，并在测试硬性消费限额以提升账单透明度。 日志、分析与数据管理功能下放 本周起，支持向第三方推送日志的 Logpush 结束了企业专属状态，通过自助按量计费模式面向 Free、Pro 和 Business 用户开放，并扩充了防火墙事件、WebSocket 分析及后量子可见性等数据集。免 ETL 处理的 SQL 数据转换工具 Transformers，以及支持个性化展示关键指标的 Custom Dashboards 也已向全量用户正式推出（GA）。 多账户架构、RBAC 与 Organizations 管理 针对单一账户在管理海量资源时的瓶颈，控制台新增了“New Account”按钮，允许用户自助建立多个独立计费的免费账户。用于聚合账户、提供统一分析面板及共享 WAF、Gateway 和 Access 策略的“Organizations”功能已在企业版进入测试，定于 10 月正式推出，并将在 2027 年初拓展至免费账户。此外，细粒度 RBAC 已覆盖到 Workers 等单独资源，配合持续更新的 Terraform Provider 与资源标签（Resource Tagging）功能，实现多账户的基础设施即代码管理。 身份、网络与管理工具全面自助化 包括 Authentik 身份提供商接入、SCIM 审计日志、SCIM 2.0 组同步、MCP Server Portals，以及网络概览页（Network Overview）和统一路由（Unified Routing）在内的多项前企业版配置，现已全量普及。官方同时公开了内部实践经验：通过按团队或服务细分账户，并借助 Terraform 与单一顶层组织实现精细权限控制与全局合规。 不再新增企业专属功能与账单透明化 作为“Code Orange: Fail Small”计划的一部分，Cloudflare 确立了新代码优先按分群推送给免费用户的灰度机制，并明确承诺除政府专有服务等少数情况外，未来不再引入新的企业专有功能。此外，平台针对非企业客户上线了计费使用情况仪表板、API 及默认启用的预算报警，预计于 2026 年第四季度小范围测试硬性消费限额，并在持续上调多项产品的默认配额限制。

A year ago, Cloudflare CTO Dane Knecht announced our intention to make [every Cloudflare feature available to everyone](https://blog.cloudflare.com/enterprise-grade-features-for-all/). Cloudflare launched an Enterprise tier years ago when larger customers came to us looking for procurement options beyond a credit card, like invoices, custom contracts, and dedicated support. Those offerings met a customer need but over time, a two-tier system developed where some of our most advanced and powerful features were only available to Enterprise customers. Our goal was to close that gap. Today, teams of every size use Cloudflare, from Fortune 100 enterprises to small businesses, open-source projects, and individuals. Across the platform, we’re committed to ensuring that every user or team can make use of all of Cloudflare’s capabilities in a way that helps their organization thrive. The underlying philosophy is that Cloudflare should offer products suitable for our most demanding customers — and make those capabilities available to everyone. Large or small, every customer would prefer not to have to call support. Building products that are easy to buy, configure, and consume means more of our products in use and a step closer to a better Internet for everybody. Every generally available (GA) feature we launched this week that is available on an Enterprise plan is also available to Pay-as-you-go customers, and most are available on the free tier. Where our plans differ, it's in how much you can use, not what you can use. While we haven’t yet met our goal that every feature be available to everyone, in the year since Dane’s announcement, we’ve made great progress. Here are a few products and features making the transition today from Enterprise to everyone. Flexibility on pushing logs to third parties and how logs are formatted expanded this week from Enterprise-only to all customers. [Logpush](https://developers.cloudflare.com/logs/logpush/) delivers Cloudflare logs to storage, security, and analytics destinations, helping customers monitor traffic, investigate issues, and analyze their data using existing tools. Previously available only to Enterprise customers, Logpush is now available to Free, Pro, and Business customers through self-service, pay-as-you-go pricing. Datasets available to Logpush have been expanding as well. We’ve recently added account-scoped firewall events, WebSocket analytics and per-zone post-quantum visibility. [Transformers](https://developers.cloudflare.com/logs/logpush/transformers/) is also becoming generally available to all customers. With Transformers, customers can use SQL to filter unnecessary records, redact sensitive information, enrich events, and reformat logs before delivery without operating a separate extraction, transformation and loading (ETL) pipeline. Together, Logpush and Transformers give every customer greater control over how their Cloudflare data is prepared and delivered. In addition, [Custom Dashboards](https://developers.cloudflare.com/changelog/post/2026-04-22-custom-dashboards-ga/) which let customers create personalized views highlighting the metrics most critical to them, is now available to all customers. Over the last year, we’ve dramatically expanded the availability of Role-Based Access Control (RBAC) across all Cloudflare products and for all customers. Today, nearly all products have RBAC roles available at the account and zone level. Recently, Workers joined R2 and Access in having RBAC roles available at the individual resource level as well, so Administrators can decide who on their team gets specific access to individual Workers. While fine-grained RBAC lets customers manage subsets of an account, this setup still relies on a small number of super administrators making choices about who gets access to what. Centralized authority works great when your problem space is small, but as the number of teams and projects being managed on Cloudflare grows, it can turn into an organizational bottleneck. The single account model is excellent in its simplicity, but it can start to feel a little crowded for customers maintaining hundreds or thousands of zones, workers, and storage products. That’s why we’ve been expanding our capabilities around managing multiple accounts. Last month, we quietly [launched](https://developers.cloudflare.com/changelog/post/2026-08-04-free-dashboard-button/) the **New Account** button on the dashboard that, for the first time, lets users create additional accounts directly. The response has been overwhelmingly positive, and we’re seeing thousands of customers branching out into additional accounts every week. When you use this button, it creates a new, free, Cloudflare account that you can use to segment your open source projects, or segment the work of multiple teams in your organization. Each of these accounts is independently billed, so you can segment spending across multiple cost-centers directly. Safeguards are in place to prevent fraud and abuse. While the New Account button is for everyone, for the time being, we recommend that Enterprise customers reach out to their account team to get new accounts provisioned instead. This lets you reuse your existing enterprise agreement and subscriptions across all of your accounts. There is no preset limit on how many accounts an enterprise can request. We will be adding additional features in the future that make this process self-serve for enterprises too. Once you’ve created multiple accounts, how do you organize and track them all? [Organizations](https://blog.cloudflare.com/organizations-beta/) allow customers to group accounts together with a single analytics and shared configuration surface. It’s in beta for Enterprise customers now, will be GA in October, and will be rolling out to free accounts in early 2027. Adding your multiple accounts to a single organization makes managing them easier by providing a unified surface for visibility and management. Organizations provide shared administrators with unified analytics and audit logging as well as shared WAF, Gateway, and Access IdP configurations. Enterprises are eligible for exactly one organization. We limit enterprises to a single organization, so there’s a single pane of glass that shows all the company’s assets in one place. This makes life easier, so you can invite the CISO, CTO, or other executive stakeholders and give them unified visibility. If you’re an Enterprise customer and haven’t tried organizations yet, you can [set one up](https://developers.cloudflare.com/fundamentals/organizations/for-enterprise/#set-up-your-organization) directly as long as you are a super administrator of at least one account and nobody else has already created the organization. If the organization has already been started, talk to the other Cloudflare administrators in your company to get your accounts added to it. This process ensures that there’s never an elevation of privilege as we layer on this new management plane. Once a customer has created multiple accounts, an organization to manage them, and set RBAC rules for the products and resources they contain, they need to be able to manage them in a way that’s auditable and repeatable. Terraform lets customers use Infrastructure as Code to manage everything using version-controlled code rather than clicking on the dashboard in a way that may not be repeatable. In the last year, Cloudflare has made dramatic progress creating a Terraform provider that is built programmatically, so it’s always up-to-date with the latest version of the Cloudflare API. Terraform, like the other features mentioned in this post, is available to all customers, Enterprise and not. Additionally, [Resource Tagging](https://developers.cloudflare.com/changelog/product/resource-tagging/) lets customers apply key value tags to a very broad set of resources within the Accounts and Organizations. Today tags can be produced interactively or via API and are useful for organizing resources in the dashboard. In the future we intend to make tags useful in billing and access control scenarios and to be manageable via Terraform. With the increasing menu of enterprise-ready options for everyone, one of the top questions we get is “What does Cloudflare do internally?” Within Cloudflare, we create accounts per team, or per service, depending on the nature of the team. We then use Terraform to manage account access and production configuration, giving teams a peer-reviewed, auditable path for changes. Because the scope of each account is narrow, we can grant broader permissions to the engineers responsible for that account while keeping the blast radius contained. This lets teams grow their accounts organically without bottlenecking on a small number of central administrators, and it makes operational work like on-call response faster and safer. Every account at Cloudflare lives within Cloudflare’s organization, which provides our security team with administrative access to every account within the organization, as well as analytics, policy management, and shared configurations. This makes it easier to align every account in the organization to our security standards. Our teams have the right blend of autonomy and centralized control to go fast. Enabling teams to quickly sort, organize, and filter their resources is critical in our production environments. While it’s still early, Resource Tagging is enabled internally and teams have begun to roll out tags to make finding the WAF rule, R2 bucket, etc. that they need to interact with easier. We launched support for the [Authentik](https://developers.cloudflare.com/changelog/post/2026-03-17-scim-authentik-support/) identity provider (IdP), [SCIM Audit logging](https://developers.cloudflare.com/changelog/post/2026-03-18-scim-audit-logging/), and SCIM 2.0 Group Sync. [MCP Server Portals](https://developers.cloudflare.com/changelog/post/2026-09-24-mcp-portals-ga/) moved into general availability. All these features were once in some way Enterprise-only. Even network management is going self-serve: the [Network Overview page](https://developers.cloudflare.com/changelog/post/2026-04-21-network-overview-page/) and [Unified Routing](https://developers.cloudflare.com/changelog/post/2026-09-18-unified-routing-ga/) both recently became available for all. Solving big problems starts with first ensuring they aren’t getting any larger. This year, as part of [Code Orange: Fail Small](https://blog.cloudflare.com/code-orange-fail-small-complete/), we announced a commitment to rolling new code out by traffic cohort, starting with our free customers. As a result, today we are committed to introducing **no new Enterprise-only features**. Naturally there will be some carve-outs for things like [Cloudflare for Government](https://blog.cloudflare.com/fedramp-class-d-certification/) that are inherently Enterprise-oriented in nature. Beyond making previously enterprise-only features available to everyone, we’ve also done a lot of work to make Cloudflare more powerful and accessible for everyone In August, we introduced the [billable usage dashboard and API](https://blog.cloudflare.com/billable-usage-api/) which lets non-Enterprise customers see how much they’ve spent and download their consumption data to use offline directly or through third-party tools like Vantage. We also introduced budget alerts, which are on by default to prevent unpleasant billing surprises. We're prototyping hard spending caps now, with early availability in Q4 2026. Because Enterprise customers have dramatically more variation on contract terms and how they pay, this experience is not yet available to Enterprise customers, but we are hard at work and expect to have an announcement in 2027. Over the past year we’ve increased limits across Cloudflare products. We’re constantly working to increase these defaults, and keep our front door as open as possible to people building the next big thing. `topK` can now `concat()` Between exposing formerly enterprise-only features to everyone and increasing the power of features that were already available to everyone, Cloudflare is committed to building the most powerful and accessible platform for customers large and small without the need for a contract. We still have much work to do on Dane’s pledge from a year ago, but we are committed to getting there and are delighted to be able to highlight our progress over the last year.