Account
Plans and limits
Every workspace is on a plan. A new workspace starts on Free, a 14-day trial; paid plans are coming.
| Free | Starter | Pro | Team | |
|---|---|---|---|---|
| Apps | 1 | 2 | 10 | 25 |
| How long | 14 days | as long as you pay | ||
| Members (counting open invites) | 1 | 3 | 5 | 10 |
| Databases | 1 | 1 | 3 | 10 |
| Disk per database | 1 GB | 5 GB | 15 GB | 40 GB |
| App storage, shared by the apps | 1 GB | 5 GB | 15 GB | 40 GB |
| Memory for all apps together | 512 MB | 1 GB | 3 GB | 6 GB |
| Memory per app, at most | 512 MB | 512 MB | 1 GB | 2 GB |
| CPU per app | 0.5 vCPU | 0.5 vCPU | 1 vCPU | 1 vCPU |
CPU figures are what an app is guaranteed. When the server has CPU to spare, an app may use up to 2 vCPU, so it starts and handles bursts faster; when it hasn't, CPU is shared in proportion to the plans.
Memory
A plan's memory is shared by the workspace's apps. Each app has its own size, chosen under Settings › Memory on its page: 256 MB, 512 MB, 1 GB or 2 GB, up to the plan's most per app. All the apps' sizes together, stopped apps included, fit in the plan's memory. Databases have their own memory and don't count.
- A new app gets 512 MB, or less if that's all that's left (at least 256 MB). A static site always has 128 MB. When nothing is left, lower another app's memory or delete one first.
- Changing the size is for workspace owners and admins. A running app is redeployed with the new size, with no downtime.
- An app that needs more than its size is stopped by the system and started again, and shows as crashing. Check its peak on Monitoring before lowering it. Java apps size their heap from the container's memory.
- On a smaller plan, an app bigger than the plan's most per app gets that size on its next deploy. If the apps still need more than the plan's memory, only the ones that fit can deploy or start, and 7 days later the others are stopped (never deleted), as for any other limit.
The free trial
Free is a 14-day trial, with no card to enter. The workspace shows how many days are left.
- 3 days before the end, the workspace's owners get an email.
- When the trial ends, its apps and databases stop, and nothing new can be deployed or started. Nothing is deleted yet: variables, domains and backups stay, and you can download database backups.
- 14 days later, the apps, databases and their backups are deleted, and this can't be undone. Owners get an email 2 days before. Your account and the workspace stay, so you can deploy again on a paid plan.
To keep going after the trial, choose a plan on the workspace's Usage & billing page. While paid plans are being set up, write to support@oceanlaunch.cloud and we'll move your workspace across.
On every plan
| What | Limit |
|---|---|
| Memory and CPU per static site | 128 MB · 0.25 vCPU |
| Memory and CPU per database | 256 MB · 0.25 vCPU |
| Files an app writes outside its storage | 2 GB (they start fresh on each deploy) |
| Upload (JAR, WAR or site) | 150 MB |
| Custom domains per app | 3, each with HTTPS |
| Variables per app | 100, each up to 32 KB |
| Database backups | every night, last 7 kept |
| Workspaces you own | 3 |
| Build time | 30 minutes |
| Deployments per workspace | 60 an hour, all apps together (pushes included) |
Disk
Disk limits are hard: past one, writes fail with "disk full" (No space left on device) in that app or
database only, and nothing else on the server is affected.
- A database may hold its plan's size of data (backups don't count). Its page shows how much it uses; at 90% the workspace's owners and admins get an email. A full database refuses new data until you delete some or move to a bigger plan. A smaller plan can't be chosen while a database uses more than that plan allows.
- An app may write 2 GB of files outside its storage: temporary files, caches, logs written to files. They're wiped on every deploy, so a redeploy frees them. Files to keep belong in the app's storage (Settings › Storage on the app's page), which has its own size.
- An app's
/tmpis kept in memory (unless the image puts files there itself), so what it writes there counts towards the app's memory, not its disk. Large temporary files belong elsewhere, such as/var/tmpor the app's storage.
See Pricing for prices. When a limit is reached, the portal says so: delete something, or ask us about a bigger plan at support@oceanlaunch.cloud.