Introduction
Vegha is a cross-platform, native, MIT-licensed API testing desktop app. It pairs a Bruno-class request engine with enterprise-grade polish — and it runs entirely on your machine, with zero telemetry.
If you live in an API client all day, Vegha is built for you: fast to launch, calm under load, and honest about what it does with your data (nothing).
Why Vegha exists
Section titled “Why Vegha exists”The desktop API-testing category is dominated by Electron apps that boot slowly, consume gigabytes of memory, and quietly phone home. Vegha takes a different position:
- Native binary. Built on Avalonia and .NET 10. It starts in under a second and stays responsive with thousands of requests open. The installed footprint is roughly 32 MB.
- Local-first. Your collections are plain-text files in a folder you choose. There is no account, no workspace in someone else’s cloud, and no sync you didn’t ask for.
- Zero telemetry. No analytics, no crash reporting, no phone-home. The only outbound traffic Vegha ever produces is the requests you explicitly send and the auth flows you explicitly start. See Data & Privacy.
- MIT-licensed. Use it, fork it, ship it commercially. The full source is on GitHub.
What you can do with it
Section titled “What you can do with it”Vegha covers the full surface of modern API work:
| Area | Highlights |
|---|---|
| Protocols | HTTP/REST, GraphQL, gRPC (unary + all streaming modes), WebSocket, SOAP 1.1/1.2 with WSDL |
| Authentication | API Key, Bearer, Basic, Digest, NTLM, OAuth1, OAuth2 (auth-code + PKCE, client-credentials, password), AWS SigV4, WSSE, mTLS |
| Collections | Bruno-style .bru files — plain-text, human-readable, git-friendly |
| Importers | Bruno, Postman v2/v2.1, Insomnia v4/v5, OpenAPI 3.x / Swagger 2.0, WSDL |
| Variables | {{variable}} interpolation with cycle detection across collection, environment and workspace scopes |
| Scripting | Sandboxed pre-request / post-response scripts and a test runner (Jint engine) |
| Git | A native git UI — branch, commit, push, pull, stash, and a three-pane merge resolver |
| Secrets | secret:// URIs resolved at send time from Azure Key Vault and AWS Secrets Manager |
| Code generation | Export any request as curl, Node fetch, Python requests, Go, C#, or Java |
| CLI | The same engine, headless: vegha run and vegha import for terminals and CI |
How Vegha is distributed
Section titled “How Vegha is distributed”Vegha ships in three flavors from a single codebase:
- Direct download — signed installers with in-app auto-update via Velopack. This is the recommended way to get Vegha.
- Microsoft Store — an MSIX package; updates are managed by the Store.
- Mac App Store — a sandboxed, signed package; updates are managed by the Store.
The Store builds defer updates entirely to the store and never check for updates themselves.
Where to go next
Section titled “Where to go next”- New to Vegha? Start with the Quick Start — your first request in five minutes.
- Ready to install? See Installation.
- Coming from Postman or Insomnia? Jump straight to Importing.
A note on the engine
Section titled “A note on the engine”Vegha’s request engine and importer logic are derived in part from
Bruno (MIT). If you already know Bruno’s .bru
format and its bru scripting API, you will feel at home immediately.