Playcode Cloud

You describe the software.
Everything else is our problem.

Servers, database, domains, HTTPS, background jobs, backups, deploys - decided, wired, and running on a cloud we built ourselves. You talk to the AI. Your software just runs.

Start building See pricing

Playcode Cloud is included with paid plans.

yourcompany.com

HTTPS Live

Orders

Anna K.Deep clean · Sat 09:00paid
Marcus T.Office weekly · Mon 07:30paid
Lena R.Move-out clean · Thu 14:00new

Project timelinerewind restores code + files + database

1.1M+
users: 26M+
projects: Since 2016; 2
EU regions, our own cloud

Why we built it

Anyone can generate an app. The hard part is running it.

So we did the unreasonable thing: we built our own cloud. Our own machines, our own storage, our own git, our own network - every layer engineered for software that gets described into existence and has to run for years.

No hosting to pick. No database to assemble. No settings page with 400 toggles. Opinionated, end to end, ours - so it can be yours.

One machine. Your whole stack inside.

Every project gets a dedicated machine with everything a real product needs. Not a sandbox. Not a shared runtime. Yours.

production machineGermany · EU

Your app

running

Database
persistent
Files
durable storage
Background jobs
nightly digest · 02:00
WebSockets
real-time

yourcompany.com · HTTPS automatic

01
A real database
Tables, queries, transactions. Chosen, tuned, and persistent. You never install or configure one.
02
Files that persist
Uploads, assets, exports - stored durably, surviving every restart.
03
HTTPS and your domain
Certificates issued and renewed without you ever seeing them.
04
Background jobs and schedulers
Digests, reports, webhooks - on the same always-on machine as your app.
05
WebSockets and real-time
Queues, workers, live updates. A full Linux process model - it behaves like a real server because it is one.
06
Preview links
Share a live preview with anyone before you ship.
07
Integrations, wired for you
Stripe, email, Telegram, WhatsApp and more - the agent builds the integration through their APIs when you hand it the keys. You never read their docs.

Publish is one click. Underneath, it's a real pipeline.

Your dev machine and your production machine share one private repository on our own git infrastructure. Publish ships the exact commit you approved. No drift, no "works on dev" surprises.

Dev machine

where you build

commit a1f3c9

Git

your code · our infra

publish

Production

yourcompany.com

Production never sleeps. Idle machines do.

24/7
production, always on: ~1s
warm wakeups for idle dev machines: ~5-20x
faster than a cold start

You pay for production, not for idle.

Break something? Rewind the whole machine.

Code, files, and database come back together, in place, to a saved moment - in about a second. Snapshots happen automatically before risky changes, on request, and whenever you press the button.

We can promise this because we own the machine your software runs on.

Snapshot history

Add customer login14:02
New pricing page15:11
Checkout redesignbroken16:24

code + files + database · in place · ~1s

Losing a database kills a business. Here, that has to fail four different ways at once.

Your work lives in four independent layers, each further from the machine than the last.

Your appthe live machine

Live

Whole-machine snapshotson the machine
Code, files, and database, restored together in place.
manual · on request · auto before risky changes
Git historyseparate infrastructure
Every change committed. Code recoverable independently of the machine.
every change · full history
Encrypted off-site backupsseparate provider
Project history backed up nightly, encrypted, every run monitored.
nightly · point-in-time restore
Export anytimein your hands
Real code, your property. Download the whole project whenever you like.
ZIP · git pull

Four independent layers between your business and zero.

We built the parts nobody sees.

Years of infrastructure engineering run under every prompt. Not a wrapper over someone else’s cloud - our own technology, all the way down.

01
Our own cloud
Bare-metal machines in two EU regions - Germany and Finland. We run the hardware. Nobody rents it to us. And when it helps, a machine can move to the other region in seconds.
02
A dedicated machine per project
Hardware-level isolation. Your app never shares a runtime with a stranger's code.
03
A real server, not a sandbox
A full Ubuntu Linux server: open your own ports, manage processes, reach the whole internet, reconfigure what you like. Logging comes set up out of the box; our in-machine agent adds the extra powers.
04
Written in Rust
The infrastructure layer is written in Rust - we picked the most reliable, fastest tool for the job. You feel it in wake times and uptime.
05
Storage we built ourselves
A distributed storage and snapshot system, engineered in-house - the technology that makes whole-machine rewind possible. Bottomless: it grows as you write, survives crashes, and you pay for what you use.
06
Private networking, down to the DNS
Your machines talk to each other inside your workspace - never over the public internet. Even the DNS layer is ours.
07
Scale up, then out
Grow a machine's CPU and RAM when the app needs more, or add machines on the same private network when one is not enough.

Built. Building. Next.

The direction is the full cycle of a real software business: build it, run it, operate it, grow it - one chat, one runtime. Here is exactly where the line is today.

TodayNext

Manual horizontal scaling - add machines when you need them

Single-app auto-scale across machines

Two-region fleet (Germany + Finland); each app runs in one region

Multi-region failover

Our own git server - push, pull, and export anytime

Two-way GitHub mirror

Security hardening as a daily practice

SOC 2 - in progress

Who Playcode Cloud is for.

Playcode Cloud is the production runtime for software you describe to Playcode AI: business websites, MVPs, client portals, dashboards, internal tools, and small full-stack apps. One system runs the app with a database, HTTPS, custom domains, background jobs, snapshots, and rollback - no separate hosting, database, or deploy stack to assemble.

Choose it when

You want one guided system that builds AND runs the software - no vendor assembly.
The app has to outlive the demo: real users, real data, always online.
Losing data is unacceptable - you want snapshots, git history, off-site backups, and export, all included.
You are non-technical, or technical but done with DevOps chores.

Look elsewhere when

You need compliance certifications held today (SOC 2 is in progress, not held).
You want low-level infrastructure control - your own Kubernetes, Docker pipelines, or cloud account.
Large-enterprise procurement is the buyer.
You only want a code editor or playground, not a running product.

The questions builders actually ask.

Straight answers. No hand-waving.

Will my backend stay online, or does it shut down when inactive?

Production stays online 24/7. Your development machine suspends when idle and wakes in about a second when someone needs it. Nothing is lost - only the running processes pause.

Can it handle real production traffic - multiple users, concurrent requests?

Yes. Each project runs on its own dedicated machine with real TCP/UDP networking, a public domain, and automatic HTTPS - suitable for a small to mid-sized app. Need more? Add machines; they share a private network. Automatic scaling across machines is on the roadmap.

Is storage persistent? Will my database and files survive restarts and redeploys?

Yes. Databases, files, and uploads write to durable storage that survives every restart, reboot, and crash. You pay for the bytes you use, not the disk you reserve.

Can it run WebSockets, queues, and background workers?

Yes. A full Linux process model, like any real server: WebSocket servers, workers, schedulers, and the usual server frameworks.

Do you sync with GitHub?

Every project has its own repository on our git server - branches, merges, full history. Push and pull anytime, export the whole project as a ZIP. A two-way GitHub mirror is on the roadmap.

Is this a production host, or a cloud IDE for prototyping?

Both, and that's the point. One project has a development machine (browser editor, terminal, AI) and a production machine (always on, your domain, snapshots and rollback). Publish moves the exact commit from one to the other.