No login wall
Open it and send a request. Your workspace is a file on your disk, it works offline, and nothing is uploaded unless you choose to share it.
A fast, local-first API client for REST, gRPC, GraphQL, SSE and MCP. No account, no cloud lock-in, no bloat. Just a native app that gets out of your way.
Protos synced from gitPrivate repos, your SSH keys
FieldMask, Tab to completePaths straight from the schema
Schema drift, caughtWhen the server knows fields you don't
Open it and send a request. Your workspace is a file on your disk, it works offline, and nothing is uploaded unless you choose to share it.
Secret variables live in the macOS Keychain, Windows Credential Manager or Secret Service. Never in workspace files, never in exports, never in AI prompts.
Requests go out from a Rust core, so there's no CORS to fight. localhost just works, the app opens instantly, and it's light on memory.
REST
Most of your day is plain HTTP, so that's where Ofcors is sharpest. Paste a cURL command into the URL bar and it's a request. Flip between local, staging and production with one click.
Flows
Creating a sandbox account, seeding test data, walking an order through to "shipped": chain the requests once as a flow, then run it whenever you need it.
{{step1.id}}, {{step1.headers.location}}. Mix REST, GraphQL, gRPC and SSE steps.
Project folders
Link a folder and its requests, flows and environments live there as plain YAML files, next to the code they test. Review them in pull requests like anything else.
git pull or a branch switch shows up in Ofcors straight away.method: GET url: "{{baseUrl}}/v1/charges"url: "{{baseUrl}}/v2/charges?limit=20"
Command line
The ofcors command runs your flows and saved requests with the same environments and keychain secrets as the app. It comes with the app; on a CI
runner, one line installs it.
ofcors run a flow with inputs, ofcors send a request (HTTP, GraphQL or gRPC), or ofcors curl to get it as cURL.--json output and exit codes that mean one thing each, so scripts and CI jobs can rely on it.ofcors skill prints instructions that teach them how.$ ofcors run "Sandbox merchant" -e staging Sandbox merchant · staging ✓ 1 POST Create merchant 201 132 ms merchantId=m_42 ✓ 2 SCRIPT Plan code 0 41 ms planCode=M_42-PRO ✓ 3 GET Check merchant 200 88 ms Done in 302 ms Merchant m_42 (M_42-PRO), log in as ada@example.com $ curl -fsSL https://ofcors.dev/install.sh | sh
AI chat · SSE
Point Ofcors at any endpoint that streams its replies as server-sent events and just talk to it. Your messages go into the body as
{{chat.messages}}, and every reply streams back token by token.
gRPC
Point Ofcors at the repo your protos live in. It clones with your own SSH keys, understands Buf workspaces, and quietly syncs when the commit changes.
grpcurl.
Auth
Tell a variable which request logs you in and where the token is in the response. When the JWT expires, Ofcors runs the login for you before your
request goes out, and retries once if anything still says 401 or UNAUTHENTICATED.
exp or an expires_in field. The cached token is a secret in your keychain.{{variables}} are flagged before you send.
MCP
Connect to any Model Context Protocol server over stdio (Ofcors launches it) or Streamable HTTP, and see exactly what it does.
Test data
Type rand. anywhere for around seventy generators: names, emails, ULIDs, ISO dates, prices, Luhn-valid test card numbers,
rand.pick(a, b, c) and more. Fresh values on every send.
Speed
Jump to any request, gRPC method, recent call or command with ⌘K. Fire a one-liner from the quick-call bar. Every call lands in the log with its response, ready to reopen or replay.
Paste a cURL command into the URL bar and it becomes a request. Take any request back out in the form you need.
Pay only for what involves other people or our servers. Small teams shouldn't need a budget meeting.
$0 forever
ofcors commandFor one developer, many machines
Free for teams of up to 3
Free for macOS, Windows and Linux. Updates install themselves.
Apple silicon and Intel
Windows 10 and 11, x64
AppImage, .deb and .rpm
For a CI runner or a server without the app: curl -fsSL https://ofcors.dev/install.sh | sh
(Windows: irm https://ofcors.dev/install.ps1 | iex)
The first public build is nearly here. Join the waitlist and we'll email you the moment it's out.
Yes. Everything you do on your own machine is free, with no account and no time limit. Paid plans will cover things that involve other people or our servers, like real-time team workspaces and device sync.
In a JSON file in your app data folder, plus secret values in your operating system's keychain. Link a project folder and its requests, flows and environments are stored there as YAML files instead (secret values still stay in the keychain). Nothing is sent anywhere unless you use a sharing feature.
The only request Ofcors makes on its own is checking for updates. There's no analytics or tracking in the app. We count downloads and update checks per day to know roughly how many people use it, without storing IP addresses or any identifier.
Yes. Ofcors uses your system git, so your SSH keys, agent and credential helpers just work. It reads buf.yaml and ships the common Buf registry dependencies (googleapis, protoc-gen-validate, protovalidate) for repos that don't vendor them.
Yes. Export your collections and environments from Postman, then use Import → Postman in Ofcors. Folders, auth, bodies and {{variables}} come across, and it tells you what doesn't (like scripts). How Ofcors compares to Postman.
Yes. Keep them in a project folder in your repo, install the command on the runner with curl -fsSL https://ofcors.dev/install.sh | sh, and run ofcors run "Your flow" --json. It exits non-zero when a step fails.
Yes. Ofcors applies the known WebKitGTK workaround for NVIDIA + Wayland automatically, so it starts cleanly without any setup.