No-code QA for real backends

Test annotated APIs without writing tests in your app language.

Cat-Inspector gives QA teams a guided way to validate backend behavior. Developers allowlist the functions that are safe to test, the platform turns those functions into readable forms, and every run records clear inputs, outputs, and assertion results.

Instead of asking testers to learn internal services, payload formats, or source code, the home workspace explains what is available, how to run it, and what the expected outcome should be.

Create an organizationSign in

What the platform connects

From backend functions to QA-ready checks

The same catalog powers discovery, form generation, execution, and result review. That keeps product behavior, QA expectations, and developer-owned code connected.

Developer setup

Annotate

Mark the functions QA is allowed to call.

QA workflow

Author

Build cases from generated forms and assertions.

Runtime

Invoke

Run checks safely through the inspector transport.

Why teams use Cat-Inspector

One surface for catalog discovery, no-code case authoring, controlled execution, and explainable results against your allowlisted backend surface.

Live catalog
The host application publishes a catalog of registered functions, readable names, parameters, expected shapes, and return metadata so QA knows exactly what can be tested.
Forms, not scripts
Each function becomes a guided form. Testers enter payloads, choose assertions, and save reusable cases without learning the backend language or test framework.
Run and assert
Run selected functions over the inspector transport, compare the returned value with expected outcomes, and review clear pass or fail results in one place.
Allowlisted only
Only functions explicitly registered by developers are callable. Payload validation and authentication keep the test surface intentional and controlled.
Tenant workspace
Each organization gets its own workspace for members, access keys, saved cases, and activity, keeping tenant data separated from other teams.
Fits your pipeline
Backend teams wire the SDK once, then QA, dashboards, and automation can consume the same catalog and protocol as the product evolves.

How it works

Two views of the same pipeline: developers keep control over what can run, while QA gets a clear workspace for building and repeating checks.

1. Developers expose safe test units

Backend developers register functions through the SDK and describe the inputs, return types, and labels that should appear in the catalog.

2. The catalog becomes the QA interface

The web app reads that metadata and turns it into understandable forms, so testers work with business inputs instead of source code.

3. Runs produce explainable results

Every invocation returns structured output, errors, and assertion results that make it easier to see what failed and why.

  1. Open the workspace and review the catalog synced from the host. Each entry explains what the function does and which fields are required.
  2. Pick a function and fill the generated form from parameter metadata, without guessing payload structure or writing request scripts.
  3. Set expected outcomes, run checks, and compare the response with assertions that are easy for non-developers to read.
  4. Save useful cases, repeat them after changes, and share failures with enough context for developers to reproduce quickly.

Questions

Quick answers for evaluators and new tenants.

What is Cat-Inspector?▼
A no-code testing platform that connects QA-friendly UIs to annotated host functions via a catalog and safe invoke path. The goal is to help teams validate real backend behavior without forcing every tester to write application-level tests.
Who is the home page for?▼
Anyone evaluating the product: engineering leads, QA managers, platform operators, and new tenant admins who need to understand what happens before they sign in or create an organization.
Do testers write code?▼
No. Test cases are authored from forms built from parameter metadata and simple assertions, such as type checks, structured equality, or field existence. Developers own the SDK side and decide what is exposed.
How do I try it?▼
Use Get started to create an organization, or Sign in if your tenant already exists. From the dashboard you can manage users, access keys, catalog data, and related workspace tools.
Is my tenant data isolated?▼
The platform is built around per-tenant workspaces for people, keys, and activity. You should still follow your organization's policies for secrets, sandbox data, and production environment access.
Why not just use an API client?▼
API clients are useful, but they usually require testers to know endpoints, payload details, and expected response shapes. Cat-Inspector starts from developer-approved functions and turns their metadata into a guided QA workflow.