Deploy
From generated repo to live project
Deployment should feel like a normal continuation step after the repo is understood, not like a hidden mystery. Virex gives you the repo. You decide where it lives, where it runs, and which services it connects to.
A practical deployment sequence
Most users should move through a simple order: inspect, run, store, connect, deploy.
- Open the generated repo locally and understand the baseline before you connect hosting.
- Use GitHub when you want version history, backup, and a clean source-of-truth repo.
- Use Vercel for many web builds when you want the fastest route from repo to live URL.
- Add project-specific services and environment variables only after the repo structure is understood.
- Use Expo as the continuation layer for mobile repos before you think about deeper release preparation.
Ownership comes first
The point of deployment is not to hand the project back to another black box. The point is to take the repo you own and make it live through a path you understand.
What Virex is not trying to do
Virex is not built around forced hosting. Managed convenience can exist later, but the core direction is still repo ownership, self-hosting flexibility, and standard deployment paths.
Useful related docs
Use these pages when you are deciding how the repo should continue after generation.