# Performate vs the k6 CLI

Canonical HTML: https://performate.app/compare/k6-cli

Performate uses the same k6 engine as the CLI. It does not replace k6. It is a Windows desktop workspace so requests, variables, scenarios, live metrics, and reports live in one place instead of a terminal-plus-spreadsheet loop.

## When should I use Performate instead of only the k6 CLI?

| Capability | Performate | k6 CLI |
| --- | --- | --- |
| Engine | Bundled k6; you do not install k6 separately | You install and version k6 yourself |
| Primary UI | Desktop workspace (Windows) | Terminal and your editor |
| Postman import | First-class collection and environment import | Manual translation or a separate converter |
| Reports | In-app dashboard plus shareable reports | stdout, JSON, or your own Grafana stack |
| AI | Copilot for scripts and run summaries (not autopilot) | None built-in |
| CI/CD | Same k6 tests; Pro+ aimed at pipelines | Native fit for GitHub Actions and similar |

## When to choose which

### Choose Performate when you need

- A desktop workspace for API/QA teams that already have Postman collections.
- Live metrics and shareable reports without wiring exporters first.
- k6 semantics without installing k6 as a separate toolchain step.

### Choose the k6 CLI when you need

- Full control of flags, cloud execution, or custom outputs from day one.
- A script-only workflow with no desktop app.
- Linux or macOS as the primary load-generator OS today (Performate is Windows-only).

## FAQ

### Does Performate replace the k6 CLI?

No. k6 still executes the load. Performate is a workspace around that engine: import, scenarios, dashboards, and reports. You can still think in k6 scripts.

### Can I take Performate tests into CI?

Yes on Pro+: the product is built to reuse the same k6-based tests in pipelines such as GitHub Actions. The CLI remains the execution model.

Related: https://performate.app/en/blog/k6-scenario-types-explained