All your tests.
One Plan.
Stop stitching tavern, hurl, Bruno, Playwright, SQL, and AI-conversation tests together with cron jobs and hope. Run them all as one ordered Plan instead on a real schedule, or straight from your agent's own session and every result lands somewhere you can actually find it later.
Here's the same idea, running for real.
The real TestPlanHQ dashboard your tests, Plans, schedules, and webhooks, all in one place, screenshot taken straight off the product.
What you actually do with it
Compose every test type into one Plan
Mix all 8 types freely in one ordered run: an HTTP contract test, a browser flow, a database assertion, an LLM conversation check. Each group sets its own failure policy, so one flaky step doesn't have to take down the rest. Outputs thread automatically into the next step's Environment no manual variable hand-off.
Let an AI agent run the whole lifecycle
The MCP server isn't a chat layer bolted onto the product. It's the same Project/Suite/Plan/Run/Environment lifecycle the UI uses, exposed as real tool calls author and validate content, trigger a run, read history, manage your org. An agent can operate this platform end to end today.
Automate on a schedule you can actually trust
Schedules run on real RFC 5545 RRULE recurrence. The preview you see while building a rule uses the exact same engine as the poll that fires it later so what you see is genuinely what happens, not a second implementation guessing at the same rule.
Multi-tenant, with roles that mean something
Every organization is a real, isolated tenant, and every member holds one of four roles Observer, Operator, Maintainer, Owner enforced on the same backend path whether the caller's a browser session or a token. Webhook payloads are HMAC-SHA256 signed, so a receiver can actually verify they came from you.
An honest status page, not a trust-badge wall.
Every route resolves the calling tenant and project before it touches any data, not after that's enforced on the main request path, not bolted on. We're actively hardening it this week as real usage turns up real edges, and we fix them in the open.
- Tenant → Project → execution profile, resolved on every request, never assumed from a client header.
- A dispatched run gets its own ephemeral container spun up, executed, torn down, never shared or reused.
- An Observer role sees results and history never source, never write access enforced identically for a person or a token.
Built for environments that can't afford a mistake real multi-tenant isolation, role enforcement on every route, an execution boundary that's architectural rather than a settings toggle. We test this platform with the same discipline we built it with.
Before you ask sales
Stop maintaining four test runners to cover one product.
Start on the free tier 100 test cases, 500 runs a month, no card required.