Cloudflare is opening its Logpush service to Free, Pro and Business customers through self-service, pay-as-you-go pricing, removing an Enterprise-only restriction. Its 2 October announcement also details higher limits for vector databases, AI Search and application hosting, giving smaller teams more room before they hit the ceiling. The important distinction: access is widening, but that does not mean every feature is free. The velvet rope is moving; the meter remains.
Cloudflare Watch analysis
What happened
Cloudflare’s announcement updates its year-old pledge to make every feature accessible beyond Enterprise contracts. The company says every generally available feature launched during its Birthday Week that is offered on Enterprise is also available to pay-as-you-go customers, with most available on the free tier.
It also acknowledges that the wider pledge is not yet complete. Among the concrete changes, Logpush now lets customers on all plans send Cloudflare logs to external storage, security and analytics services. Logpush Transformers is also becoming generally available to all customers.
Our top picks
- Logpush without an Enterprise contract
Free, Pro and Business customers can buy log delivery through self-service pricing and use their existing storage and analysis tools. - Four times the Vectorize index capacity
Each index can hold 20 million vectors rather than five million; queries can return up to 50 matches instead of 20. - More metadata for AI Search
Vectors can carry up to 10 KiB of metadata, replacing the previous 500-character limit for each text field. - Longer-lived outbound connections for Durable Objects
Objects with an active outbound connection can stay alive for up to 15 minutes, rather than becoming eviction-eligible after 70–140 seconds without incoming traffic. - More room for static sites
Pages projects can contain up to 100,000 static assets, up from 20,000.
Why it matters
For smaller operators, the Logpush change removes a procurement barrier between running a service and analysing its traffic in tools they already use. That is a practical improvement for teams that need exported logs but do not need an Enterprise buying arrangement.
The developer limits address a different constraint: applications outgrowing individual platform allowances. Larger vector indexes and richer search metadata give AI developers more capacity within the same services. Neither change, by itself, establishes better search accuracy or lower running costs.
Our read
This is a meaningful access change because it includes something teams can actually buy and use, rather than another promise to democratise a pricing page.
Start with the constraint you already have. If exporting logs required an Enterprise conversation, revisit Logpush. If a search application is approaching its index or metadata limit, reassess the new allowances before redesigning it around the old ones.
Keep feature access, usage limits and price as three separate questions. Cloudflare’s direction is welcome, but a feature becoming available on your plan is the beginning of a cost calculation, not the end of one.
What to watch
- Logpush’s usage charges and the total cost of sending logs to external destinations.
- Which remaining Enterprise-only features gain self-service access next.
- Whether the higher developer limits remove real application bottlenecks without creating unexpected bills.
Discussion spark: Should advanced cloud features be available on every plan with usage-based charges, or do predictable bundled tiers serve smaller teams better?
Sources and evidence
- Source update (2 October 2026, 13:00 UTC)
not affiliated with or endorsed by Cloudflare