Compare

Bruno vs FieldFlow

Bruno is an offline-first API client focused on request management, not on automatic field filtering.

Which to pick

Pick Bruno if you want…

  • Git-native API client
  • Integrations with Vault or Azure Key Vault (on Bruno's list, not FieldFlow's)

Pick FieldFlow if you want…

  • Selective field fetching for LLM agents
  • Integrations with FastAPI, httpx or Pydantic (on FieldFlow's list, not Bruno's)

Side by side

What it is
Bruno:Bruno is an open-source, offline-first API client that stores collections as plain-text files in Git.
FieldFlow:FieldFlow converts any OpenAPI-described REST API into a filtered MCP server with FastAPI routes.
Best for
Bruno:Git-native API client
FieldFlow:Selective field fetching for LLM agents
Who it’s for
Bruno:Developers and teams who need a secure, local-first API testing tool.
FieldFlow:Developers building LLM agents or apps that need field-level API responses.
Pricing
Bruno:Freemium
FieldFlow:Free
Plans
Bruno:Open Source $0 · Pro $6user/month per month, billed annually · Ultimate $11user/month per month, billed annually
FieldFlow:—
Open source
Bruno:Yes, 47,301 GitHub stars
FieldFlow:Yes, 111 GitHub stars
Works with
Bruno:Vault, Azure Key Vault
FieldFlow:FastAPI, httpx, Pydantic, OpenAPI 3.x, Model Context Protocol, Claude Desktop

Bruno features

  • Git-native collections. Store API requests as YAML files in your repo, enabling diff, branch, and merge workflows.
  • No cloud sync. All data stays on the local machine; no account or login required.
  • Multi-protocol support. Send HTTP, REST, GraphQL, gRPC and WebSocket requests.
  • Secret manager integration. Connect to Vault, Azure Key Vault and AWS Secrets Manager for credentials.
  • Built-in terminal & scripting. Run JavaScript scripts and use an integrated terminal for automation.
  • Workspace & collection runner. Organize requests in workspaces and run entire folders of requests at once.

FieldFlow features

  • OpenAPI native. Point FieldFlow at an OpenAPI 3.x spec and it auto-discovers endpoints and schemas.
  • Typed Pydantic models. Generates request/response models with full validation, aliases and nested refs.
  • Selective responses. Each route accepts a fields list so callers receive only the data they request.
  • FastAPI gateway. Proxies calls via httpx and serves filtered results through FastAPI routes.
  • Spec-first fidelity. Handles recursive schema resolution to stay aligned with the upstream API.
  • Optional MCP layer. Exposes the same filtered endpoints to Model Context Protocol clients like Claude Desktop.

Bruno vs FieldFlow FAQ

Is Bruno or FieldFlow free?+

Bruno has a free plan (Open Source) and paid plans. FieldFlow is listed as free on DevHunt.

Is Bruno or FieldFlow open source?+

Yes, both are open source: Bruno (usebruno/bruno on GitHub, MIT license) and FieldFlow (guillaumegay13/fieldflow on GitHub, MIT license).

Do Bruno and FieldFlow integrate with the same tools?+

Their integration lists don't overlap: Bruno lists Vault and Azure Key Vault; FieldFlow lists FastAPI, httpx, Pydantic, OpenAPI 3.x and 2 more.

On DevHunt

FieldFlow

0 upvotes · Launched on DevHunt on Jan 6, 2026

Based on each tool's website and DevHunt data. Details may change; check the official sites.