How to Export Your App from Replit
Replit's download button gets you halfway there. Here's what comes next: the gotchas, the checklist, and four paths to production hosting.
What Stays Behind When You Export
Replit makes exporting your code simple: three-dot menu, download as ZIP. But the docs stop there.
What they don't tell you: your database doesn't export. Your secrets don't export. Your integrations don't export. Your auth doesn't port.
This is not Replit's fault. Any platform stores user data, API keys, and authentication separately from code. But it means export is 60% of the job—reconfiguration is the other 40%.
Here's what actually exports:
- All your project files (code, assets, package.json)
- Git history (if you use GitHub sync)
Here's what doesn't:
- Database data (stored in Replit's App Storage, not in your repo)
- Environment variables and secrets (kept separately for security)
- Integrations (email, image generation, AI APIs tied to Replit)
- Authentication (if you built on Replit's auth, not on standard OAuth/JWT)
Once you know this, export is straightforward. And if your app is simple—no database, no user accounts—you're done in 2–4 hours.
Step-by-Step Export Checklist
Follow this before you click download. It takes an hour and saves days of debugging.
Backup your data
Export your database from Replit App Storage. Write down every environment variable. Screenshot your secrets. This is your insurance policy.
Export your code
Two methods: ZIP download (three-dot menu on Files → Download as zip) or GitHub sync (Git pane → Connect GitHub → Push to repo). GitHub is safer for large projects.
Test locally
Unzip, run npm install (or pip install / bundle, etc.). Make sure your app starts locally before you commit. This catches missing dependencies now, not in production.
Document dependencies
Verify package.json lists all your packages. Check for any Replit-specific imports or SDK calls that won't work outside Replit. Replace them with standard alternatives (e.g., Supabase for auth instead of Replit auth).
Choose a host and deploy
Push to GitHub. Pick your hosting destination. Follow their docs to connect your repo and set environment variables. Most platforms auto-deploy on git push.
Where to Host After Export
You've exported your code. Now: where does it run?
Path 1: Northflank (Popular with Enterprise Teams)
If you want managed infrastructure with databases included, Northflank is the most mentioned choice in production today.
Best for: Full-stack apps with PostgreSQL/Redis, teams that want to stay on a platform.
Cost: Entry is around €20 per month for shared CPU; popular production tier around €24 per month for dedicated resources. Additional charges for CPU, memory overage, and network traffic. Free tier available for low-traffic projects.
Setup time: 2–4 hours (connect GitHub, configure environment, add database).
Lock-in risk: Moderate. Your app runs in their containers. Export is possible but you're still on their platform.
Path 2: Railway (Usage-Based, Fast Deploys)
Railway removes the build and deploy friction. Connect GitHub, it runs.
Best for: Rapid prototyping, teams that move fast and don't mind variable costs.
Cost: Usage-based. Can be cheaper than fixed plans for light traffic, expensive if you scale. Budget €5–€100+/mo depending on load.
Setup time: 1–2 hours. Fastest of the four.
Lock-in risk: Moderate-high. Usage-based pricing can surprise you. Switching costs time, not money.
Path 3: Coolify (Self-Hosted, Zero Platform Fees)
If you have DevOps skills and want maximum control: rent a VPS (Hetzner, DigitalOcean, Linode) and run Coolify on top. You own everything.
Best for: Teams with DevOps experience, cost-sensitive projects, EU data residency requirements.
Cost: Infrastructure only. €2.99–€10/mo for a basic VPS. Coolify itself is free. Total cost well under €20/mo. Scaling requires you to buy bigger servers or add more nodes.
Setup time: 4–8 hours if you're new to DevOps. 1 hour if you've done this before.
Lock-in risk: Zero. You own the servers. Portability is absolute.
Maintenance cost: You handle updates, backups, security patches. This is real work.
Path 4: Ship (Managed Hosting with GDPR Compliance)
Ship is the middle path: managed infrastructure without the enterprise pricing or complexity.
Best for: EU-first teams, compliance-conscious companies, teams that want managed + flat pricing.
Cost: Flat pricing model (details available from Ship team). No surprise usage charges.
Setup time: 2–4 hours (similar to Northflank).
Lock-in risk: Moderate. Your app is containerized. Germany-based infrastructure means GDPR compliance out of the box.
Advantage: Opsily team handles platform updates, scaling, monitoring. You focus on your app.
Simple apps export and deploy in one afternoon
No database, no complex auth, no custom integrations: export in 1 hour, test locally in 30 minutes, deploy by end of day. Apps with databases or user authentication take 4–8 hours.
The GDPR Angle: Why EU Teams Export First
Replit is US-based. Your data lives in US data centers. If you're in the EU and serve EU customers, this is a problem waiting to happen.
GDPR requires data residency: customer data must stay in the EU. You can use a US platform if you have proper data processing agreements, but it adds complexity and legal cost.
Alternative: host in Europe from the start. Opsily runs servers in Germany. Many of the hosting options after export (Northflank supports EU regions, Render has EU plans, Coolify on a Hetzner VPS) can keep your data in the EU natively.
Exporting now—while your app is small—means compliance by default later, not a scramble when you get your first customer.
Why Ship After Export
Once you've exported and tested locally, Ship is the no-friction way to go live.
Managed Infrastructure
Ship handles deployment, scaling, and monitoring. Push to GitHub, your app updates automatically. No DevOps work required. Unlike self-hosting, you don't maintain servers.
GDPR Compliant by Default
Your app runs on German infrastructure with data residency built in. No separate compliance checklist. No data processing agreements to negotiate. Ship is GDPR-by-default.
Flat Pricing, No Surprises
Fixed monthly cost. No usage charges, no surprise bills when traffic spikes. You know your hosting cost upfront, like rent instead of a utility bill.
FAQ
Yes—your code, absolutely. Your database, secrets, and integrations, no. When we say export, we mean get your source code out as a ZIP or push to GitHub. You can run it locally right after. But reconfiguring the database connection, API keys, and auth will take time. If your app is simple, the export itself is 30 minutes. If you have a database and user accounts, plan 4–8 hours total.
Ready to move your app to production?
After export, Ship handles the rest: deployment, scaling, monitoring, and GDPR compliance. No DevOps work required.