diff --git a/apps/cloud/src/engine/execution-rate-limit.ts b/apps/cloud/src/engine/execution-rate-limit.ts
index 906bee2522..03f5d75b28 100644
--- a/apps/cloud/src/engine/execution-rate-limit.ts
+++ b/apps/cloud/src/engine/execution-rate-limit.ts
@@ -47,7 +47,7 @@ export const RATE_LIMIT_WINDOW_MS = 3_600_000;
 // against the largest customer is a losing game, so the number no longer tries
 // to describe them — paid orgs are exempt below, and this now has only
 // free-tier abuse to cover, which is what it was picked for.
-export const EXECUTIONS_PER_ORG_PER_HOUR = 1000;
+export const EXECUTIONS_PER_ORG_PER_HOUR = 10_000;
 // Counter DO slower than this => fail open rather than stall executions.
 const RATE_LIMIT_CHECK_TIMEOUT_MS = 2_000;
 // Exemption lookup slower than this => treat as unresolved.
diff --git a/e2e/setup/execution-limits.ts b/e2e/setup/execution-limits.ts
index 16395523dd..e98e834be0 100644
--- a/e2e/setup/execution-limits.ts
+++ b/e2e/setup/execution-limits.ts
@@ -5,7 +5,7 @@
 //
 // Picking the value is a squeeze from both sides. It must be LOW enough that
 // the backstop scenario can exhaust it with real sequential executions (prod's
-// 1000/hour cannot be reached in a test), and HIGH enough that no other
+// 10,000/hour cannot be reached in a test), and HIGH enough that no other
 // scenario trips it: the counter is per organization and every `execute` a
 // scenario runs counts against its org, so this must exceed the busiest
 // single-org scenario's execute count (currently toolkits-mcp at ~8) with