Bruno: Fast and Git-friendly open-source API client (Postman alternative)

Original Article ↗ Hacker News Discussion ↗

Overall Sentiment

  • Strong enthusiasm for Bruno as a fast, simple, “file-over-app”, offline-first alternative to Postman/Insomnia.
  • Significant frustration with Postman and Insomnia for forced logins, cloud-centric workflows, data loss, bloat, and “enshittification” driven by VC funding.
  • Some users remain happy with CLI/IDE-based solutions and see limited need for GUI API clients.

Why People Are Switching

  • Postman/Insomnia now often require accounts, push cloud sync, and have had rough migrations that wiped or hid collections/environments.
  • Many orgs cannot use tools that sync secrets to external clouds for compliance and security reasons.
  • Postman’s UI is widely described as slow, complex, and over-featured for “just hit an API” use cases.
  • Users value Bruno’s:
    • Local-only storage of collections.
    • Git-friendly, human-readable Bru files.
    • Easy collaboration by checking collections into repos.
    • Import from Postman collections.

Features, Gaps, and Comparisons

  • Bruno praised for:
    • Simple, fast GUI + CLI.
    • Environments, pre-request scripts, OAuth2 support, and Postman-like test flows.
    • Git-native workflow and “everything as code” philosophy.
  • Missing or weaker areas (some improving/paid):
    • WebSockets, SSE/streaming, gRPC, MQTT, cookies, mTLS, and some environment/variable scripting edge cases.
    • OpenAPI import not as robust as Postman/Insomnia, especially around server variables.
  • Comparisons:
    • CLI/text tools (curl, httpie, Hurl, JetBrains/VS Code .http, Emacs/Vim/IDE plugins) preferred by power users who like scripting, reuse, and CI integration.
    • GUI tools (Postman, Insomnia, Paw, Thunder Client, Yaak, HTTPie GUI, Hoppscotch, Restfox, etc.) still popular, but cloud lock-in and bloat are recurring complaints.

Business Model & Licensing Discussion

  • Bruno has a free open-source core plus a paid “Golden Edition” with proprietary features (e.g., gRPC/WebSockets, load testing).
  • Pricing is one-time with limited years of updates; debate over whether that is truly “lifetime” and whether messaging is misleading.
  • Many appreciate the no-VC stance and perpetual, non-subscription model; others are wary of dual-licensing and long-term openness.

Meta & Philosophy

  • Strong support for:
    • “File over app” and Git as the source of truth.
    • Tools that don’t require accounts, telemetry, or auto-updates.
  • Ongoing debate over GUI vs shell: GUIs seen as easier for less CLI-savvy devs/testers; shells and notebooks seen as more powerful and flexible for those comfortable with them.