Barflare

What is Barflare?

Barflare is a Mac menu bar app for developers who want to expose local web servers through Cloudflare Tunnel without working directly with tunnel configuration files or command-line setup. It scans the machine for local web servers, including Conductor dev servers, labels them by type, and lets the user create a public HTTPS URL with a single click.

The app is designed to stay out of the way: it runs from the menu bar, has no main window, and can also surface tunnels on other machines or on a Tailscale tailnet when those systems are reachable. It uses Cloudflare Tunnels under the hood, so a Cloudflare account is required, but it supports free Cloudflare accounts and can work with the default barflare.dev domain or a user’s own domain.

Key Features

• Menu bar interface on macOS: Barflare lives in the menu bar instead of a dock app or separate window, which keeps tunnel management accessible while you work.
• Automatic local server detection: It finds local web servers on your machine and labels them by type, including common stacks such as Next, Vite, and Rails.
• Conductor workspace support: It specifically detects dev servers started by conductor.build and lists them alongside other local servers for quick access.
• One-click Cloudflare Tunnel creation: Clicking flare publishes a local server to a public HTTPS Cloudflare Tunnel URL without YAML files, CLI flags, or manual DNS setup.
• Stable per-project URLs: You can pin a slug for a project so the same public link is reused each time you flare it.
• Multi-machine and Tailscale awareness: Barflare can show tunnels running on other machines and can detect devices on a Tailscale tailnet so tunnels can be managed remotely.
• Domain flexibility: The default barflare.dev domain works without setup, and users can also point their own domain at Cloudflare and select it in the app.

How to Use Barflare

Install the app on a Mac and move it to Applications. After launch, Barflare sits in the menu bar and scans for local web servers automatically. When you see the server you want to share, click flare to generate a public Cloudflare Tunnel URL.

If you want a consistent link, assign a slug to the project so the same address can be reused. If you use Conductor or have devices on a Tailscale network, Barflare can surface those servers and tunnels in the same menu bar workflow.

Use Cases

• Sharing a local frontend or API server with a teammate: A developer can expose a local app running on localhost to a public HTTPS URL for quick review or debugging.
• Previewing Conductor-generated workspaces: Teams using conductor.build can discover those dev servers automatically and publish them without switching tools.
• Keeping a stable link for repeated demos: A project can use a pinned slug so the same tunnel URL is available across sessions instead of changing each time.
• Managing tunnels across personal machines: A user can check or flare tunnels from a different Mac when the target machine is elsewhere, including machines reachable on a Tailscale network.
• Testing web apps that need public access: Developers can temporarily expose a local Next, Vite, Rails, or similar server to test integrations, webhooks, or external device behavior.

FAQ

Does Barflare require a Cloudflare account? Yes. It uses Cloudflare Tunnels under the hood, and the source says free Cloudflare accounts work fine.

Can I use my own domain? Yes. The product page says you can point a domain at Cloudflare, choose it in Barflare, and use subdomains of your choosing.

Does it work with Conductor dev servers? Yes. Barflare detects dev servers spawned by conductor.build and lists them alongside other local servers.

Can I manage tunnels from another device? If Tailscale is installed and Barflare detects your tailnet, you can open the menu bar UI from another device on that tailnet and flare or unflare tunnels remotely.

Is there a free trial or limit information? The page says there is a 7-day free trial with no card required. It also says an unlicensed copy keeps detecting ports but will not flare new tunnels after the trial.

Alternatives

• Manual Cloudflare Tunnel setup: This is the underlying Cloudflare workflow done through configuration files or CLI commands rather than a Mac menu bar app.
• Other local tunneling tools: Products such as ngrok or similar tunnel services provide public URLs for local servers, but they typically use their own setup and interfaces instead of Barflare’s menu bar-based workflow.
• Reverse proxy or DNS-based workflows: Teams that prefer to manage subdomains, proxies, and routing directly may use infrastructure-level setup instead of a desktop app for one-click tunnel creation.
• Remote development platforms: Some teams use hosted preview or dev environments instead of exposing a local machine, which changes the workflow from local tunneling to cloud-hosted development.