Skip to content

Restura

One client for every protocol your stack uses. No account required.

Get the desktop app

Native builds for macOS, Windows & Linux — unlocking Kafka, mTLS, SOCKS proxies, filesystem-backed collections, and OS-keychain secrets. Auto-updates itself.

I got tired of opening a different tool for every protocol. Postman for HTTP, a separate gRPC client, a WebSocket tab somewhere, Kafka buried in Docker. Then Postman changed its pricing and Insomnia went cloud-first, and I realised my request history — including auth tokens and internal endpoints — was syncing to someone else’s server. Restura is what I wanted instead: one client that speaks every protocol I actually use, with everything staying on my machine.

Web, desktop, or self-hosted

Runs as a web app on Cloudflare, a native desktop app for macOS / Windows / Linux, or a Docker container behind your own firewall. They share one renderer and protocol core; native networking features remain intentionally desktop-only.

Nothing leaves your machine

No account to create. Collections, history, environments, and secrets live in your browser’s IndexedDB or your OS keychain on desktop. The only thing that can leave is opt-out crash reports, which are scrubbed of request content before they go anywhere. You can turn that off in Settings too.

Scripts that can't escape the sandbox

Pre-request and test scripts run in a QuickJS WASM sandbox. No DOM, no filesystem, no network. Memory and execution time are capped. If someone sends you a collection with a dodgy pre-request script, it doesn’t get far. Fully pm.* compatible if you’re coming from Postman.

Chain requests together

Sequence saved HTTP requests as portable OWS workflows with typed bindings, set/wait, and cancellation. Run them in the app or in CI with restura workflow run.

Ask an AI about your request

The AI assistant can see the current request and response — useful for explaining errors, writing test assertions, or generating follow-up requests. Secrets and internal URLs are stripped before anything reaches the model.

Debug MCP servers, or be one

Connect to any MCP server as a client to inspect what’s being sent and returned. Or flip it around: expose your own collections as an MCP server so agents like Claude can discover and run your requests, with your permission.

Tested like it matters

A layered suite of unit, integration, security, contract, and end-to-end tests runs against every change, across the web, desktop, and self-hosted builds.