PocketHost enforces several limits to keep hosting fair and reliable. For trusted proxy setup and conference planning, see Trusted IPs.
PocketHost implements multiple layers of rate limiting.
Cloudflare restricts requests to 50 requests per 10 seconds per IP at the edge, before traffic reaches PocketHost infrastructure.
These are the defaults. They reset every hour. Operators can raise an instance’s caps via mothership instances.firewall (ip_hourly, instance_hourly, ip_concurrent, instance_concurrent). File routes (/api/files/...) consume less of the hourly budget than API routes. See weighted rate limits for how weighting works.
Once a request completes, the slot becomes available for new requests.
Connecting from an address on your Trusted IPs list uses the higher numbers above. Manage the list under Account → Trusted IPs.
If you make many requests from the client, use the Bottleneck NPM package to throttle efficiently.
Exceeding rate limits often indicates a coding issue. Consider JS Hooks for bulk fetching server-side instead of tight client polling.
If traffic comes from a shared server IP, see Trusted IPs or Server-Side PocketBase is an Anti-Pattern.
Every request through the PocketHost firewall (success or 429) includes X-PocketHost-RateLimit-* headers with your current budget on that edge. Inspect them with browser devtools, curl -i, or your HTTP client.
| Header | Meaning |
|---|---|
X-PocketHost-RateLimit-Ip-Hourly-Limit | Per-IP hourly cap (API-weighted; see below) |
X-PocketHost-RateLimit-Ip-Hourly-Remaining | Budget left this hour for your client IP on this instance |
X-PocketHost-RateLimit-Ip-Hourly-Reset | Unix timestamp when the per-IP hourly window resets |
X-PocketHost-RateLimit-Instance-Hourly-Limit | Per-instance hourly cap |
X-PocketHost-RateLimit-Instance-Hourly-Remaining | Budget left this hour for the instance hostname |
X-PocketHost-RateLimit-Instance-Hourly-Reset | Unix timestamp when the per-instance hourly window resets |
X-PocketHost-RateLimit-Ip-Concurrent-Limit | Max simultaneous requests from your IP on this instance |
X-PocketHost-RateLimit-Ip-Concurrent-Remaining | Concurrent slots left (while the request is in flight) |
X-PocketHost-RateLimit-Instance-Concurrent-Limit | Max simultaneous requests for the instance |
X-PocketHost-RateLimit-Instance-Concurrent-Remaining | Instance concurrent slots left |
Limit and Remaining numbers use the same API request weights as the caps above (1,000 / 10,000 per hour, etc.). /api/files/... routes consume less budget, so file-heavy traffic can show higher Remaining than a naive request count would suggest.
Example:
curl -sI "https://your-subdomain.pockethost.io/api/health" Look for the X-PocketHost-RateLimit-* lines in the response headers. On 429 Too Many Requests, the same headers reflect the bucket that blocked you, plus Retry-After.
These headers reflect the edge firewall that handled the request, not a global dashboard aggregate. Cloudflare edge limits (above) are separate and are not included in these headers.
PocketHost instances may enter hibernation during inactivity. They wake on the next request, but the first request after hibernation may be slower. See How PocketHost Works.
cronAdd and the schedule in Settings > Backups) only runs while your instance is awake. Use webhooks for scheduled work, including scheduled backups.PocketHost limits are simple: you pay per instance.
We also monitor bandwidth, storage, and CPU under fair use. We think fair means using about the same resources as the average active app on the platform. See Pricing Ethos for how we balance scale and indie-friendly hosting.
We operate under a Fair Use Policy in our Terms of Service. If usage significantly exceeds typical levels, we may contact you to discuss a resolution.
In extreme cases, if the issue cannot be resolved and it negatively impacts other users, your instance may be suspended. In severe cases, we may delete data without providing a backup. This is rare (it has only happened once due to an abusive situation).
If your plan goes down (one of your subscriptions ends, or you lower the number of instances) and you have more instances running than it now includes:
While you have more instances than your plan includes, you can’t create new ones, and only as many as your plan includes can be powered on. To change which ones run, power one off, then power another on.
If your plan ends completely, so it doesn’t include any instances, your instances stop running right away and we email you once. There’s nothing to choose, so nothing is powered off and nothing is deleted. Add instances to your plan and they start again, just as you left them.
Disk storage is everything your instances keep on PocketHost’s servers: databases, logs, pb_public, pb_hooks, backups, and file uploads stored locally. It’s one number, pooled across all of your instances.
| Plan | Disk storage |
|---|---|
| Pay Per PocketBase | 10 GB per paid instance |
| Flounder, Founder, and other legacy plans | 25 GB total |
| No paid instances | 1 GB total |
Legacy plans come with a large instance allowance (250 or more). Their storage is a flat 25 GB and doesn’t grow with the number of instances.
Files in your own S3 bucket don’t count. If you store uploads or backups in S3, they don’t use your disk storage. See S3 storage. This is the best option for large or fast-growing files such as images and media.
Static files in pb_public are welcome, and they count. Serving your frontend or a few assets from pb_public is fine; those files use your disk storage like everything else. For a large static site or a media library, a static host or CDN (such as Cloudflare Pages or Cloudflare R2) is usually faster and cheaper, and it keeps your disk storage free for your data.
Store PocketBase app data, not everything. PocketHost hosts PocketBase apps, not files in general. What you keep here should be part of a PocketBase app you run: its database, uploads, hooks, backups, and frontend. Bulk files your app doesn’t use, such as media mirrors, data dumps, or scraper output, belong with an object storage or static hosting provider. See section 6.2 of the Terms of Service.
See Account for your usage meter. Usage is measured once a day, so recent changes can take up to a day to show.
Our Terms of Service outline restrictions on prohibited content and usage. Review those guidelines to ensure your instance complies with our policies.