Skip to content
Restura logo

Restura

One open-source 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, and environments live in your browser’s IndexedDB (plaintext) or in encrypted desktop storage. Opt-out crash reports are scrubbed of request content. On desktop, AI chat and AI Lab also send the current request to the provider you configure, with secrets redacted and the URL sent as written.

Scripts that can't escape the sandbox

Pre-request and test scripts run in a QuickJS WASM sandbox. No DOM, no filesystem, no raw fetch. pm.sendRequest goes out through the same SSRF-guarded proxy as a normal send. Memory and execution time are capped. Postman pm.* scripts mostly run; the gaps are listed in the scripts guide.

Chain requests together

Sequence saved HTTP and GraphQL requests as portable OWS workflows with typed bindings, guards, loops, try/catch recovery, and cancellation. Run them in the app or in CI with restura workflow run.

Ask an AI about your request

In the desktop app, the AI assistant can see the current request and response — useful for explaining errors, writing test assertions, or generating follow-up requests. Secrets in headers and bodies are redacted before anything reaches the model; the request URL is sent as written. Web support is planned.

Debug MCP servers

Connect to any MCP server as a client to inspect what’s being sent and returned. Restura can also run as a local MCP server that agents like Claude Code and Codex use to build and run your collections — only what you share, with your approval.

Tested like it matters

A layered suite of unit, integration, security, and end-to-end tests — plus API-contract checks that run the shared protocol core against Worker-style and Node-style fetchers — runs against every change, across the web, desktop, and self-hosted builds. See how it’s tested.

Where Restura is going

Every feature lives on one public roadmap — what has shipped, what is being built, and the ideas taking root. Progress counts milestones already in the code, not estimates.

  • 57 shipped
  • 6 in progress
  • 10 planned
  • 35 exploring