Deploy Remix in 60 Seconds
Remix is a full-stack React framework built on web standards. Deploy it with loaders, actions, and nested routing on a real server - no adapter juggling required.
The usual way to deploy Remix
- Choosing between Express adapter, Hono adapter, Architect adapter - each with different config requirements
- Build output differs per adapter: some produce a single server file, others need a full directory structure
- Express adapter requires manually wiring createRequestHandler and configuring static file serving
- Getting HMR and live reload working in development vs production asset paths and public directory config
- Deploying to a VPS means setting up Node.js, running remix build, and configuring PM2 to serve the right entry point
Remix is great for web-standards apps, but its adapter-based deployment adds needless complexity.
Or just run one command
What you get
Recommended plan for Remix
- 2 vCPU
- 2 GB RAM
- 25 GB storage
- HTTPS included
- Custom domain support
- SSH & web terminal access
Remix deployment notes
Express Adapter
Use @remix-run/express for the simplest deployment. InstaPods runs your server entry point (server.js or server.ts) directly with Node.
Build Output
Remix outputs to build/server and build/client. InstaPods serves static assets from build/client and runs the server bundle for SSR automatically.
Environment Variables
Access server-side env vars in loaders and actions via process.env. Set them in the InstaPods dashboard - no .env file needed on the server.
Deploy Remix in 60 seconds
One command. Real server. HTTPS included. No DevOps degree required.
Start Free