Free
For a small team evaluating Reqflo with real shared workflows.
$0/mo
Free forever
- Up to 3 users
- Unlimited local CLI runs
- 25 secure cloud runs · lifetime
- 3 services
- Metadata-only evidence
Pricing
Built for shared API work, priced around actual execution.
Every Reqflo organization is team-ready. Unlimited local CLI runs, journeys, and roles on every plan - you pay as cloud execution, retained evidence, and org scale grow.
Business annual - save 15%
Starter
For small teams running approved API workflows with managed secrets.
$149/mo
Monthly only
- 5 users
- Unlimited local + CI CLI runs
- 500 secure cloud runs / mo
- 10 services
- 3-day full evidence retention
BusinessRecommended
For governed validation, support runbooks, and shared execution across the org.
$799/mo
billed monthly · save 15% annually
- Up to 50 users
- Unlimited local + CI CLI runs
- 3,000 secure cloud runs / mo
- 100 services
- 14-day full evidence retention
- SSO/SAML included
Enterprise
For production controls, private execution, and custom governance.
From $24k/yr
Annual contract · PO available
- 100+ users
- Unlimited local + CI CLI runs
- Contracted secure cloud run pool
- Unlimited services
- SCIM + private runners
- Custom retention & controls
On every paid plan
Team-ready out of the box.
Reqflo keeps the core workflow model open across plans, with tiers that scale by cloud execution, evidence retention, and team size.
Unlimited local and CI execution
Run Reqflo from your machine, GitHub Actions, GitLab, CircleCI, or your own runners without spending hosted cloud runs.Secure governed cloud runs
Reqflo-hosted runs include managed secrets, environment bindings, access controls, and structured evidence..Workflows aren’t the meter
Build journeys, request templates, and reusable components for the services in your plan without per-workflow fees.Standard roles included
Owner, Admin, Builder, Viewer, Billing, and the Run Ops / Support role - on every plan.Secrets stay governed
Run Ops and support users can execute approved workflows without viewing raw secrets, tokens, or sensitive environment values.Structured validation evidence
Assertion results, timing, status, redacted traces, and retained artifacts according to your plan. Reqflo is not a log sink.Source-controlled by default
Templates and journeys generated from the same OpenAPI specs that ship your services.Environment bindings included
Connect each service to the environments your team uses, with governed access to sensitive bindings for cloud runs and runbooks.Compare all features
Free $0 | Starter $149/mo | Business $799/mo | Enterprise Custom | |
|---|---|---|---|---|
| Local CLI runsRun validation locally, always free | ||||
| CI execution through CLIUse GitHub Actions, GitLab, CircleCI, or your own runners | ||||
| Secure cloud runsReqflo-hosted execution with governed secrets and environment bindings | 25 · lifetime | 500 / mo | 3,000 / mo | Contracted |
| Additional secure cloud runsPay-as-you-go or contracted overflow | — | $0.20/run | $0.12/run | Contracted |
| Scheduled cloud runs | ||||
| UsersAcross the workspace / domain | 3 | 5 | 50 | 100+ |
| Standard rolesOwner, Admin, Builder, Viewer, Billing | ||||
| Run Ops / Support roleSafe execution without edit access | ||||
| Custom roles | ||||
| Services / APIs | 3 | 10 | 100 | Unlimited |
| Journeys | Unlimited | Unlimited | Unlimited | Unlimited |
| Request templates | Unlimited | Unlimited | Unlimited | Unlimited |
| Components & playbooks | Unlimited | Unlimited | Unlimited | Unlimited |
| Full evidence retentionRequest/response details, assertions, timing, redacted traces | None | 3 days | 14 days | Custom |
| Metadata retentionRun history, pass/fail, summaries | 30 days | 90 days | 1 year | Custom |
| Structured evidenceNot raw application logs | ||||
| Evidence export & sharing | ||||
| Audit exports | ||||
| Role-gated safe execution | ||||
| Managed secret distributionUse approved secrets without exposing raw values | ||||
| Environment-bound secretsBind credentials to approved test, staging, or production environments | ||||
| Production binding controlsRestrict who can execute workflows against production | ||||
| SSO / SAML | ||||
| SCIM provisioning | ||||
| Custom domain enforcement | ||||
| Private runnersRun in your own network | Optional | |||
| AI credits / monthGeneration, summaries, suggestions | 25 | 250 | 5,000 | Contracted |
| No training on your data | ||||
| Enterprise-grade AI handlingWorkspace isolation + admin controls | ||||
| Approved / private AI providers | ||||
| Support | Community | Priority | SLA options | |
| Guided onboarding | Dedicated | |||
| Uptime SLA | ||||
| BillingHow each plan is purchased | Free | Monthly only | Monthly or annual | Annual · PO |
Evidence & retention
Full detail when it's fresh. History for the long run.
Ninety days of full run history is expensive and usually unnecessary. Reqflo keeps complete evidence while it's useful, then retains lightweight metadata far longer so you can still answer "did this pass last month?"
Full evidence
Everything you need to reopen a run and see exactly what happened.
- Request and response metadata
- Assertion results and step timing
- Status codes and retained headers
- Body snapshots and artifacts, when retained
- Detailed failure context
- Variable resolution trace, with redaction
Metadata only
The run's history, kept long after the full payload ages out.
- Run ID, journey, service, environment
- Started / completed timestamps and duration
- Triggered by user, CI, or schedule
- Pass / fail / error, with failed step names
- Assertion and status-code summaries
- Linked work item, release, or build
| Plan | Full evidence | Metadata |
|---|---|---|
| Free | None | 30 days |
| Starter | 3 days | 90 days |
| Business | 14 days | 1 year |
| Enterprise | Custom | Custom |
Reqflo keeps the validation evidence teams need while avoiding raw log storage. Live request logs are available during execution, redacted by default, and not retained as application logs.
Roles & access
The same role model on every plan.
Roles are a product primitive, not a paywall. The Run Ops / Support role lets non-builders run approved workflows safely - for support diagnostics, CSM validation, QA regression packs, and onboarding checks.
Owner
Billing, workspace settings, and domain controls.
Admin
User management, integrations, and environment settings.
Builder
Creates and edits services, journeys, templates, and components.
Run Ops / SupportSpotlight
Runs published journeys and playbooks in approved environments - without touching the logic.
Viewer
Read-only access to dashboards, services, journeys, and evidence summaries.
Billing admin
Optional billing-only role, separate from org administrator.
Run Ops can
- Run published journeys and playbooks
- Select allowed environments
- Provide approved input variables
- View execution status and pass/fail summaries
- Export approved evidence reports, if permitted
- Rerun failed steps, if permitted
Run Ops cannot
- Edit request templates or journey structure
- Modify assertions or governance rules
- Access raw secrets or redacted values
- Change environment configuration
- Create or modify components
Enterprise · from ~$1,000/mo
For scale, controls, and custom operating needs.
Contracted execution pools and unlimited services, metered only where it's fair: compute minutes, retained evidence, AI usage, private runners, and support tier.
Contact salesSSO/SAML & SCIM - provisioning, plus custom domain enforcement
Unlimited services & journeys - no procurement conversation about API #801
Private runners - run validation inside your own network
Custom evidence & retention - contracted pools for execution and storage
Custom AI controls - approved or private providers if you need them
SLA & dedicated support - uptime SLA and a named contact
Questions
Pricing, answered plainly.
A secure cloud run is a Reqflo-hosted execution of a journey, scheduled check, or runbook action. It includes managed secret access, environment bindings, role-gated execution, redaction, and structured evidence. It is not generic CI compute.