Playcode Cloud
We obsess over servers, so you never have to.
Hosting for the apps you build with Playcode.
Your app gets its own computer in our cloud, with a database, file storage and HTTPS. We choose the hardware, keep it running and keep it safe. You build your business.
Cloud apps come with Pro and Max.
Every part your app needs, already connected.
Hosting has a word for every part. You don’t need the words. Here’s what each part does for your app.
- Server
- The computer your app lives on. It runs the pages, the sign-in and the work behind every button, and you never log in to it.
- Database
- Where your app keeps its records: customers, orders, bookings. SQLite from the start; Postgres and Redis when the app needs them.
- File storage
- Photos, PDFs and other uploads, on the app’s own disk next to its database, up to 200 GB.
- Background jobs
- Work your app does out of sight: a receipt, a resized photo, a nightly report. A schedule can wake the app for a job.
- Address and HTTPS
- A free address on playcode.run, or your own domain, bought here or brought along. HTTPS turns on by itself.
- Sign-up messages, password resets and receipts, sent by your app through Playcode Email. No email provider to sign up for.
- AI
- AI features for your customers through Playcode AI Gateway. No AI account or key to buy; each request uses credits.
- Secrets
- Payment keys and passwords your app needs, stored encrypted, with separate values for building and for the live app.
Domains go on your card. Computer time, email past your plan’s amount and AI requests use credits.
Pick a size, from a small rocket to a spaceport.
Start on your plan’s size. Move up or down whenever you like, in Settings or by asking Playcode AI: it tells you the new price and waits for your yes. The app restarts briefly on its new size.
Either plan can pick any size. Rates are in credits, 4 to the dollar. Disk is billed by the GB you use, 0.6 credits per GB a month, and traffic past your plan’s allowance costs 0.2 credits per GB.
Most servers bill you while you sleep. Ours sleep too.
We built our own way to put a server to sleep with its memory saved. When nobody visits, it rests and costs only its disk. When someone comes, it wakes right where it left off.
Visitors
It’s awake. You pay its size’s hourly rate.
10 minutes of quiet
It sleeps. Its processors and memory are freed, and only its disk is billed.
The next visit
It wakes from its saved memory, right where it left off.
Background work waits while it sleeps. For a bot or a job that must keep running, turn on Always on, or set a schedule that wakes the app. Settings, Computer shows what each app spent and what Always on would cost.
Timed on our production servers.
Only the first visitor after a quiet spell waits for the wake. Everyone after that reaches an awake app.
under half a second
For a sleeping server in Germany to wake and answer the first visitor.
60 to 90 ms
For an awake app to start answering, timed from Europe.
under a second
For a brand-new computer to boot.
Measured in October 2026 on our production servers. These are the platform’s times; a heavier app adds its own.
We chose the servers. You can skip this part.
Our engineers could talk about them for hours. Here’s the short version.
- Processors
- Current-generation Intel server processors.
- Memory
- Plenty of it on every server.
- Disks
- NVMe, mirrored: every write lands on two disks.
- Network
- Fast links on every server that runs apps.
- Where
- Data centers in Germany and Finland.
We run everything on these machines, so you never manage a server.
Good walls make good neighbors.
Your app shares a server with other apps, never a computer. It runs in its own Firecracker microVM, with its own Linux kernel and memory, and other projects can’t reach it.
Need your app in a particular country, or special privacy terms? Tell us what you need, and we’ll say what we can support.
Isolation alone doesn’t make an app compliant, and some services we use run in other locations.
Your customers see only what you publish.
Every Cloud app has two computers, and your changes cross from one to the other when you publish.
Development
Where you and Playcode AI build and test, with a terminal, a browser and the app’s own database. Its size: 4 CPU, 4 GB memory on Pro; 8 CPU, 16 GB memory on Max.
Production
Where your customers come. After the first publish, each one sends it only your new code; its database and uploads stay as they are.
Once a task has started, you can close your laptop: Playcode AI keeps working on the development computer.
Five safety nets under your live app.
- Before each publish
- Production saves a checkpoint of itself. The last 10 are kept.
- After each publish
- A check makes sure the app answers. If the publish fails, the old code comes back by itself.
- Any time
- Each computer keeps up to 20 checkpoints that you or Playcode AI save. A restore brings back the code, the files and the database together.
- Every night
- Your code, copied to our own Git server at each publish, goes into an encrypted backup off site.
- When something breaks
- Alerts reach our team, and a person helps you look into it.
A failed publish brings back the old code, but database changes it already made stay. A restore can’t be undone, takes the app offline while it runs and leaves secrets as they are. The nightly backup holds your code, not your database.
Our engineers get the alerts. You get your evenings back.
We run the servers, the network and the disks under your app, and their alerts come to our team, not to you.
When your live app misbehaves, ask Playcode AI: it reads the logs, finds the cause and tells you what it found, and it asks before it changes anything live. When a problem gets past it, a person on our team looks into it with you.
No response time is promised.
What Pro and Max give your Cloud apps.
- Price
- Pro $19 a month. Max from $100 a month.
- Credits each month
- Pro 76. Max from 400.
- Cloud apps per workspace
- Pro 3. Max 10.
- Starting size
- Pro M. Max L. Either can move to any size.
- Computer to build on
- Pro 4 CPU, 4 GB memory. Max 8 CPU, 16 GB memory.
- Traffic included
- Pro 100 GB a month. Max 1,000 GB a month. Shared by the workspace’s apps.
- App email included
- Pro 500 recipients each billing cycle. Max 2,000.
- People
- Up to 25 per workspace, each a Viewer, Editor or Admin.
Credits pay for AI work and Cloud running costs alike. Free has no Cloud apps.
Your code can leave with you.
Download the whole project as one ZIP, with a guide to running it somewhere else. Secrets and live data stay out of it, so moving a running app also means moving those.
The full spec sheet.
You don’t need this table. Your developer friend will love it.
- Computers
- Two per app: development, where you and Playcode AI build, and production, which serves the published app.
- Production sizes
- S, M, L, XL and 2XL, from 1 vCPU and 1 GB of memory up to 8 vCPUs and 16 GB of memory. Pro apps start on M, Max apps on L. The app restarts when the size changes.
- Development computer
- 4 CPU, 4 GB memory on Pro; 8 CPU, 16 GB memory on Max.
- Sleep and wake
- Sleeps after 10 minutes of quiet, its memory saved; a visit wakes it in under half a second in Germany and about 1.4 seconds in Finland. Always on and wake schedules when you need them.
- Servers
- Current-generation Intel server processors, mirrored NVMe disks and fast network links, in Germany and Finland.
- Isolation
- Firecracker microVMs, each with its own kernel. Development and production on separate private networks; projects can’t reach each other.
- Disk
- Up to 200 GB for production, billed for the gigabytes stored.
- The app
- Astro and React for the pages, NestJS for the server, Prisma for the database. SQLite to start; Postgres and Redis on request. Sign-in and email templates built in.
- Background jobs
- Run inside the app. A wake schedule runs jobs at set times; while the app sleeps, they wait.
- Tools
- Node, Python, ffmpeg, PDF text tools and a Chromium browser on the development computer. Playcode AI installs more when a job needs them.
- Publishing
- A checkpoint first, then the code, the build and a check that the address answers. The previous code comes back if the new version fails. Live data stays.
- Saved points
- 20 per computer, plus the 10 latest from before publishing. Code, packages, database and files restore together.
- Code history
- On a Git server we run, at each publish, with an encrypted backup every night to a separate location. The database isn’t in that backup.
- Logs
- Up to 32 MB per computer, in memory; a restart clears them. A build log for every publish.
- Secrets
- Encrypted, with separate values for development and production; up to 64 in each.
- Terminal
- On both computers, up to 8 sessions each.
- Address
- A free name on playcode.run plus up to 5 more, or your own domain with HTTPS.
- Playcode Email: 500 recipients each billing cycle on Pro and 2,000 on Max, then credits. It sends; it hosts no inbox.
- AI
- Playcode AI Gateway: Claude and other models, no keys to buy, credits at each model’s own rate.
- Traffic
- 100 GB a month on Pro and 1,000 GB a month on Max, per workspace; past it, credits per gigabyte.
- Team
- Viewer, Editor and Admin; up to 25 members per workspace.
- Export
- A ZIP of the whole project with a guide. Secrets, data, uploads and installed packages stay out. Git from the terminal.
- People
- Alerts reach our team. A person looks into technical problems with you; no response time is promised.
Limits change; the docs list the current ones. Read the Cloud docs
What people ask before they publish.
Do I need to know how servers work?
No. That’s our job. We run the computers and the network under your app, and Playcode AI sets up what your app needs on them. You decide what to build, when to publish and how big its computer is.
Do I need Cloud for a simple website?
No. A site with no sign-in or stored data can publish as a static site on any plan, Free included, at an address on playcode.site. Cloud is for apps with a server, a database and stored files.
What if a crowd shows up at once?
Your app serves them from the size you picked. If it starts to struggle, move it up a size in Settings or ask Playcode AI, and it restarts on the bigger computer. It doesn’t resize by itself.
What does running it cost?
Credits for the hours production is awake, at its size’s rate, plus its disk and any traffic past your plan’s allowance. While it sleeps, only the disk counts.
What if my credits run out?
We email the workspace owner. The app keeps running for 72 hours, then stops, and starts again once the balance is above zero. Its AI requests stop at once, and email past your plan’s allowance is held, not sent.
Is my data backed up?
Production saves a checkpoint, database and files included, before every publish, and you or Playcode AI can save one before any change. Your code is also backed up every night, off site. The database isn’t in that backup, so save a checkpoint before a big change.
Where does my data live?
On your app’s computers, in Finland or Germany. AI providers, the network in front of the servers and our off-site code backups use other locations; the Privacy Policy lists them.
What about GDPR?
Tell us what your project needs, and we’ll go through the setup and the data-processing terms with you. Isolation keeps projects apart, but how your app handles personal data is still part of the work.
We sweat the servers. You build the business.
Build your app with Playcode AI, publish it here, and change its size whenever your customers ask for more.
