pragma.vision Your technology observatory

Verification register Compute & Web Infra

Readiness verdict

Cloudflare Containers

A dated reading of what is claimed, reported, and independently verified in the current evidence.

As of
2026-06-28
Revision
1
Method
v1.0.0

Current reading

The readiness gap, in one scan

AI-assisted assembly · derived results

Claimed
85

Public ambition and stated capability

Reported
74

Observed practitioner reporting

Verified
63

Independently supported evidence

Gap
+22

Claimed minus verified

Evidence strength Critical

Decision

What the current evidence supports

Human editorial judgment · 2026-06-28

Adopt with guardrails

Why
GA on existing Workers Paid plan with scale-to-zero active-CPU pricing fits the free-tier-discipline (Rule 9) and co-locates with our Worker stack, but 1-3s cold starts, ephemeral disk, and manual scaling mean it is a batch/async fit, not a hot-path replacement, so guardrails (keep-warm or async-only) are required.
Next
Prototype a single containerized workload (e.g. a headless render or batch job) on Workers Paid, measure real cold-start + placement against a Tier-A platform's latency budget, and externalize all state (no reliance on ephemeral disk).

Constraints

Blockers

No named blocker is present in the current public projection.

Evidence summary

Derived counts

AI-assisted assembly

Total
8
Tier 1
0
Tier 2
1
Tier 3
7
Supports
3
Contradicts
4
Context
1
Latest observed
2026-06-24

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Revisions

Initial public reading

This is the initial public reading. No earlier readiness change is recorded.

Your opinion

Tell us anything.

What works, what doesn't, what's missing — especially about our watches, lenses, and the register itself. Anonymous is fine; leave an email if you'd like a reply.