Buoy ships 15+ tools inside your React Native or Flutter app — and lets your developers add their own. Devs stop rebuilding to add a log. QA triggers error states in one tap. Support impersonates the customer who's stuck.
$ npm i @buoy-gg/core
import { FloatingDevTools } from '@buoy-gg/core'
<FloatingDevTools /> // the whole team, on devicefree forever on device · $9/mo for desktop & MCP · no account to start

one session · phone, desktop & agent · nothing leaves your machine
shipping in production apps at

One install puts the same menu in front of your whole product team. Pick a seat and see what changes.
today
A bug only happens in production. You add a console.log, ship a build, wait, and guess again.
with buoy

Register any React component in the same on-device menu. A refund button for support, an order-state switcher for QA, a flag panel for product — shipped with the app, gated however you like.
<FloatingDevTools
customTools={[
{
name: 'Refund',
component: RefundPanel,
icon: '💸',
},
]}
/>
// now support has a Refund button
// in the same menu, on their phoneThe tools run inside your app's process. A small broker on your machine mirrors them to the desktop app and hands them to any MCP client as real tool calls — never through our servers.
One component, and every installed tool appears in a dial on the device. No cable, no desktop app, no proxy, no certificate — which is why QA and support can use it without help.
free foreverBuoy Desktop mirrors the same session to macOS, Windows and Linux, with a live perf HUD. Devices connect on their own — physical phones included.
Pro · free downloadThe MCP server hands your agent real tool calls against the live app. It reads the state, taps the UI, and reproduces the bug itself.
Pro · npx @buoy-gg/mcp initEvery one is its own package, and every one streams to all three surfaces. These are real captures from a real app.
@buoy-gg/networkEvery request the app makes — headers, bodies, timings — without a proxy, a certificate, or a rebuild.


Buoy's MCP server gives Claude Code, Cursor, or any MCP editor real tool calls against the running app — structured state in, actions out. No pixel-guessing, no copy-pasting logs into a chat window.
npx @buoy-gg/mcp init{ "error": "TAX_RATE_NULL",
"region": "CA-QC" }● Quebec tax rates are missing from the config — here's the fix.
The bugs that matter are the ones you can't reproduce locally — and the people who hit them first are usually support, not engineering. Buoy runs where they are, and one condition in your own code decides who sees it.
import { FloatingDevTools } from '@buoy-gg/core'
<>
{/* your app */}
{user.isStaff && <FloatingDevTools />}
</>Not a roadmap — this is what's in the packages today, across all three surfaces.
You know Flipper, Reactotron and RN Debugger. Here's why teams move.
| feature | buoy | flipperarchived | reactotron | rn debugger |
|---|---|---|---|---|
| Still maintained in 2026 | ||||
| On-device — no desktop app required | ||||
| Usable by QA & support, not just devs | ||||
| Add your own custom tools | ||||
| Works in production builds | ||||
| AI agent control (MCP) | ||||
| Live perf HUD (FPS / CPU / memory) | ||||
| Zero-config setup | ||||
| Network inspector | ||||
| Query cache (TanStack) |
Full write-ups: Buoy vs Flipper · Buoy vs Reactotron · the best RN debugging tools in 2026
Plays nice with your stack: Sentry and PostHog tell you what broke. Buoy lets anyone on the team reproduce it on a live device — the exact request, state and route.
The in-app tools are free for your whole team — devs, QA and support alike. Individuals pay $9/mo for the desktop dashboard and agent control; companies license per seat.
Every tool, inside your app, for everyone who installs the build.
Adds the desktop dashboard, agent control, and production builds.
The same tools on a company license — priority everything included.
volume pricing from 10 seats · cancel anytime · no credit card to start
No. Everything is taps inside the app — force a loading state, edit a value, impersonate a user, jump to a screen. The only person who touches code is the developer who installs it once.
Yes. The Impersonate tool injects impersonation headers into every network request, so the app behaves as that user without anyone logging out or sharing a password. You wire it to your own user-search API, so your rules and your auth decide who can do it.
Yes, and this is where most teams get the biggest win. Register any React component in the customTools array and it appears in the same on-device menu — a refund button, an order-state switcher, a flag panel.
Yes. Buoy runs entirely on-device and never phones home. Gate it behind your own flag so only staff see it — or strip it from release builds entirely.
No. The network tool runs inside your app’s process, so there is no proxy to configure, no root certificate to trust, and nothing to set up on the device. That is what makes it usable by non-engineers.
Never. The in-app tools are free forever for as many people as you like. You only pay for the desktop dashboard, agent control and production debugging — $9/mo for individuals, per-seat for companies.
Nothing leaves the device by default. The desktop app and MCP server connect over a local broker on your own machine — never through our servers.
The Flutter suite is in beta and streams to the same desktop dashboard and MCP server as React Native.
A developer adds one component. From then on everyone who ships your app — engineering, QA, support — can see it and change it while it runs.
$ npm i @buoy-gg/core
import { FloatingDevTools } from '@buoy-gg/core'
<FloatingDevTools /> // the whole team, on devicefree forever on device · Pro 14-day trial · cancel anytime
or download Buoy Desktop for macOS, Windows & Linux