Cloudflare
Cloudflare runs the Adventive edge: application logic, database access, private connectivity, and identity. Each service below links to its operating standard.
New here? The Architecture Map is an interactive drill-down of the whole application with Cloudflare as the front door, and the Account Inventory is the as-built record of everything in the account.
Services
Section titled “Services”Workers run the application logic at the edge. The standard covers naming, wrangler configuration, secrets, QA and deployment, resiliency, and observability.
Hyperdrive pools database connections at the edge and reaches the private AWS databases through the Tunnel. The standard covers read-only and read-write credential and connection naming, and the provisioning mechanism.
Tunnel carries Worker-to-database traffic from the edge to the private AWS network. Its operating standard spans both providers, so it lives in Cloud Connectivity; this entry points there.
Status Dashboard is the operator health surface at status.adventive.dev — the live Network Operations map and the classic status table, backed by one-minute checks and a read-only AWS topology collector.
Account inventory and architecture
Section titled “Account inventory and architecture”The Account Inventory is the as-built record of the whole Cloudflare account, generated read-only from the API and refreshed on a schedule. It covers the account and its 13 zones, DNS and request routing, the Workers fleet and its storage, and the Zero Trust and security posture, with a running change log. The Architecture Map turns that inventory into an interactive drill-down of the whole application.
Other services
Section titled “Other services”Access gates every internal hostname against JumpCloud and presents service-token credentials to Hyperdrive. Pages hosts this docs site and the operator UIs. R2, D1, and KV back individual Workers. Each gets its own page here as its standard is written.