Custom Domains
Using your own domain with your RubyOnVibes app.
Your App Is Already Live
Every RubyOnVibes app runs at https://your-app-name.fly.dev from the moment you create it. No setup, no config — it just works.
Using the Platform as Production
For personal tools, internal apps, and projects where you're the main user, the platform works great as your production environment. You get a lot for free:
- Zero config — your app is deployed and running automatically
- Auto-deploy — every code change goes live within seconds
- Auto-recovery — if something breaks, Ada diagnoses and fixes it
- AI-assisted development — build and iterate with Ada's help, live
Things to know
- Single server — your app runs on one machine. Horizontal scaling isn't available on the platform (yet).
- Preview URL can change — if you ever need to use emergency revert & rebuild, your app gets a new
*.fly.devURL. This is not very common, but it can happen, especially if your context is management practices are still at an early stage. - Shared environment — development and production are the same environment. If you're actively building while others are using the app, they'll see changes in real time.
- Data lives on the server — by default, your database (SQLite) and uploaded files are stored on the server's disk. If you ever need emergency revert & rebuild, that data resets. For production use with real data, we recommend using an external database like Supabase (PostgreSQL) and an external file storage service like Amazon S3 — that way your data is safe no matter what happens to the app.
For many use cases — personal projects, MVPs, tools you use yourself — these trade-offs are totally fine. And if you set up Supabase + S3, the platform becomes durable as a production environment.
Custom Domains
Custom domains on platform-hosted apps aren't officially supported yet. We plan to add stable custom domain support in the future.
In the meantime, we don't recommend pointing a DNS record (like a CNAME) at your *.fly.dev URL. That URL can change after an emergency revert & rebuild, which would break your domain.
When You Need a Custom Domain Now
The recommended path is to deploy your app to your own infrastructure:
- Sync your code to GitHub — follow the steps in Connect to GitHub
- Deploy to a hosting provider — your app ships with a ready-to-use
render.yamland step-by-step deployment guides in thedocs/deployment/folder (visible in the code editor). Render, Railway, Heroku, AWS, or any Docker host will work. - Point your domain at that production deploy — your hosting provider will give you stable DNS instructions.
Best of Both Worlds
You can keep building on RubyOnVibes and sync changes to GitHub whenever you're ready. Your production deploy stays stable with its own domain, while you continue using the platform for AI-assisted development.
This gives you the best of both worlds: fast iteration with Ada on the platform, and a rock-solid production setup with your own domain.