Reprova

Support

Most of setup is self-serve and guided inside the product. When you need a hand, here's how to get it.

Getting started

After you sign up, the Agents & keys page walks you through the whole setup — the SDK snippet for your framework and ORM, adding an agent next to your database, and the CLI login command, each with copy-paste-ready values.

Create a tenant →

Contact us

Email [support@reprova.io]. We aim to respond within [1–2 business days]. To help us find your capture fast, include your tenant name, the issue ID (REP-#), the release SHA, and a trace id if you have one.

Common questions

repro run fails with “relation … does not exist”+

The reproduction rebuilds your schema from the migrations in the app you point --cwd at, then seeds the rows the capture recorded. This error means the table exists in the captured data but not in that schema. Check two things: your agent's replica URL points at the same application database the error came from, and your local checkout's migrations include the schema version the capture used. Fix the agent's database URL if needed, rebuild the reproduction, and re-run.

I can’t connect to the disposable database+

repro run creates the throwaway database with username reprova, password reprova, database reprova, on the port printed in the run output (it changes each run). It exists only while the reproduction environment is up — repro down removes it. The quickest way in is repro db <ISSUE_ID>, which opens a shell for you.

My captures aren’t showing up on the Issues page+

Confirm your REPROVA_DSN uses an ingest key for the tenant you're viewing, and that the host is reachable from where your app runs — use localhost from your own machine, or the internal service hostname from inside a container. The SDK is fire-and-forget, so an unreachable or wrong URL fails silently.

Which database URL does my agent need?+

Your own application's database — a read replica is preferred. The agent extracts reproduction data from whatever this points at, so it must be your app's database, not the bundled demo. Paste a plain connection string without framework-only parameters (for example, drop Prisma's ?schema=public, which Postgres rejects).

Resources