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 | Unlimited |
| Database size | 500 MB | Unlimited, billed per GB above 1 GB |
| Database memory and CPU | 128 MB, half a CPU, shared server | Own container: Standard (256 MB, 1 CPU) by default, resizable from 256 MB to 4 GB |
| Storage per project | 500 MB | Unlimited, billed per GB |
| Redis memory | 32 MB | 256 MB by default, resizable live from 256 MB to 4 GB |
| Registered auth users per project | 10,000 | Unlimited |
| Monthly active auth users included per project | 10,000 | 10,000 |
| Hosted apps per project (coming soon) | 2, Micro size, sleeps when idle | Unlimited, any size, optionally always on |
| App disk | 1 GB per app | Unlimited, billed per GB above 1 GB |
| 100 a day and 3,000 a month, free | No daily or monthly limit, 3,000 a month per project included | |
| Background jobs | 500 runs a day, free | No daily limit, 50,000 run-seconds a month per project included |
| 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 | $10 |
Pro is billed by usage: where the table says unlimited, you pay for what you use instead of hitting a limit. Two guards stand behind that: an account can hold up to 100 projects and a project up to 50 apps before support has to raise it, and a single database, bucket or app volume past the platform's safety ceiling (hundreds of GB) blocks new deploys until it is back under or support raises it. A monthly spend cap (below) is yours to set.
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 | $10 with each paid Pro invoice | End of that billing period |
| Free | $10 once at signup, for eligible accounts | 90 days later |
| Paid | Bought on the Credits & Billing page in packs of $10, $25, $50, $100, with an active Pro subscription | Never |
Your balance is shown at the top of the dashboard, and the Credits & Billing page lists every charge.
What costs money
| Meter | Charged |
|---|---|
| Database compute | By the hour while running: $0.001 per hour for a Free database on the shared server (about $0.73 a month), and for a Pro container by its size, from $0.0125 per hour (Micro) and $0.014 (Standard, the default) to $0.196 (XL). Sizes are listed on the Postgres page. |
| Database disk | $0.40 per GB-month above the first 1 GB |
| Redis compute | $0.002 per hour on Free (32 MB), and on Pro by size, from $0.012 per hour (256 MB, the default) to $0.193 (4 GB). Sizes are listed on the Redis page. |
| Stored files | $0.08 per GB-month of bucket size |
| Backups | $0.08 per GB-month of finished backups |
| Auth active users | 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), $0.032 (Large). Nothing while asleep or stopped |
| App disk | Pro: $0.40 per GB-month of an app's volume above the first 1 GB. Free volumes are capped at 1 GB instead |
| Emails | Free on Free, within its limits. Pro: 3,000 emails a month per project included, then $0.40 per 1,000 (each recipient counts as one) |
| Job run time | Free on Free, within its limits. Pro: 50,000 run-seconds a month per project included, then $0.01 per 1,000 run-seconds |
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 24 hours 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 your credit limit, databases, Redis and apps are stopped and buckets made read-only where supported. The credit limit is $5 below zero on Free and in a Pro subscription's first billing period, and $50 once a Pro renewal has been paid. 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.
Spending controls
Under Settings you can set a monthly spend cap. We email you at 50% and 80% of it; when this month's usage reaches it, databases, Redis and apps pause and buckets become read-only until the next month (UTC) or until you raise the cap. Nothing is deleted. Without a cap, you can set an alert amount instead, which sends one email a month.
The Usage and Credits & Billing pages show what you have spent this month and a forecast for the whole month.
Size limits
A usage check records each database and bucket size. On Free, 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. Pro databases, buckets and app volumes have no size limit and are never paused for size, except a Pro database still on the shared server, which keeps the Free limit until you move it to its own container.
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 Free limit (database size, storage size, Redis memory, connection count, number of auth users, emails or job runs a day) or make the Pro bill grow quickly. Suggest changes, but do not edit any files.
Replace the placeholders in <angle brackets> before sending. Always review what the agent changes.
