[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M796H71ZP7ZN9BW0BJYAMVNW":3,"skill-same:01M796H71ZP7ZN9BW0BJYAMVNW":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M796H71ZP7ZN9BW0BJYAMVNW","supabase-rate-limits",null,"Manage Supabase rate limits and quotas across all plan tiers.\nUse when hitting 429 errors, configuring connection pooling,\noptimizing API throughput, or understanding tier-specific quotas\nfor Auth, Storage, Realtime, and Edge Functions.\nTrigger: \"supabase rate limit\", \"supabase 429\", \"supabase throttle\",\n\"supabase quota\", \"supabase connection pool\", \"supabase too many requests\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-rate-limits\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase-rate-limits\ndescription: |\n  Manage Supabase rate limits and quotas across all plan tiers.\n  Use when hitting 429 errors, configuring connection pooling,\n  optimizing API throughput, or understanding tier-specific quotas\n  for Auth, Storage, Realtime, and Edge Functions.\n  Trigger: \"supabase rate limit\", \"supabase 429\", \"supabase throttle\",\n  \"supabase quota\", \"supabase connection pool\", \"supabase too many requests\".\nallowed-tools: Read, Write, Edit, Bash, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, supabase, rate-limiting, reliability, quotas]\n---\n# Supabase Rate Limits\n\n## Overview\n\nSupabase enforces rate limits and quotas across every API surface — PostgREST, Auth, Storage, Realtime, and Edge Functions. Limits scale by plan tier. This skill covers the exact numbers per tier, connection pooling via Supavisor, retry\u002Fbackoff patterns, pagination to reduce payload, and dashboard monitoring so you can stay within quotas and handle 429 errors gracefully.\n\n## Prerequisites\n\n- Active Supabase project (any tier)\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Project URL and anon\u002Fservice-role key available\n- Node.js 18+ or equivalent runtime\n\n## Instructions\n\n### Step 1 — Understand Rate Limits by Tier and Surface\n\nEvery Supabase project has per-surface limits that differ by plan. Know these numbers before you architect:\n\n**API Request Limits**\n\n| Metric | Free | Pro | Enterprise |\n|--------|------|-----|------------|\n| Requests per minute (RPM) | 500 | 5,000 | Unlimited (custom) |\n| Requests per day (RPD) | 50,000 | 1,000,000 | Unlimited (custom) |\n\n**Auth Rate Limits**\n\n| Endpoint | Free | Pro |\n|----------|------|-----|\n| Signup | 30\u002Fhour per IP | Higher (configurable) |\n| Sign-in (password) | 30\u002Fhour per IP | Higher (configurable) |\n| Magic link \u002F OTP | 4\u002Fhour per user | Configurable |\n| Token refresh | 360\u002Fhour | 360\u002Fhour |\n\nAuth limits are per-IP and per-user. Configure custom limits in Dashboard > Authentication > Rate Limits.\n\n**Storage Bandwidth**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Storage size | 1 GB | 100 GB |\n| Bandwidth | 2 GB\u002Fmonth | 250 GB\u002Fmonth |\n| Max file size | 50 MB | 5 GB |\n| Upload rate | Shared with API RPM | Shared with API RPM |\n\n**Realtime Connections**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Concurrent connections | 200 | 500 |\n| Messages per second | 100 | 500 |\n| Channel joins | Shared with connection limit | Shared |\n\n**Edge Functions**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Invocations\u002Fmonth | 500,000 | 2,000,000 |\n| Execution time | 150s wall \u002F 50ms CPU | 150s wall \u002F 2s CPU |\n| Memory | 256 MB | 256 MB |\n\n**Database Connections**\n\n| Mode | Free | Pro |\n|------|------|-----|\n| Direct connections | 60 | 100+ |\n| Pooled connections (Supavisor) | 200 | 1,500+ |\n\n### Step 2 — Configure Connection Pooling with Supavisor\n\nSupavisor is Supabase's built-in connection pooler (replaced PgBouncer). It supports two modes:\n\n**Transaction mode (port 6543)** — recommended for serverless:\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\n\u002F\u002F Transaction mode: connections returned to pool after each transaction\n\u002F\u002F Best for: serverless functions, Edge Functions, high-concurrency apps\nconst supabase = createClient(\n  'https:\u002F\u002Fyour-project.supabase.co',\n  process.env.SUPABASE_ANON_KEY!,\n  {\n    db: {\n      \u002F\u002F Use the pooler connection string with port 6543\n      \u002F\u002F Format: postgresql:\u002F\u002Fpostgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:6543\u002Fpostgres\n    }\n  }\n)\n\n\u002F\u002F For direct Postgres connections (e.g., Prisma, Drizzle), add pgbouncer=true\n\u002F\u002F Connection string: postgresql:\u002F\u002F...@pooler.supabase.com:6543\u002Fpostgres?pgbouncer=true\n```\n\n**Session mode (port 5432)** — for LISTEN\u002FNOTIFY and prepared statements:\n\n```typescript\n\u002F\u002F Session mode: dedicated connection per client session\n\u002F\u002F Best for: long-lived connections, LISTEN\u002FNOTIFY, prepared statements\n\u002F\u002F Connection string: postgresql:\u002F\u002F...@pooler.supabase.com:5432\u002Fpostgres\n```\n\n**When to use which mode:**\n\n| Use case | Mode | Port |\n|----------|------|------|\n| Serverless \u002F Edge Functions | Transaction | 6543 |\n| Next.js API routes | Transaction | 6543 |\n| Long-running workers | Session | 5432 |\n| Realtime subscriptions | Direct (no pooler) | 5432 |\n| Prisma \u002F Drizzle ORM | Transaction + `?pgbouncer=true` | 6543 |\n\n### Step 3 — Implement Retry, Pagination, and Monitoring\n\n**Retry with exponential backoff for 429 errors:**\n\n```typescript\nimport { createClient, SupabaseClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n)\n\ninterface RetryConfig {\n  maxRetries: number\n  baseDelayMs: number\n  maxDelayMs: number\n}\n\nasync function withRetry\u003CT>(\n  operation: () => Promise\u003C{ data: T | null; error: any }>,\n  config: RetryConfig = { maxRetries: 3, baseDelayMs: 500, maxDelayMs: 10_000 }\n): Promise\u003CT> {\n  for (let attempt = 0; attempt \u003C= config.maxRetries; attempt++) {\n    const { data, error } = await operation()\n\n    if (!error) return data as T\n\n    const isRetryable =\n      error.message?.includes('rate limit') ||\n      error.message?.includes('too many requests') ||\n      error.code === '429' ||\n      error.code === 'PGRST000'  \u002F\u002F connection pool exhausted\n\n    if (!isRetryable || attempt === config.maxRetries) {\n      throw new Error(`Supabase error after ${attempt + 1} attempts: ${error.message}`)\n    }\n\n    \u002F\u002F Check Retry-After header if available\n    const retryAfter = error.details?.retryAfter\n    const delay = retryAfter\n      ? retryAfter * 1000\n      : Math.min(\n          config.baseDelayMs * Math.pow(2, attempt) + Math.random() * 200,\n          config.maxDelayMs\n        )\n\n    console.warn(`[supabase-retry] Attempt ${attempt + 1}\u002F${config.maxRetries}, waiting ${delay}ms`)\n    await new Promise((resolve) => setTimeout(resolve, delay))\n  }\n\n  throw new Error('Unreachable')\n}\n\n\u002F\u002F Usage — wraps any Supabase query\nconst users = await withRetry(() =>\n  supabase.from('users').select('id, email, created_at').eq('active', true)\n)\n```\n\n**Pagination to reduce payload and stay within limits:**\n\n```typescript\n\u002F\u002F Use .range() to paginate — reduces response size and avoids timeouts\nasync function fetchPaginated\u003CT>(\n  table: string,\n  pageSize = 100,\n  filters?: (query: any) => any\n): Promise\u003CT[]> {\n  const allRows: T[] = []\n  let from = 0\n\n  while (true) {\n    let query = supabase.from(table).select('*', { count: 'exact' })\n    if (filters) query = filters(query)\n\n    const { data, error, count } = await query.range(from, from + pageSize - 1)\n\n    if (error) throw error\n    if (!data || data.length === 0) break\n\n    allRows.push(...(data as T[]))\n    from += pageSize\n\n    \u002F\u002F Stop if we've fetched everything\n    if (count !== null && from >= count) break\n  }\n\n  return allRows\n}\n\n\u002F\u002F Usage\nconst allProducts = await fetchPaginated('products', 100, (q) =>\n  q.eq('status', 'active').order('created_at', { ascending: false })\n)\n\n\u002F\u002F Simple single-page fetch with .range()\nconst { data } = await supabase\n  .from('orders')\n  .select('id, total, status')\n  .range(0, 99)  \u002F\u002F First 100 rows (0-indexed)\n  .order('created_at', { ascending: false })\n```\n\n**Monitor usage via the Dashboard:**\n\n1. Navigate to Dashboard > Reports > API Usage\n2. Check the \"API Requests\" chart for RPM\u002FRPD trends\n3. Review \"Database\" section for connection count and pool utilization\n4. Set up alerts in Dashboard > Settings > Notifications for:\n   - API request threshold (e.g., 80% of RPM limit)\n   - Database connection saturation\n   - Storage bandwidth approaching limit\n\n**Batch operations to reduce request count:**\n\n```typescript\n\u002F\u002F BAD: N individual inserts = N requests against your RPM\n\u002F\u002F for (const item of items) await supabase.from('items').insert(item)\n\n\u002F\u002F GOOD: single batch insert (max ~1000 rows per request)\nconst { data, error } = await supabase\n  .from('items')\n  .upsert(batchOfItems, { onConflict: 'external_id' })\n  .select()\n\n\u002F\u002F For larger batches, chunk into groups\nfunction chunk\u003CT>(arr: T[], size: number): T[][] {\n  return Array.from({ length: Math.ceil(arr.length \u002F size) }, (_, i) =>\n    arr.slice(i * size, i * size + size)\n  )\n}\n\nfor (const batch of chunk(largeDataset, 500)) {\n  await withRetry(() =>\n    supabase.from('items').upsert(batch, { onConflict: 'external_id' }).select()\n  )\n}\n```\n\n## Output\n\nAfter applying this skill you will have:\n\n- Clear understanding of rate limits per tier (Free: 500 RPM \u002F 50K RPD, Pro: 5K RPM \u002F 1M RPD)\n- Connection pooling configured via Supavisor (port 6543 transaction mode for serverless)\n- Retry wrapper with exponential backoff handling 429 errors\n- Paginated queries using `.range(0, 99)` to reduce payload size\n- Batch upsert pattern reducing N requests to 1\n- Dashboard monitoring configured for API usage alerts\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `429 Too Many Requests` | Exceeded RPM or RPD limit | Apply `withRetry` backoff; reduce concurrency; upgrade tier |\n| `PGRST000: could not connect` | Connection pool exhausted | Switch to Supavisor transaction mode (port 6543); reduce concurrent queries |\n| Auth `over_request_rate_limit` | Too many signups\u002Flogins from one IP | Add CAPTCHA; configure custom auth rate limits in Dashboard |\n| Storage `413 Payload Too Large` | File exceeds tier limit | Use TUS resumable upload; check tier file size limit |\n| Realtime `too_many_connections` | Concurrent connection limit reached | Unsubscribe unused channels; upgrade to Pro for 500 connections |\n| Edge Function `BOOT_ERROR` | Cold start timeout or memory exceeded | Reduce bundle size; avoid large imports at top level |\n| `pgbouncer=true` errors with Prisma | Missing connection string parameter | Append `?pgbouncer=true` to pooler connection string on port 6543 |\n\n## Examples\n\n**Example 1 — Serverless Edge Function with rate-limit-safe client:**\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fprocess-webhook\u002Findex.ts\nimport { serve } from 'https:\u002F\u002Fdeno.land\u002Fstd@0.177.0\u002Fhttp\u002Fserver.ts'\nimport { createClient } from 'https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2'\n\nserve(async (req) => {\n  const supabase = createClient(\n    Deno.env.get('SUPABASE_URL')!,\n    Deno.env.get('SUPABASE_SERVICE_ROLE_KEY')!\n  )\n\n  const payload = await req.json()\n\n  \u002F\u002F Batch insert webhook events (single request vs N)\n  const { error } = await supabase\n    .from('webhook_events')\n    .insert(payload.events.map((e: any) => ({\n      type: e.type,\n      data: e.data,\n      received_at: new Date().toISOString(),\n    })))\n\n  if (error) {\n    console.error('Insert failed:', error.message)\n    return new Response(JSON.stringify({ error: error.message }), { status: 500 })\n  }\n\n  return new Response(JSON.stringify({ processed: payload.events.length }), { status: 200 })\n})\n```\n\n**Example 2 — Connection string selection for different runtimes:**\n\n```bash\n# Serverless (Vercel, Netlify, Edge Functions) — transaction mode\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres.abc123:password@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres?pgbouncer=true\"\n\n# Long-running server (Express, Fastify) — session mode\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres.abc123:password@aws-0-us-east-1.pooler.supabase.com:5432\u002Fpostgres\"\n\n# Direct connection (migrations, schema changes only)\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres:password@db.abc123.supabase.co:5432\u002Fpostgres\"\n```\n\n## Resources\n\n- [Supabase Platform Limits & Quotas](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fplatform\u002Fgoing-into-prod#rate-limiting)\n- [Supavisor Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [Auth Rate Limits Configuration](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fauth-rate-limits)\n- [Edge Functions Limits](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Flimits)\n- [Storage Limits](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fstorage#limits)\n- [@supabase\u002Fsupabase-js Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fintroduction)\n\n## Next Steps\n\nFor securing your Supabase project with RLS policies and API key management, see `supabase-security-basics`. For optimizing database queries and indexing, see `supabase-performance-tuning`.\n","# Supabase Rate Limits\n\n## Overview\n\nSupabase enforces rate limits and quotas across every API surface — PostgREST, Auth, Storage, Realtime, and Edge Functions. Limits scale by plan tier. This skill covers the exact numbers per tier, connection pooling via Supavisor, retry\u002Fbackoff patterns, pagination to reduce payload, and dashboard monitoring so you can stay within quotas and handle 429 errors gracefully.\n\n## Prerequisites\n\n- Active Supabase project (any tier)\n- `@supabase\u002Fsupabase-js` v2+ installed\n- Project URL and anon\u002Fservice-role key available\n- Node.js 18+ or equivalent runtime\n\n## Instructions\n\n### Step 1 — Understand Rate Limits by Tier and Surface\n\nEvery Supabase project has per-surface limits that differ by plan. Know these numbers before you architect:\n\n**API Request Limits**\n\n| Metric | Free | Pro | Enterprise |\n|--------|------|-----|------------|\n| Requests per minute (RPM) | 500 | 5,000 | Unlimited (custom) |\n| Requests per day (RPD) | 50,000 | 1,000,000 | Unlimited (custom) |\n\n**Auth Rate Limits**\n\n| Endpoint | Free | Pro |\n|----------|------|-----|\n| Signup | 30\u002Fhour per IP | Higher (configurable) |\n| Sign-in (password) | 30\u002Fhour per IP | Higher (configurable) |\n| Magic link \u002F OTP | 4\u002Fhour per user | Configurable |\n| Token refresh | 360\u002Fhour | 360\u002Fhour |\n\nAuth limits are per-IP and per-user. Configure custom limits in Dashboard > Authentication > Rate Limits.\n\n**Storage Bandwidth**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Storage size | 1 GB | 100 GB |\n| Bandwidth | 2 GB\u002Fmonth | 250 GB\u002Fmonth |\n| Max file size | 50 MB | 5 GB |\n| Upload rate | Shared with API RPM | Shared with API RPM |\n\n**Realtime Connections**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Concurrent connections | 200 | 500 |\n| Messages per second | 100 | 500 |\n| Channel joins | Shared with connection limit | Shared |\n\n**Edge Functions**\n\n| Metric | Free | Pro |\n|--------|------|-----|\n| Invocations\u002Fmonth | 500,000 | 2,000,000 |\n| Execution time | 150s wall \u002F 50ms CPU | 150s wall \u002F 2s CPU |\n| Memory | 256 MB | 256 MB |\n\n**Database Connections**\n\n| Mode | Free | Pro |\n|------|------|-----|\n| Direct connections | 60 | 100+ |\n| Pooled connections (Supavisor) | 200 | 1,500+ |\n\n### Step 2 — Configure Connection Pooling with Supavisor\n\nSupavisor is Supabase's built-in connection pooler (replaced PgBouncer). It supports two modes:\n\n**Transaction mode (port 6543)** — recommended for serverless:\n\n```typescript\nimport { createClient } from '@supabase\u002Fsupabase-js'\n\n\u002F\u002F Transaction mode: connections returned to pool after each transaction\n\u002F\u002F Best for: serverless functions, Edge Functions, high-concurrency apps\nconst supabase = createClient(\n  'https:\u002F\u002Fyour-project.supabase.co',\n  process.env.SUPABASE_ANON_KEY!,\n  {\n    db: {\n      \u002F\u002F Use the pooler connection string with port 6543\n      \u002F\u002F Format: postgresql:\u002F\u002Fpostgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:6543\u002Fpostgres\n    }\n  }\n)\n\n\u002F\u002F For direct Postgres connections (e.g., Prisma, Drizzle), add pgbouncer=true\n\u002F\u002F Connection string: postgresql:\u002F\u002F...@pooler.supabase.com:6543\u002Fpostgres?pgbouncer=true\n```\n\n**Session mode (port 5432)** — for LISTEN\u002FNOTIFY and prepared statements:\n\n```typescript\n\u002F\u002F Session mode: dedicated connection per client session\n\u002F\u002F Best for: long-lived connections, LISTEN\u002FNOTIFY, prepared statements\n\u002F\u002F Connection string: postgresql:\u002F\u002F...@pooler.supabase.com:5432\u002Fpostgres\n```\n\n**When to use which mode:**\n\n| Use case | Mode | Port |\n|----------|------|------|\n| Serverless \u002F Edge Functions | Transaction | 6543 |\n| Next.js API routes | Transaction | 6543 |\n| Long-running workers | Session | 5432 |\n| Realtime subscriptions | Direct (no pooler) | 5432 |\n| Prisma \u002F Drizzle ORM | Transaction + `?pgbouncer=true` | 6543 |\n\n### Step 3 — Implement Retry, Pagination, and Monitoring\n\n**Retry with exponential backoff for 429 errors:**\n\n```typescript\nimport { createClient, SupabaseClient } from '@supabase\u002Fsupabase-js'\n\nconst supabase = createClient(\n  process.env.SUPABASE_URL!,\n  process.env.SUPABASE_ANON_KEY!\n)\n\ninterface RetryConfig {\n  maxRetries: number\n  baseDelayMs: number\n  maxDelayMs: number\n}\n\nasync function withRetry\u003CT>(\n  operation: () => Promise\u003C{ data: T | null; error: any }>,\n  config: RetryConfig = { maxRetries: 3, baseDelayMs: 500, maxDelayMs: 10_000 }\n): Promise\u003CT> {\n  for (let attempt = 0; attempt \u003C= config.maxRetries; attempt++) {\n    const { data, error } = await operation()\n\n    if (!error) return data as T\n\n    const isRetryable =\n      error.message?.includes('rate limit') ||\n      error.message?.includes('too many requests') ||\n      error.code === '429' ||\n      error.code === 'PGRST000'  \u002F\u002F connection pool exhausted\n\n    if (!isRetryable || attempt === config.maxRetries) {\n      throw new Error(`Supabase error after ${attempt + 1} attempts: ${error.message}`)\n    }\n\n    \u002F\u002F Check Retry-After header if available\n    const retryAfter = error.details?.retryAfter\n    const delay = retryAfter\n      ? retryAfter * 1000\n      : Math.min(\n          config.baseDelayMs * Math.pow(2, attempt) + Math.random() * 200,\n          config.maxDelayMs\n        )\n\n    console.warn(`[supabase-retry] Attempt ${attempt + 1}\u002F${config.maxRetries}, waiting ${delay}ms`)\n    await new Promise((resolve) => setTimeout(resolve, delay))\n  }\n\n  throw new Error('Unreachable')\n}\n\n\u002F\u002F Usage — wraps any Supabase query\nconst users = await withRetry(() =>\n  supabase.from('users').select('id, email, created_at').eq('active', true)\n)\n```\n\n**Pagination to reduce payload and stay within limits:**\n\n```typescript\n\u002F\u002F Use .range() to paginate — reduces response size and avoids timeouts\nasync function fetchPaginated\u003CT>(\n  table: string,\n  pageSize = 100,\n  filters?: (query: any) => any\n): Promise\u003CT[]> {\n  const allRows: T[] = []\n  let from = 0\n\n  while (true) {\n    let query = supabase.from(table).select('*', { count: 'exact' })\n    if (filters) query = filters(query)\n\n    const { data, error, count } = await query.range(from, from + pageSize - 1)\n\n    if (error) throw error\n    if (!data || data.length === 0) break\n\n    allRows.push(...(data as T[]))\n    from += pageSize\n\n    \u002F\u002F Stop if we've fetched everything\n    if (count !== null && from >= count) break\n  }\n\n  return allRows\n}\n\n\u002F\u002F Usage\nconst allProducts = await fetchPaginated('products', 100, (q) =>\n  q.eq('status', 'active').order('created_at', { ascending: false })\n)\n\n\u002F\u002F Simple single-page fetch with .range()\nconst { data } = await supabase\n  .from('orders')\n  .select('id, total, status')\n  .range(0, 99)  \u002F\u002F First 100 rows (0-indexed)\n  .order('created_at', { ascending: false })\n```\n\n**Monitor usage via the Dashboard:**\n\n1. Navigate to Dashboard > Reports > API Usage\n2. Check the \"API Requests\" chart for RPM\u002FRPD trends\n3. Review \"Database\" section for connection count and pool utilization\n4. Set up alerts in Dashboard > Settings > Notifications for:\n   - API request threshold (e.g., 80% of RPM limit)\n   - Database connection saturation\n   - Storage bandwidth approaching limit\n\n**Batch operations to reduce request count:**\n\n```typescript\n\u002F\u002F BAD: N individual inserts = N requests against your RPM\n\u002F\u002F for (const item of items) await supabase.from('items').insert(item)\n\n\u002F\u002F GOOD: single batch insert (max ~1000 rows per request)\nconst { data, error } = await supabase\n  .from('items')\n  .upsert(batchOfItems, { onConflict: 'external_id' })\n  .select()\n\n\u002F\u002F For larger batches, chunk into groups\nfunction chunk\u003CT>(arr: T[], size: number): T[][] {\n  return Array.from({ length: Math.ceil(arr.length \u002F size) }, (_, i) =>\n    arr.slice(i * size, i * size + size)\n  )\n}\n\nfor (const batch of chunk(largeDataset, 500)) {\n  await withRetry(() =>\n    supabase.from('items').upsert(batch, { onConflict: 'external_id' }).select()\n  )\n}\n```\n\n## Output\n\nAfter applying this skill you will have:\n\n- Clear understanding of rate limits per tier (Free: 500 RPM \u002F 50K RPD, Pro: 5K RPM \u002F 1M RPD)\n- Connection pooling configured via Supavisor (port 6543 transaction mode for serverless)\n- Retry wrapper with exponential backoff handling 429 errors\n- Paginated queries using `.range(0, 99)` to reduce payload size\n- Batch upsert pattern reducing N requests to 1\n- Dashboard monitoring configured for API usage alerts\n\n## Error Handling\n\n| Error | Cause | Solution |\n|-------|-------|----------|\n| `429 Too Many Requests` | Exceeded RPM or RPD limit | Apply `withRetry` backoff; reduce concurrency; upgrade tier |\n| `PGRST000: could not connect` | Connection pool exhausted | Switch to Supavisor transaction mode (port 6543); reduce concurrent queries |\n| Auth `over_request_rate_limit` | Too many signups\u002Flogins from one IP | Add CAPTCHA; configure custom auth rate limits in Dashboard |\n| Storage `413 Payload Too Large` | File exceeds tier limit | Use TUS resumable upload; check tier file size limit |\n| Realtime `too_many_connections` | Concurrent connection limit reached | Unsubscribe unused channels; upgrade to Pro for 500 connections |\n| Edge Function `BOOT_ERROR` | Cold start timeout or memory exceeded | Reduce bundle size; avoid large imports at top level |\n| `pgbouncer=true` errors with Prisma | Missing connection string parameter | Append `?pgbouncer=true` to pooler connection string on port 6543 |\n\n## Examples\n\n**Example 1 — Serverless Edge Function with rate-limit-safe client:**\n\n```typescript\n\u002F\u002F supabase\u002Ffunctions\u002Fprocess-webhook\u002Findex.ts\nimport { serve } from 'https:\u002F\u002Fdeno.land\u002Fstd@0.177.0\u002Fhttp\u002Fserver.ts'\nimport { createClient } from 'https:\u002F\u002Fesm.sh\u002F@supabase\u002Fsupabase-js@2'\n\nserve(async (req) => {\n  const supabase = createClient(\n    Deno.env.get('SUPABASE_URL')!,\n    Deno.env.get('SUPABASE_SERVICE_ROLE_KEY')!\n  )\n\n  const payload = await req.json()\n\n  \u002F\u002F Batch insert webhook events (single request vs N)\n  const { error } = await supabase\n    .from('webhook_events')\n    .insert(payload.events.map((e: any) => ({\n      type: e.type,\n      data: e.data,\n      received_at: new Date().toISOString(),\n    })))\n\n  if (error) {\n    console.error('Insert failed:', error.message)\n    return new Response(JSON.stringify({ error: error.message }), { status: 500 })\n  }\n\n  return new Response(JSON.stringify({ processed: payload.events.length }), { status: 200 })\n})\n```\n\n**Example 2 — Connection string selection for different runtimes:**\n\n```bash\n# Serverless (Vercel, Netlify, Edge Functions) — transaction mode\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres.abc123:password@aws-0-us-east-1.pooler.supabase.com:6543\u002Fpostgres?pgbouncer=true\"\n\n# Long-running server (Express, Fastify) — session mode\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres.abc123:password@aws-0-us-east-1.pooler.supabase.com:5432\u002Fpostgres\"\n\n# Direct connection (migrations, schema changes only)\nDATABASE_URL=\"postgresql:\u002F\u002Fpostgres:password@db.abc123.supabase.co:5432\u002Fpostgres\"\n```\n\n## Resources\n\n- [Supabase Platform Limits & Quotas](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fplatform\u002Fgoing-into-prod#rate-limiting)\n- [Supavisor Connection Pooling](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fdatabase\u002Fconnecting-to-postgres#connection-pooler)\n- [Auth Rate Limits Configuration](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fauth\u002Fauth-rate-limits)\n- [Edge Functions Limits](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Ffunctions\u002Flimits)\n- [Storage Limits](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fstorage#limits)\n- [@supabase\u002Fsupabase-js Reference](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fjavascript\u002Fintroduction)\n\n## Next Steps\n\nFor securing your Supabase project with RLS policies and API key management, see `supabase-security-basics`. For optimizing database queries and indexing, see `supabase-performance-tuning`.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"description":32,"allowed-tools":33,"compatible-with":34},[25,26,27,28,29],"saas","supabase","rate-limiting","reliability","quotas","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Manage Supabase rate limits and quotas across all plan tiers.\nUse when hitting 429 errors, configuring connection pooling,\noptimizing API throughput, or understanding tier-specific quotas\nfor Auth, Storage, Realtime, and Edge Functions.\nTrigger: \"supabase rate limit\", \"supabase 429\", \"supabase throttle\",\n\"supabase quota\", \"supabase connection pool\", \"supabase too many requests\".\n","Read, Write, Edit, Bash, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--supabase-pack--supabase-rate-limits",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill supabase-rate-limits",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill supabase-rate-limits",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill supabase-rate-limits","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--supabase-pack--supabase-rate-limits\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]