
## 🚨 Problem

API testing is fragmented.

Teams are forced to split their workflow across multiple tools: one for manual exploration, another for CI automation, another for load testing, and separate systems for reporting.

This fragmentation creates a predictable outcome:

- Test logic gets duplicated across tools
- Manual and automated tests drift out of sync
- Ownership becomes unclear
- CI failures become harder to debug
- AI assistants can’t reason about hidden scripts, cloud-locked state, or fragmented definitions

**The root problem is simple: the test is not a file.**

It lives in cloud accounts, buried in scripts, or trapped in proprietary formats instead of your repository.

And if a test isn’t a plain, versioned, reviewable file, it can never become the single source of truth.

## 💡 Solution

One tool. One file format. Runs everywhere.

- Tests are plain YAML files stored in Git alongside your code
- The same `.mmt` file runs in VS Code UI, the `testlight` CLI, and CI pipelines
- Edit YAML and the UI updates instantly — edit the UI and YAML updates instantly
- Results are versioned, reproducible, and reviewable in pull requests
- Plain YAML is easy for AI to read, generate, and modify — fits naturally into AI-assisted workflows

## 🆚 Why Not Postman, Bruno, or Insomnia?

| | Postman | Bruno | Insomnia | **Multimeter** |
|---|---|---|---|---|
| **Price** | $19+/user/mo | $19+/user/mo | $16+/user/mo | **Free** |
| Git-native (plain files) | ❌ | ✅ | ❌ | ✅ |
| Offline & fully private | ⚠️ cloud sync | ✅ | ⚠️ cloud sync | ✅ |
| Same file runs in UI + CI | ❌ | ⚠️ partial | ❌ | ✅ |
| Code ↔ UI live sync | ❌ | ✅  | ❌ | ✅  |
| Test suites | ⚠️ collections | ⚠️ collections | ⚠️ collections | ✅ |
| Reusable tests (imports) | ⚠️ partial | ⚠️ partial | ⚠️ partial | ✅ |
| Load testing | ⚠️ paid add-on | ❌ | ❌ | ✅ |
| Drag & drop test builder | ❌ | ❌ | ❌ | ✅ |
| Built-in mock server | ❌ | ❌ | ❌ | ✅ |
| AI test generation | ❌ | ❌ | ❌ | ✅ |
| Flowchart test view | ❌ | ❌ | ❌ | ✅ |
| Auto-generated API docs | ❌ | ❌ | ❌ | ✅ |

[See full comparison →](https://mmt.dev/#comparison)

## ✨ Features

- **Real-time YAML ↔ UI sync** — no separation between "code" and "visual" modes
- **Git-native** — tests live in your repo, reviewed in PRs like any other file
- **Flowchart test view** — see branches, loops, and assertions as a diagram
- **Multi-protocol** — HTTP/REST, WebSocket, GraphQL, gRPC, SOAP
- **Built-in mock server** — spin up HTTP/WS mocks from YAML in milliseconds
- **AI test generation** — `@Multimeter` VS Code chat participant generates complete test flows from natural language, OpenAPI specs, or existing API definitions
- **Import from Postman, OpenAPI, .http, Bruno** — no rewrite needed
- **Multi-format reports** — HTML, JUnit XML, Markdown, MMT
- **Load testing (beta)** — threads, ramp-up, repeat limits
- **Drag & drop test builder** — build flows visually without scripting
- **Auto-generated API docs** — HTML and Markdown from the same YAML you already write
- **Fully offline & private** — nothing leaves your machine

## 🚨 Problem API testing is fragmented. Teams are forced to split their workflow across multiple tools: one for manual exploration, another for CI automation, another for load testing, and separate systems for reporting. This fragmentation creates a predictable outcome: - Test logic gets duplicated across tools - Manual and automated tests drift out of sync - Ownership becomes unclear - CI failures become harder to debug - AI assistants can’t reason about hidden scripts, cloud-locked state, or fragmented definitions **The root problem is simple: the test is not a file.** It lives in cloud accounts, buried in scripts, or trapped in proprietary formats instead of your repository. And if a test isn’t a plain, versioned, reviewable file, it can never become the single source of truth. ## 💡 Solution One tool. One file format. Runs everywhere. - Tests are plain YAML files stored in Git alongside your code - The same `.mmt` file runs in VS Code UI, the `testlight` CLI, and CI pipelines - Edit YAML and the UI updates instantly — edit the UI and YAML updates instantly - Results are versioned, reproducible, and reviewable in pull requests - Plain YAML is easy for AI to read, generate, and modify — fits naturally into AI-assisted workflows ## 🆚 Why Not Postman, Bruno, or Insomnia? | | Postman | Bruno | Insomnia | **Multimeter** | |---|---|---|---|---| | **Price** | $19+/user/mo | $19+/user/mo | $16+/user/mo | **Free** | | Git-native (plain files) | ❌ | ✅ | ❌ | ✅ | | Offline & fully private | ⚠️ cloud sync | ✅ | ⚠️ cloud sync | ✅ | | Same file runs in UI + CI | ❌ | ⚠️ partial | ❌ | ✅ | | Code ↔ UI live sync | ❌ | ✅ | ❌ | ✅ | | Test suites | ⚠️ collections | ⚠️ collections | ⚠️ collections | ✅ | | Reusable tests (imports) | ⚠️ partial | ⚠️ partial | ⚠️ partial | ✅ | | Load testing | ⚠️ paid add-on | ❌ | ❌ | ✅ | | Drag & drop test builder | ❌ | ❌ | ❌ | ✅ | | Built-in mock server | ❌ | ❌ | ❌ | ✅ | | AI test generation | ❌ | ❌ | ❌ | ✅ | | Flowchart test view | ❌ | ❌ | ❌ | ✅ | | Auto-generated API docs | ❌ | ❌ | ❌ | ✅ | [See full comparison →](https://mmt.dev/#comparison) ## ✨ Features - **Real-time YAML ↔ UI sync** — no separation between "code" and "visual" modes - **Git-native** — tests live in your repo, reviewed in PRs like any other file - **Flowchart test view** — see branches, loops, and assertions as a diagram - **Multi-protocol** — HTTP/REST, WebSocket, GraphQL, gRPC, SOAP - **Built-in mock server** — spin up HTTP/WS mocks from YAML in milliseconds - **AI test generation** — `@Multimeter` VS Code chat participant generates complete test flows from natural language, OpenAPI specs, or existing API definitions - **Import from Postman, OpenAPI, .http, Bruno** — no rewrite needed - **Multi-format reports** — HTML, JUnit XML, Markdown, MMT - **Load testing (beta)** — threads, ramp-up, repeat limits - **Drag & drop test builder** — build flows visually without scripting - **Auto-generated API docs** — HTML and Markdown from the same YAML you already write - **Fully offline & private** — nothing leaves your machine

Multimeter

Functional, Automation And Performance Testing, as code...

Functional, Automation And Performance Testing, as code...