What is Certyn?

Certyn is an autonomous QA execution system. You configure environments and context, define what to verify, and Certyn runs continuously with browser-based agents, producing evidence and issues when something breaks.

Is Certyn a replacement for Jira/Linear/GitHub Issues?

No. Certyn tracks internal work items for auditability and automation, but your external tracker can remain your source of truth for ownership and planning.

Do I need to write code?

No. Tests are written as natural-language instructions with explicit expected outcomes.

Can I watch runs live?

Yes. While sessions are running you can open the live view (for example from a process page via Watch Live).

How do environment variables work?

Environment variables are passed to the agent as part of the environment context. In your tests, instruct the agent to use variables by name (for example: "Use LOGIN_USERNAME and LOGIN_PASSWORD from the environment variables").

Can I run on a schedule or from CI?

Yes.

Use process schedules (daily/weekly/cron) for recurring runs.
On GitHub, use certyn/action@v1.
On other CI systems, use Certyn CLI:
- certyn run smoke --project <project-slug> --environment <environment-key>
For low-level HTTP integration, use the CI Runs API reference.

Do we need to change our gitflow to use Certyn?

No. Keep your current branch and release model.

Integrate Certyn at your existing decision points:

merge gates (PR checks)
deploy/promotion gates (post-deploy smoke)
nightly quality sweeps (regression)

How is usage measured?

Usage is measured in execution minutes (compute time) rather than "number of tests". This reflects how much agent runtime your runs consume.

What if a test is flaky?

Treat flakiness as a first-class signal:

quarantine unstable tests so they stop blocking important runs
make tests smaller and more deterministic
use stable test data and dedicated test accounts

Frequently Asked Questions