Step CI
Open-source API testing configured entirely in YAML, built for pipelines.
What it is
Step CI defines API workflows in a YAML file — requests, captures, assertions, matchers — with no scripting language involved. It handles REST, GraphQL and gRPC, can generate tests from an OpenAPI spec, and is designed to run as a single CLI step in CI.
Best for
Where it is strong
- YAML workflows are easy to review in a pull request and need no runtime knowledge.
- Generates a starting suite from an OpenAPI spec.
- Includes basic load-testing capability in the same file format.
Where it falls short
- Looks dormant: the last npm release (2.8.2) was June 2024 and the last commit August 2024, so treat it as unmaintained until that changes.
- YAML hits a ceiling on complex conditional logic.
- Ecosystem and reporting are thin compared to established tools.
Pricing
Free and open source
Open sourceFree tier: Everything, self-hosted
What drives the bill: Free and open source. You pay in engineering time and CI minutes.
Check current pricing on Step CI’s siteFigures are indicative and were last reviewed August 2026. Vendors change pricing often; confirm before you commit.
Works with
What people who use Step CI say
No reviews of Step CI yet. If you have used it in anger, yours would be the first.
Alternatives to Step CI
If Step CI is not the right fit, these solve the same problem differently.
Postman
API Testing
The API platform most developers already have open: requests, collections, tests, mocks.
Bruno
API Testing
Git-native API client that stores collections as plain files in your repo.
Schemathesis
API Testing
Property-based fuzzing that generates API tests straight from your OpenAPI schema.