Tools
The tool stack around a Virex repo
These tools are not random extras. They become relevant at different points in the workflow: local setup, repo backup, deployment, backend wiring, and mobile continuation.
The practical order matters
Most users should not try to understand every service at once. Start with the repo, the editor, and the local run. Add deployment, backend services, or mobile tooling when the project actually needs them.
- Node.js first, because npm commands depend on it.
- VS Code next, because it is the easiest default place to open the repo and run commands.
- GitHub when you want remote backup, version history, or team collaboration.
- Vercel when a web project is ready to go live.
- Supabase when auth, database, storage, or saved user state are part of the product.
- Expo when the project is mobile and you need the native testing and continuation path.
Tool pages
Each page explains what the tool is, why a Virex user needs it, when it matters, and what to do with it first.
Recommended default editor for most Virex users.
Needed before npm install or npm run dev can work.
Keeps version history, backup, and collaboration around the repo you own.
Fast deployment path for many web-oriented Virex repos.
Practical continuation layer for auth, database, and stored app state.
The main continuation layer for Virex mobile app repos.
Real billing only when the product actually sells something.