Automatic fixes for your Cloudflare apps. Praxen Inc. catches issues, finds the root cause, and fixes them.
Connect with one API token. Praxen Inc. pre-fills the permissions it needs.
For connection steps, permissions and resource discovery, Set up the Cloudflare integration.
Get started for free Production down? Get help now Our founding team can help you get your Cloudflare app back up.Everything Praxen Inc. picks up.
Everything Praxen Inc. reads from your Cloudflare account.
Praxen Inc. covers every Worker and everything it binds to.
- requests vs normal
- errors vs normal
- CPU time vs normal
- P99 18x caught, no threshold
Reads Workers metrics, logs and traces
Requests, errors, CPU time and Durable Object compute are compared with each resource's normal. An 18x jump in P99 gets caught with no threshold set.
- bindings one graph
Follows bindings and DNS
Workers, Durable Objects, D1, R2, KV, Queues, zones and DNS sit in one graph with their bindings. A DNS record pointing at another cloud leads to what it serves.
- Worker no observability
- D1 Database no backups
- Cloudflare Queue stuck retrying
Flags risky setup
Praxen Inc. flags Workers without observability, D1 databases without backups and queues stuck retrying, and tells you how to fix each one.
- deploy checked first
- config change recorded
Starts from the last change
Every deploy and config change is recorded. When a Worker breaks, Praxen Inc. checks what changed first.
- cause in your code
- fix Worker's repo
Writes the fix to the Worker's repo
Praxen Inc. investigates across your code and logs. When the cause is in your code, it opens a pull request with the fix.
- read-only permissions
- code fixes your repo, for review
A read-only token
Praxen Inc. connects with a read-only Cloudflare token. It investigates and explains, and code fixes go to your repo for review.
Use Cloudflare with any coding agent. Praxen Inc. connects them.
Connect your agent to Praxen Inc. once and it can query Cloudflare alongside the rest of your stack.
Guides for Cloudflare
- Blog How to build a memory system for proactive agents Proactive agents run without a prompt, so each run has to start from what earlier runs learned. How we built memory for Praxen Inc.'s agents on git: one repository per team, a nightly clean-up, and lessons from merged pull requests.
- Blog Nobody reads pull request descriptions, so we made videos Almost none of the pull requests Praxen Inc. opens were asked for by an engineer, and a longer description does not make them easier to review. We are experimenting with a narrated video for every fix. Why, what it looks like, and what happened to merge rates.
- Guide How to correlate incidents with deploys using evidence Learn how to correlate incidents with deploys using release markers, metrics, logs and verified GitHub, Vercel, Cloudflare and Kubernetes change events.
- Guide What is change intelligence? A production safety guide What is change intelligence? Learn how deploys, config, flags, infrastructure and dependency changes connect to incidents, using tools you already have.
- Guide Fix Cloudflare “Error 1102: Worker exceeded resource limits” Why a Cloudflare Worker returns Error 1102, how to tell a CPU time overrun from a 128 MB memory overrun, and the code and Wrangler changes that fix each.
- Blog Turn your app into a context graph Agents that run software need a context graph of the app: every resource, what it connects to, the repository that deploys it and the team that owns it. How we built one on Durable Objects, keep it fresh across every provider without polling AWS, decide what counts as a change, and delete from it safely.
- Guide Workers Issues: route Cloudflare errors to coding agents Cloudflare's new Workers Issues groups exceptions and 5xx errors and sends them to Claude Code, Cursor, Devin or a webhook. Setup, automations and limits.
- Guide Cloudflare Hyperdrive connection errors: causes and fixes Fix Cloudflare Hyperdrive connection errors: config codes 2008 to 2016, pool exhaustion, connection_refused and stale clients reused across Worker requests.
- Guide Cloudflare Workers error 1101: causes and how to fix it Error 1101 means your Cloudflare Worker threw an uncaught JavaScript exception. Find the exception in logs, match it to its cause, fix it and roll back fast.
- Guide How to debug Cloudflare Workers errors: logs, traces and error codes Debug Cloudflare Workers errors step by step: read 1101 and 1102 codes, enable Workers Logs and source maps, use wrangler tail, DevTools and local traces.
- Blog How We Fixed Our Cloudflare Durable Objects Memory Exceeded Errors Cloudflare Durable Objects run in V8 isolates with a hard 128 MB limit. Ours idled at ~140 MB and was reset ~300 times a day. 130 MB of zod schemas were built at module load, most of them by code that was never called. How we profiled the production bundle, the two fixes, and the numbers, 218 MB to 82 MB and resets to zero.
Common questions.
Is Praxen Inc. an AI SRE for Cloudflare?
It does that work, though we call it self-operating software. Praxen Inc. keeps your Workers, Durable Objects and D1 in one graph, investigates what breaks and fixes it.
Can Praxen Inc. change my Cloudflare account?
No. Praxen Inc. connects with a read-only token, so it investigates and explains, and code fixes go to your repo for review.
How does detection work without alert rules?
Praxen Inc. reads your metrics, logs and traces around the clock and judges them against how each resource normally behaves. An 18x P99 regression is caught with no threshold set.
Does it work with my observability provider?
Yes. Praxen Inc. supports all the major observability providers, and you can connect any other through MCP. The full list is on getpraxen.app/integrations.
What does it cost?
Every plan, price and limit is on getpraxen.app/pricing.