Migrate from Bruno

Keep the Git-native workflow. Add a live, shared workspace.

Bruno's local-first, Git-native model is genuinely good for solo work. When your team wants everyone seeing the same requests and environments live — no pull required — zip your collection folder and import it directly.

Request access See the steps
Migration path

Four steps, straight from your .bru files.

What actually happens when you move a Bruno collection over.

  1. 1

    Zip your collection folder

    Bruno stores each collection as a plain folder of .bru files plus a folder.bru manifest. Compress that folder as-is — no export step inside Bruno needed, the folder on disk is the source of truth.

  2. 2

    Import the zip into HTTP Titan

    Create a workspace, then use Import → Bruno Collection and upload the zip. HTTP Titan parses the .bru DSL directly — requests, nested folders, headers, auth, and scripts carry over.

  3. 3

    Bring over your environments

    Bruno environment files (.bru under environments/) import alongside the collection — variable names and values map directly.

  4. 4

    Invite your team to the workspace

    This is the actual reason most teams make this move: instead of everyone pulling a Git repo to see the latest request changes, invite teammates to the workspace directly — same requests, environments, and results, live for everyone.

FAQ

Migrating from Bruno, answered.

The questions that come up most before a team makes the switch.

Do I need to export anything from Bruno first?

No — Bruno collections are already plain files on disk (.bru + folder.bru). Just zip the collection folder and upload it; nothing to export from inside the app.

Do my Bruno scripts carry over?

Pre-request and post-response scripts written in plain JavaScript import as-is. Bruno-specific helper APIs may need small edits to match HTTP Titan's scripting surface.

Should I keep using Bruno for solo/offline work?

If fully offline, local-only work is your priority, Bruno's Git-native model is genuinely a better fit — this isn't an either/or. Some teams keep Bruno for individual exploration and use HTTP Titan for the shared team workspace.

Is HTTP Titan open source like Bruno?

No — Bruno's core is open source and free forever. HTTP Titan is a hosted product with a free tier, built around always-synced team workspaces rather than local file storage.

Contact us

Talk to us.

Tell us about your team and what you're building. We'll get back to you.