Skip to content
All Use Cases
Platform Migration

Migrate from Legacy PaaS

Move from maintenance-mode platforms to a modern, actively-developed alternative with zero vendor lock-in

What You Get

Active development with regular feature releases
Generous free tier to start without risk
Zero vendor lock-in with open source standards
Growing community and ecosystem

Legacy vs. Modern PaaS

See how actively-developed platforms compare to those in maintenance mode

Legacy PaaS

Platforms in Maintenance Mode

Limited or no free tier
Reduced feature development
Proprietary APIs and lock-in
Uncertain long-term roadmap
Declining community activity

Open Source Cloud

Active Development

Free tier: 100 tokens to start
Regular updates and new services
Open source, no lock-in
Clear roadmap and transparency
Thriving builder community

Migration Guide

Move your workloads with confidence

Follow these steps to migrate your applications from legacy platforms to Open Source Cloud.

1

Audit Your Current Stack

Document your databases, services, environment variables, and dependencies. List all add-ons and integrations.

2

Create OSC Account

Sign up for free at app.osaas.io. No credit card required to start.

3

Provision Services

Use our MCP integration with your AI agent to set up databases, caches, and storage. Or browse the catalog and deploy manually.

4

Deploy Your Application

Push your code as a hosted application. Configure environment variables and custom domains.

5

Test Thoroughly

Run your test suite against the new infrastructure. Verify all integrations work as expected.

6

Switch DNS

Update DNS records to point to your new deployment. Keep the old platform running until migration is verified.

Common Stack Migrations

Typical configurations and their OSC equivalents

Pricing Comparison

Typical workload costs

Compare pricing for a typical production workload: 1 web app, 1 PostgreSQL database, 1 Redis cache, and regular traffic.

Legacy Platform: ~$50-100/month (limited free tier)

OSC Personal Plan: €15/month (plus generous free tier)

Save up to 70% on infrastructure costs

Exact costs depend on usage patterns. OSC charges only for active services with transparent, predictable pricing.

Why Developers Are Migrating

No Vendor Lock-in

Built entirely on open source. Your data, your apps, your control. Export and migrate anytime with standard protocols.

Active Development

Regular feature releases, new services added monthly, responsive to community feedback. Not in maintenance mode.

AI-Native Platform

Use MCP to let your AI agent handle infrastructure. Deploy databases, configure services via natural language.

Transparent Pricing

No surprise bills. Clear per-service pricing, generous free tier, no hidden costs or premium add-ons.

Migration patterns

Common migration paths developers ask about when moving to Open Source Cloud.

How do I migrate from a proprietary document database to Open Source Cloud?

Document-database BaaS platforms typically export data via vendor CLI tools that produce LevelDB or JSON output. Download the export, then re-shape the documents into a relational schema for managed PostgreSQL on Open Source Cloud. Replace the bundled authentication service with SuperTokens or OpenAuth, both available in the catalog with self-hosted user data. File storage objects move to S3-compatible MinIO with a standard `aws s3 sync`. Document and relational stores have different shapes, so the data step is a re-shape, not a one-to-one dump.

How do I migrate from a proprietary edge-runtime platform to Open Source Cloud?

Connect your GitHub repository through Open Source Cloud My Apps, set environment variables in the dashboard, and add your custom domain. Builds run on standard Node tooling and the runtime is a published Docker image you can inspect or run locally. Vendor key-value stores map to Valkey, vendor Postgres to managed PostgreSQL, blob storage to MinIO, all reached through standard connection strings. Edge runtimes and edge middleware are vendor-specific; if your app uses them heavily, plan to refactor those routes to standard Node handlers before cutover.

How do I migrate from a single-vendor Postgres + Auth + Storage bundle to Open Source Cloud?

Tables move with pg_dump, users move to Keycloak with their bcrypt passwords kept and files move to MinIO, with the full steps on a page of their own.

Moving a hosted Postgres backend, step by step

Ready to migrate?

Join developers moving to a platform designed for the future, not the past.

Basic tier free, no credit card required.