Know what is happening inside your software.
Invince checks the public website you already run. Paste a URL you own. You get Ready, Fix first, or Do not launch from uptime, HTTPS, and what a visitor can already see. GitHub is optional after you sign in. Invince does not rewrite your repo. Connect GitHub, watch errors, review findings with evidence, keep documentation next to the code, and see why people are (or are not) signing in.
Install npx --yes @invince/cli@0.2.2 --help, npm install @invince/node@0.1.2, and npm install @invince/browser@0.1.2. Skip npm 0.1.1 of the SDKs (empty tarball). The GitHub App already posts a launch-gate check on pull requests. To also fail CI when a key is committed, copy scripts/ci-secret-gate.mjs into your repo. Browser, Node, and Python SDKs post to /api/ingest/errors. An existing Sentry SDK can keep its client and use DSN https://INGEST_KEY@host/0. The Python import is invince (doccraft_ai still works).
- Security findings with evidence, a developer prompt, and why it is high or low
- Runtime errors, performance, and a suggested reply when something pops up
- Hits, new logins, bots, and what people do. from the browser SDK on your app
- Agent observability: startAgentTrace() reports cost, tokens, and stuck loops (Datadog for the agents you run. Invince does not execute the model)
- Documentation generated from the repo, then flagged when a commit moves the facts
- Launch gate on pull requests: Ready / Fix first / Do not launch