Skip to content

Run any repo

Run a GitHub repo online. Skip the clone.

Paste a link to a public GitHub or GitLab repository. pyrovue starts it in a box of its own in the cloud, works out how to install and start it, and hands you the running app with a terminal and the files. Nothing is installed on your laptop.

How it works

From a link to a running app.

Most repos are up in about a minute. Big installs take as long as they take, and you can watch every command as it runs.

  1. 01

    Paste a link

    A repo URL, owner/name, a branch, or a pull request. GitHub and gitlab.com both work.

  2. 02

    Get a box

    A fresh Linux container with its own CPU and memory limits and its own network: 2 vCPU and 4 GB on the free plan, ready in about two seconds.

  3. 03

    It sets itself up

    pyrovue reads the package files, lockfiles, README and Dockerfile, installs what they ask for, repairs the usual failures and waits until the app answers on a port.

  4. 04

    Use the app

    A live preview on its own address, a terminal, an editor for the files and a map of the code. Share the link if you want someone else to see it.

What it runs

Most stacks need no config at all.

The setup engine reads what the repo already says about itself. When it isn't sure, Claude takes over, and what worked is saved so the next run of that commit replays it.

JavaScript and TypeScriptnpm · pnpm · yarn · Bun · Deno
Next.js, Vite, Remix, SvelteKit, Nuxt, Astro, Express and plain Node scripts. The right Node version is picked from .nvmrc, engines or the lockfile.
Pythonpip · uv · venv
Django, FastAPI, Flask, Streamlit and Gradio. Requirements files, pyproject.toml, Poetry and Pipenv are read; modules imported under another name (cv2, PIL) are installed for you.
Go, Rust, Ruby, PHP and moremise
Runtimes are fetched on demand at the version the repo asks for, including Rails and Laravel apps.
Databases and queuesPostgres · MySQL · Redis · RabbitMQ · Memcached
When a Compose file asks for one of these, pyrovue runs it inside the box and points the app at it.
Frontend plus backendtwo folders, one box
A repo with a client and an API in separate folders gets both started, the API in the background and the client in the preview.
Libraries and command-line toolsno preview needed
Projects that don't serve a page are installed and left ready in the terminal, so you can run their tests or try the CLI.

When it can't

What doesn't run, plainly.

Boxes don't run Docker inside them, so a project that only starts through containers is reproduced natively, and services pyrovue doesn't know how to run (MongoDB and Elasticsearch, for now) aren't started. There are no GPUs, so model training and CUDA code won't run either.

If a repo needs something pyrovue can't guess, like a migration before the first start or a particular folder, a pyrovue.json file at its root says exactly what to do. Every setup step is in the box's log, so when something fails you can see the command and its output.

Tell it how

One small file for the repos it can't guess.

{
  "setup": ["pnpm install", "pnpm db:migrate"],
  "start": "pnpm dev",
  "port": 3000,
  "env": { "DATABASE_URL": "file:./dev.db" }
}

The full reference, including background services for a separate API, is on the support page.

Questions

Asked often.

The Hobby plan is free with no card: one box at a time, 2 vCPU and 4 GB, and 20 box-hours a month. Pro is $14 a month for bigger boxes, three at a time and 150 box-hours.

No. Everything runs in pyrovue's cloud and you use it in the browser: the preview, the terminal and the editor.

Yes, for GitHub. Connect GitHub under My Repos and open any repository you own or collaborate on. Its box is always private, and its setup is never shared with anyone.

No. Most repos are set up by the built-in detector, and a commit that has run before replays its saved recipe. Claude only steps in for repos the detector isn't sure about, three times a month on the free plan.

You can edit files in the browser and use git in the box's terminal. Pushing to GitHub is off until you turn it on for that box.

It sleeps when nobody is watching, after 15 minutes on Hobby and an hour on Pro, and wakes when you come back. Free boxes are deleted a day after they go to sleep; the Code Map, the tour and the setup log are kept until you delete the box.

Run the repo you bookmarked and never tried.

Hobby is free and needs no card. Paste a link and your first box is up in about a minute.

See plans