Karve app icon

Karve

One-time purchase · Owned forever

A native home for your .http files.

Karve is a native Windows API workspace built around .http and .rest files already scattered across your repos.
Organize requests in one workspace and run them without bloat or subscriptions.

Start with a 7-day free trial

Windows 10/11 · no account · no subscription

Native WinUI 3 · no Electron 100% local No account, no subscription Open .http format · owned forever Crash-only telemetry

Your requests are plain .http files — the open, text-based format your editor already understands. They live as files on disk, scattered across whatever repos you work in: they sit next to your code, diff cleanly in Git, and belong to you. Karve is the workspace that sits on top of them — no conversion, no import, no proprietary format.

The problem

Requests pile up everywhere

The same .http files scatter across repos and editor tabs — and you hunt for the one you need.

You lose the thread

Which request hit which service, and what did it return last time? The context is gone the moment you switch windows.

What actually got sent?

Between variables and substitution, the real request on the wire is a guess — until something breaks in production.

Before / after

Before Karve
  • Hunt for the right .http file across repos.

  • Paste it into a separate client and fix the variables by hand.

  • Run it — then lose the response the moment you move on.

  • Repeat for the next service, in the next window.

With Karve
  • Gather .http files from every repo into one workspace — files never move.

  • Variables resolve in the file — run straight from the method line.

  • Each response stays in its own panel; the resolved request shows exactly what was sent.

  • Tabs and history keep your place across services.

Features

Every request in one workspace.

Add .http files from anywhere on disk — even spread across different repos and projects — and group them into virtual folders. Karve organizes on top of your filesystem: files never move, so your repo structure and Git history stay exactly as they are. Reorder with drag-and-drop, search across files and requests, and drop files straight from Explorer onto the window.

Virtual folders Across repos Files stay put

Write it, run it, read it.

Write a request, click Run on its method line, and the response lands in its own panel. All HTTP methods, custom headers, query params, and request bodies are supported — with syntax highlighting, line numbers, and {{variable}} autocomplete.

Open a file. Run a request. Read the response.

See exactly what came back.

A response viewer that gets out of the way: switch between a collapsible JSON tree, a pretty-printed raw body (JSON and XML), a clean response-headers table, and the resolved request that shows exactly what was sent after variable substitution. Status, time, and size at a glance — copy or save any response body in one click.

JSON tree Raw Headers Timing

And the rest

File-level variables

Declare @baseUrl once and reuse it with {{baseUrl}} across every request in the file.

Tabs with session restore

Work across multiple files in tabs. Karve restores your open tabs on every launch, so you pick up where you left off.

Session history

Every request you run is listed with its method, status, and timing — click any entry to jump back to it.

Light & dark, with Mica

Native Mica material; light and dark themes follow your Windows setting automatically.

Native WinUI 3

Built on WinUI 3, not a browser in a box. Cold-starts in under 2 seconds, runs 0 background services, and sends no telemetry beyond crash diagnostics.

Drag-and-drop

Drop .http files and whole folders straight from Explorer onto the window.

Why I built Karve

As I was working a lot with microservices, I already kept my requests as .http files next to my code in repos. It was quite annoying to manage and work with them, especially when I need share requests, like get a token or something like that. So I built a tool to manage and run them. Karve is the workspace I wanted: your files stay on disk and stay yours, and the tool just helps you run and read them.
Pavel, founder of Karve

Pavel

XAKPC Dev Labs · founder

Follow along on GitHub

FAQ

Why .http files?
Because they're open and text-based. Your requests live next to your code, diff cleanly in Git, and stay readable in any editor — no proprietary format, no export step, no lock-in. Karve runs the exact files you already have.
Why not just use VS Code?
If you live in your editor, the REST Client extension is a great free option. Karve is for when you want a dedicated native workspace: gather .http files from many repos into virtual folders, get a richer response viewer (JSON tree, headers, timing), and keep tabs and history — no editor required. Karve vs VS Code REST Client →
Why not Bruno?
Karve doesn't invent its own format or collection store — it runs your existing .http files in place. It's native WinUI 3 (not Electron), a one-time purchase, and needs no account. Karve vs Bruno →
Is my data private?
Yes. Karve runs entirely on your machine — requests are sent straight from your PC and nothing is stored in any cloud. The only data it sends is anonymous crash diagnostics. Privacy policy →
Can I import from Postman?
.http and .rest files open directly — it's the same format VS Code REST Client and JetBrains HTTP Client use, so there's nothing to convert. Importing Postman collections and cURL is on the v1.1 roadmap →
What does it cost?
$29.99 during launch (25% off the regular $39.99), a one-time purchase with a 7-day free trial — no subscription, no metered requests. See pricing →

Pricing

Launch Offer

Start with a 7-day free trial.

$29.99 launch price · one-time purchase · v1.x updates included. No account, no subscription, no upsell. See pricing details.

7-day free trial · No account · No subscription · No metered requests

25% off now