Linux
Release
Current public distribution platform, with release artifacts for standard Linux install paths.
Local-first desktop API workspace
Build, test, and automate API workflows without centering the cloud.
API Wire keeps requests, collections, environments, runtime tooling, and secret handling in one desktop workspace for HTTP, GraphQL-over-HTTP, gRPC, SSE, and WebSocket workflows.
Linux release available. macOS and Windows are available as unsigned previews, so trust warnings are expected until signing is added.
Current workspace
Platform status
Linux leads the release path. The other desktop surfaces are honest previews.
macOS
Unsigned preview
Available as a preview build. Trust warnings are expected until signing is added.
Windows
Unsigned preview
Available as a preview build. SmartScreen and trust warnings are expected until signing is added.
Core workflows
Protocol breadth, runtime depth, and workspace control in one desktop surface.
Request authoring
Work across the protocols teams actually use.
Author and organize HTTP, GraphQL-over-HTTP, gRPC, SSE, and WebSocket workflows inside one desktop workspace.
Runtime tooling
Keep execution logic near the request.
Use auth, scripts, assertions, chaining, and response inspection without bouncing between disconnected tools.
Workspace organization
Structure collections and environments deliberately.
Manage collections, environments, import and export flows, diff and review paths, and request history in the same place.
Local services
Support the surrounding workflow, not only the request.
Local mock services, CLI execution, and OS keyring-backed secret handling help keep the daily loop grounded on-device.
Operator tooling
Give operational workflows a first-class surface.
Settings, monitoring views, and Control Plane workflows sit alongside the rest of the workspace instead of pretending to be a hosted console.
Why local-first
Core usage works on your machine, by default.
API Wire does not require a cloud account for core local usage. Collections, settings, environment work, and secret handling stay local by default, and optional sync is a user-chosen path rather than the center of the product.
No cloud account required
Core request work, local collections, and workspace flows are designed to run without requiring a cloud account for core usage.
Secrets handled locally
Secure values are kept out of workspace metadata plaintext exports and are intended to stay within local secret-handling paths.
Optional sync stays optional
If you configure Cloud Sync against your own endpoint, selected workspace snapshot data can move there. That is not the default mode.
Trust and safety
Clear caveats beat vague polish.
- Verify checksums before running downloaded binaries.
- Linux is the current release platform; macOS and Windows remain unsigned previews.
- Trust warnings on macOS and Windows are expected until signing is added.
- Security reporting instructions are published and routed privately.