Moving off a managed PaaS
If the platform you run on is being retired, one question decides everything: does what you run today run here? This page answers it stack by stack, including the cases where the answer is no.
What runs on Open Source Cloud today
Checked against the live service catalog. Launch any of these from the catalog, from an API call, or from an AI agent over MCP.
| What you run today | On Open Source Cloud | How the move works |
|---|---|---|
| MySQL or MariaDB | MariaDB | Standard connection string. Import with mysqldump. |
| PostgreSQL | PostgreSQL | Standard connection string. Import with pg_dump and pg_restore. |
| Redis | Valkey | Speaks the Redis protocol, so it is a drop-in. Point your client at the new host. |
| ClickHouse | ClickHouse Server | Both the native protocol and the HTTP interface are available. |
| CouchDB | Apache CouchDB | Replicate straight from your existing instance. |
| Neo4j | Neo4j | Restore from a dump. |
| Vector search | Postgres Vector | pgvector on Postgres, so one database serves both jobs. |
| Node.js application | My Apps | Connect a Git repo. No Dockerfile and no build config required. |
| Python application | Python Runner | FastAPI and Flask are detected from the repository. |
| Static site | My Pages | One command. No repository and no server to run. |
What does not run here today
Stated plainly, because discovering it after you have moved is worse. If your workload is on this list, this is not the right destination for it today.
- PHP applications. There is no PHP runtime in the catalog today.
- Java and servlet containers. There is no Java runtime in the catalog today.
- MongoDB. Not in the catalog. The document database here is CouchDB, which is not wire-compatible, so this is a rewrite rather than a move.
- Your own container image. Custom applications run as Node.js, Python or WebAssembly. Bringing an arbitrary image is not a self-service option yet.
For those workloads a container platform or plain infrastructure is the better destination, and your current provider can usually route you there. We would rather say so now than take the signup.
How the move works
Check your stack
Read the two tables above. They are the honest answer, and the second one matters more than the first.
Launch what you need
A free account includes 100 tokens, once. That is enough to launch a service and watch it run. Keeping it running continuously needs a paid plan.
Import, then cut over
Every service exposes standard connection details, so imports use the tools you already use. Move the data, point your application at the new host, done.
What you get
- Every service is open source. Where we run a modified build, we publish our changes and link the exact source.
- Your application code stays in a Git repository you control, so the export route is the same repository you deployed from.
- 188+ services, launched from the web, from an API, or from an AI agent over MCP.
- No proprietary runtime to rewrite against, so moving on later to another host or your own hardware stays a real option.
Find out whether your stack runs here
A free account takes an email address and no credit card. If the tables above say your workload does not fit, tell us what you run and we will say where it should go instead.