Skip to content

Support

Stuck? Write to us.

Email hello@pyrovue.com with the link to your box and what you expected. We answer within two working days. Security problems go to the same address; the security page says what to include.

Common questions

Before you write.

The answers come from the same numbers pyrovue enforces.

Open the box and read the setup log: each step shows what ran and what failed. Rebuild from the box's menu to try again. When your plan's Claude setups are used up for the month, the detector works alone; the line under the repo field on your dashboard shows how many are left.

If it's your repository, a pyrovue.json tells pyrovue exactly how to install and start it. Still stuck? Email hello@pyrovue.com with the link to the box.

A box with no viewer goes to sleep after 15 minutes on Hobby, 1 hour on Pro and 2 hours on Team. Its container is deleted 24 hours after it sleeps on Hobby and 7 days on Pro and Team. Its tour, Code Map and setup log stay until you delete the box, and opening it sets it up again.

The box is removed for good: its container with every file and dependency, its setup log, its guided tour and its Code Map. Its share link and preview address stop working at once, and anyone watching it is disconnected. Box-hours and Claude setups the box already used this month still count. The repo's saved recipe is kept, so a fresh box from the same repo sets up quickly. A sleeping box is different: it keeps its tour, map and log, and only its container is removed after 24 hours on Hobby or 7 days on Pro and Team. Waking it sets it up again.

1 on Hobby, 3 on Pro and 5 per seat on Team. Put one to sleep to start another. The comparison has every limit.

Your own GitHub ones, yes: open My Repos, connect GitHub, and open any repository there. Its box is always private and its setup is never shared. Anyone's public repositories on github.com and gitlab.com run too, branches and GitHub pull requests included. Private GitLab projects and repositories you can't see on GitHub aren't supported yet.

Only when Claude does the setup: the repository's file list, key files and command output go to Anthropic's API. Setups by the built-in detector and replays of a saved recipe send nothing to any model. The security page and the privacy policy have the details.

Settings, Plan & usage, Manage billing. Your plan runs to the end of the period you've paid for, then the account moves to Hobby. For a refund, email hello@pyrovue.com from the address on your account within 14 days of the charge.

Settings, Profile, Delete account: type your email address, and your password if the account has one. A paid plan must be cancelled first. Your boxes are removed and your record deleted at once; backups age out within 14 days, as the privacy policy says.

Email hello@pyrovue.com first, with what you found and how to reproduce it. What is in scope is on the security page.

  • Ctrl C stops the running command (copies instead when text is selected).
  • Ctrl D leaves a node, python or nested shell prompt.
  • q leaves less, top and paged git output.
  • Ctrl X leaves nano; Y then Enter saves first.
  • Esc, then :q! and Enter leaves vi without saving; :wq saves.
  • fg brings back a program stopped with Ctrl Z.
  • Ctrl Shift C and Ctrl Shift V copy and paste (Cmd C and Cmd V on a Mac).

The Keys button in the terminal shows this list and can restart the shell.

No. pyrovue is a hosted service: your boxes run on our machines and nothing is installed on yours. Teams that need a dedicated setup can talk to us about Enterprise.

Write to us

Still stuck?

Tell us what happened. A screenshot or the setup log helps; we answer within two working days.

Optional. Up to 3 screenshots, PDFs or logs, 3 MB each.

For repository owners

Tell pyrovue how your repo runs.

pyrovue works most repositories out on its own. A small file at the root makes it exact, and a button in your README lets anyone run it.

pyrovue.json

Drop a pyrovue.json at the root of your repository and pyrovue uses it instead of guessing. The detector reads these fields; all of them are optional.

setup
shell commands, run in order from cwd
start
the command that serves the app; leave it out for a library or CLI
port
the port the app listens on
env
environment variables: strings, numbers or booleans
cwd
a folder inside the repository to run from
previewPath
the path or query to open first
stack
labels shown on the box
services
background programs that start before start: each one is { cwd, start, port }, its cwd from the repository's root

A repository with a frontend and a backend declares the backend as a service: it starts first, in the background, and the preview shows the frontend, which reaches the backend through its own dev-server proxy.

The button and pull request links
pyrovue.json
{
  "setup": ["pnpm install", "pnpm db:migrate"],
  "start": "pnpm dev",
  "port": 3000,
  "env": { "DATABASE_URL": "file:./dev.db" },
  "cwd": ".",
  "previewPath": "/",
  "stack": ["Node", "Vite"]
}
pyrovue.json with a backend service
{
  "setup": ["cd /workspace/backend && pip install -r requirements.txt", "npm install"],
  "services": [{ "cwd": "backend", "start": "uvicorn main:app --port 8000", "port": 8000 }],
  "cwd": "frontend",
  "start": "npm run dev",
  "port": 5173
}