Platform
Plans, limits and billing
What Free and Pro include, how credits are spent, and what happens when they run out.
Plans
| Free | Pro | |
|---|---|---|
| Projects | 2 | 10 |
| Database size | 500 MB | 10 GB |
| Database memory and CPU | 128 MB, half a CPU, shared server | 256 MB, 1 CPU, own container |
| Storage per project | 500 MB | 50 GB |
| Redis memory | 32 MB | 256 MB |
| Registered auth users per project | 10,000 | 50,000 |
| Hosted apps per project | 1, Micro size, sleeps when idle | 5, any size, optionally always on |
| App disk | 1 GB | 5 GB |
| Backup retention | Up to 7 days | Up to 30 days |
| Idle databases | Stopped after 6 hours with no connections | Always on |
| Monthly plan credits | $0 | $20 |
Credits
You pay for what runs, from prepaid credits in US dollars. Usage spends plan credits first, then free credits, then paid credits.
| Credits | Added | Expire |
|---|---|---|
| Plan | $20 at the start of each month on Pro | End of that month |
| Free | $10 once at signup | 90 days later |
| Paid | Added by the platform operator | Never |
Your balance is shown at the top of the dashboard, and the Credits & Billing page lists every charge.
What costs money
| Meter | Charged |
|---|---|
| Postgres compute | By the hour while running: $0.001 per hour for a Free database on the shared server (about $0.73 a month), $0.014 per hour for a Pro container |
| Postgres disk | $0.40 per GB-month above the first 1 GB |
| Redis compute | $0.002 per hour on Free and $0.012 per hour on Pro |
| Storage | $0.08 per GB-month of bucket size |
| Backups | $0.08 per GB-month of finished backups |
| Auth | First 10,000 monthly active users per project free on both plans, then $0.003 per additional active user |
| App compute | By the hour while running, by size: $0.004 (Micro), $0.008 (Small), $0.016 (Medium) or $0.032 (Large). Nothing while asleep or stopped |
Prices come from the platform's configuration and may change. The Usage tab on each project shows the current numbers for that project. A deploy needs one day of that service's cost in credits.
When credits run out
- At zero, a 3-day grace period starts. Services keep running, but you cannot deploy or wake anything new.
- After the grace period (or once the balance reaches -$5), databases, Redis and apps are stopped and buckets made read-only where supported. Paused accounts are not charged.
- Nothing is deleted. Add credits and everything starts again after the next hourly meter run. Apps that are not always on wake on their next request instead.
Size limits
A usage check records each database and bucket size. Going over a limit triggers a warning. After 3 days over, the database becomes read-only and the bucket stops accepting uploads. Delete data or upgrade to bring it back.
Creating projects, deploying, revealing secrets, resetting, waking, backing up and restoring are rate limited per user. If you see a rate limit message, wait for the window to pass.
Use with AI
Ask an agent to estimate what your app will cost, or to keep it inside the plan limits.
- 1
Open a terminal in your app's folder and start Claude Code.
claude
- 2
Paste the prompt below and press Enter. Approve the file edits and commands it asks about.
- 3
Optional: save a short note about CloudHike.dev in CLAUDE.md so every session knows about it.
Read https://cloudhike.dev/docs/md/plans-and-billing, then review how this app uses CloudHike.dev. Estimate roughly what it would cost per month on the Free plan and on Pro, and point out anything that could push it past a limit (database size, storage size, Redis memory, connection count, number of auth users). Suggest changes, but do not edit any files.
Replace the placeholders in <angle brackets> before sending. Always review what the agent changes.