Local evidence layer
Capture on your Mac. Inspect with context. Redact before sharing.
- HTTP
- HTTPS
- WebSocket
- GraphQL
- AI traffic
- Web3/RPC flows
Rockxy turns real app and device traffic into a faster debugging loop: capture the request, find the cause, replay the failure, and compare the fix—all on your Mac.
Capture on your Mac. Inspect with context. Redact with intent. Reproduce with evidence.
Released 24 Jul 2026 · v0.31.0 build 48 · signed universal .dmg · release notes · SHA256 checksum · macOS 14+ · Apple Silicon + Intel
brew install --cask rockxy
Install Rockxy directly with Homebrew · or download the signed .dmg
Built for real debugging work
Local evidence layer
One debugging workflow
Community proof
5 teams joined · Workspace beta5000+
Developers
AGPL
Open source
Mac
Native app
Built for engineers shipping at any scale
Light and dark themes
Inspect API, mobile, AI, WebSocket, GraphQL, and Web3/RPC traffic from one local-first HTTP debugging proxy, with capture, replay, rules, diffs, redaction, and shareable network evidence on macOS.
Real traffic. Local evidence. Public proof.
Apps · devices · simulators
Inspect · modify · replay · compare
Signed builds · releases · SHA256
Open source · on-device · auditable
brew install --cask rockxy
SwiftUI · AppKit · SwiftNIO
SwiftUI · AppKit · 100k+ requests
System proxy · helper · app identity
TLS · Keychain · public source
From setup to shared proof
Rockxy removes setup guesswork, keeps the failed request in context, and turns it into something you can replay, compare, and hand off.
First capture
No account setup. No remote agent. No guessing whether the proxy or certificate is the reason you cannot see traffic.
Productivity compounds
Developer
01Inspect the real request, change one variable, replay, and diff the result without rebuilding context.
Team
02Share a redacted session plus the rules, mappings, or scripts another engineer needs to reproduce it.
Enterprise
03Keep captures local while Workspace manages members, seats, and devices. Rockxy supports security and procurement review.
Capture the failing request once. Modify, replay, and diff it until the fix is clear, then share a redacted capture with the team.
Capture traffic beyond the browser: desktop apps, CLIs, services, simulators, mobile devices, WebSocket sessions, GraphQL APIs, model calls, and RPC endpoints. Rockxy keeps the full request trail on your Mac.
Read our documentationInspect network traffic from iOS
Guided setup for iPhone, iPad, and iOS Simulator is planned so mobile traffic can join the same Rockxy capture timeline.
Turn noisy sessions into signal. Combine method, host, status, header, body, process, and full-text filters to find the request that explains the failure.
Read our documentation
Your AI coding tool can list captured flows, inspect request and response data, replay a request, and compare two flows through Rockxy's local MCP—without copy-pasting traffic into chat.
Works with your favorite AI tools
China AI ecosystem
Coming soonPlanned coverage includes DeepSeek, Qwen, Kimi, Doubao, and GLM. Each integration will be marked available after its MCP or AI workflow is validated.
Use Rockxy MCP with Claude by Anthropic, ChatGPT by OpenAI, Gemini by Google, Cursor, GitHub Copilot by Microsoft, and other MCP-capable AI coding tools.
Pick your runtime, client, browser, container, or device. Copy the right proxy setup and run Run Test instead of debugging the debugger.
Read our documentation
A P-256 ECDSA root CA generated on first launch, sealed in your Keychain. Decrypt HTTPS on the first try; pinned hosts pass through automatically.
Read our documentation
Pick which hosts get TLS decryption. Decrypted traffic shows real headers and JSON; everything else passes through encrypted. Wildcard rules let you scope by domain in one click.
Read our documentation
Skip specific hosts so cert-pinned apps, internal services, or noisy telemetry never enter the capture. Wildcards keep the list short and your request log focused on what you actually care about.
Read our documentation
Block any host to test how your app handles a missing API, tracker, or third-party dependency—no code change or redeploy.
Read our documentation
Serve a saved file or a directory tree in place of a live response. Swap a JSON payload, replay a snapshot, or pin a flaky third-party API to a local copy while you debug.
Read our documentation
Send a captured request to staging, localhost, or a teammate's machine without changing app code or /etc/hosts.
Pause a request or response, edit it, and continue. Test a 401, bad payload, or missing header without waiting for backend changes.
Read our documentation
Add, remove, or replace headers without redeploying. Test CORS, auth, and cache behavior against live app traffic.
Read our documentation
Override headers per host with full control over both phases. Inject auth tokens on outgoing requests, strip Set-Cookie on responses, or pin a custom User-Agent — saved as named rules you can toggle anytime.
Throttle to 3G, EDGE, LTE, WiFi, or a custom delay. Your laptop is on fiber; your users aren’t — see the UX at 400 ms RTT before they do.
Read our documentation
Reopen the exact failed request, change only what matters, and send it again from the same capture. No manual reconstruction, no lost context.
Read our documentation
Compare status, headers, JSON, body, and timing in place. See what changed between the failure and the fix without exporting payloads.
Read our documentation
Render request and response bodies the way you want. Pin extra tabs to the inspector for JSON, GraphQL, JWT, image, or your own format — reusable across every captured request.
Read our documentation
Package the evidence: saved sessions, HAR import/export, cURL, JSON, raw request bodies, and response bodies. Redact authorization headers, cookies, and bearer tokens before you hand off a working bug repro.
Read our documentation
Keep staging, production, and device captures in separate tabs, each with its own filters and inspector state. Switch targets without losing your place.
Read our documentation
JS hooks on requests and responses for the cases a static rule can’t cover — redact PII, sign tokens, rewrite payloads. Errors surface inline instead of corrupting traffic.
Read our documentation
Planning board
Public direction, date-free until shipped.
Multiplexed traffic, readable evidence
Separate streams, timing, headers, and response behavior so HTTP/2 debugging feels as clear as single-request HTTP debugging.
Planning board
Public direction, date-free until shipped.
Streaming sessions with a readable trail
See connection open, message bursts, payload changes, latency spikes, and shutdown behavior without losing the session context.
Planning board
Public direction, date-free until shipped.
Device setup with verification built in
Guide the Mac, simulator, and mobile device through proxy and certificate setup, then confirm the first captured request.
Planning board
Public direction, date-free until shipped.
Share proof without sharing too much
Keep the request, response, diff, redaction state, and export trail together so another engineer can reproduce the bug safely.
Planning board
Public direction, date-free until shipped.
From captured traffic to API shape
Use real request and response examples to produce reviewable schema references while keeping sensitive payloads redacted.
A native macOS HTTP/HTTPS debugger with public source, public releases, and a local-first workflow.
Ask about selected captures, compare responses, explain failures, and turn a real request into a replay or test without leaving Rockxy.
BYOK is coming soon.
Follow the roadmap
AI-assisted debugging
100% free and unlimited in the Free tier. No license upgrade required.
Let your AI coding tool inspect, replay, and compare captured flows without manually pasting requests into chat.
Works with your favorite AI tools
Compare with context
Put the failed flow beside the fixed one. Rockxy highlights status, header, body, and timing changes in place.
Build, send, and inspect
Start blank, import cURL, or reopen history. Edit and resend the request beside the response you are debugging.
Reopen, duplicate, edit, and resend earlier requests without rebuilding the request from scratch.
Paste a cURL command to populate the method, URL, headers, query values, and body in one step.
Configure methods, URLs, headers, query parameters, and request bodies in one focused Rockxy workspace.
Paste or update multiple headers and parameters together when repetitive field editing slows the test loop.
Open WebSocket connections, send messages, and inspect the session without switching away from Rockxy.
Review the complete outgoing request and the formatted response side by side as soon as it returns.
What's more?
Follow one failed request from live traffic to a verified result without rebuilding it in another tool.
Live traffic
See HTTP, HTTPS, WebSocket, and GraphQL traffic from apps, services, and CLI tools in one session.
Find the cause
Filter the noise, then read headers, bodies, cookies, timing, and TLS details beside the selected request.
Test a change
Change one variable with headers, rules, breakpoints, or scripts—without rebuilding or restarting the app.
Send it again
Route the captured request to another endpoint with Map Remote, then replay it without rebuilding the request.
Connection handling
SwiftNIO's non-blocking event loop handles thousands of in-flight connections without spawning per-request threads.
TLS termination
Security.framework generates a per-host leaf certificate signed by a local root CA. The private key never leaves the macOS Keychain.
UI updates
Captured transactions are batched on a background actor and published to SwiftUI every 100 ms — keeping the main thread free under heavy load.
Privileged helper
A launchd daemon registered via SMAppService handles system proxy changes with zero password dialogs after one-time approval in System Settings.
XPC security
Every XPC call is validated by two independent checks — certificate chain comparison and bundle identity verification via SecRequirement. Both must pass.
Crash recovery
If Rockxy exits unexpectedly, the helper daemon auto-restores your original proxy settings from a backup plist. A watchdog monitors the app process every 2 seconds.
The stack is part of the product story: native frameworks for Mac UX, SwiftNIO for the proxy engine, and public source so teams can inspect the implementation.
SwiftNIO
Async networking engine. Handles thousands of concurrent connections on a non-blocking event loop — no thread-per-connection overhead.
SwiftUI + AppKit
Native Mac UI with a virtual-scrolling NSTableView — renders 100k+ rows by keeping only visible cells in memory.
Security.framework
Per-host TLS leaf certificates, signed by a local root CA. The root CA private key is stored in the macOS Keychain — never written to disk.
XPC Services
Privileged helper process isolated via XPC. Every connection validated with certificate-chain comparison before any proxy operation runs.
Implementation notes from building Rockxy.
A walkthrough of the per-host certificate chain, how the root CA private key stays in Keychain, and why your browser still shows a green padlock.
Why NSTableView with an NSViewRepresentable bridge outperforms a native SwiftUI List by 40x at 100k rows, and the batching strategy that keeps the main thread at zero.
Network.framework abstracts away the connection pipeline we need to intercept. SwiftNIO gives us channel handlers we can insert at the byte level — the only place MITM proxying works correctly.
Available now
Filter model calls, streaming events, tool use, blockchain methods, transaction intent, and RPC errors in the same local inspector.
AI traffic inspection
See provider, model, streaming events, tool calls, retries, and rate-limit failures beside the captured request and response.
Read our documentation
Web3 and RPC traffic inspection
See the chain, method, transaction intent, and protocol error, then replay or compare the underlying JSON-RPC request.
Read our documentation
Public direction
Rockxy Tutorials
Set up a local proxy, trust the certificate, inspect decrypted requests, and understand pinned-domain limits.
Read tutorial Mobile appsCapture API calls from iOS Simulator, Android emulator, and physical devices without adding temporary logs.
Read tutorial Backend devRoute axios, Node core, and got traffic through Rockxy so auth, retry, TLS, and payload bugs are visible.
Read tutorialMobile debugging guides
Capture traffic from mobile devices with Rockxy setup guidance for physical devices, simulators, and emulators. Manual setup is available now; guided automation remains on the roadmap.
Route iPhone and iPad traffic through Rockxy, install certificate trust, and verify the first captured request.
Guided workflowFollow proxy and trust guidance for Simulator traffic, then validate that requests are reaching Rockxy.
Manual setupConfigure the device proxy and Android trust rules, then inspect the HTTP and HTTPS flows that reach your Mac.
Reusable setupConnect the emulator to Rockxy on the host Mac and keep the proxy, certificate, and validation steps together.
Developer Setup Hub
Choose a runtime, client, framework, device, or environment. Rockxy gives you the relevant proxy and certificate steps, reusable snippets, and a local validation path.
Set up Python, Node.js, Go, Rust, Ruby, and Java clients with copy-ready proxy and CA guidance.
Keep cURL, Firefox, Postman, Insomnia, and other client-specific proxy and trust steps in one place.
Follow the correct path for Flutter, React Native, physical devices, simulators, and emulators.
Configure Docker, Electron, Next.js, and local environments, then run a probe to confirm traffic reaches Rockxy.
Coming soon
Rockxy in public
Audit the code, check the AGPL-3.0 license, and inspect the project structure before you install anything.
The release page shows versioned assets, release notes, build number, and publish date in public on GitHub.
Read the privacy policy, then compare it against the product architecture and the public code to see how traffic stays on-device.
Review how certificate handling works, what lives in Keychain, and how the proxy model is implemented on macOS.
“Will try it for future projects looks promising”
“It’s normal now! Thank you for fixing it!”
“Nice tool! Does it work well with Android/iOS Simulator for capturing HTTP/HTTPS traffic out of the box?”
“I’m not a native macOS user, but this is truly a great repo. I’ve already starred it.”
Native macOS. Open source. Local-first.
Capture once. Inspect, modify, replay, and compare in one native Mac app. Export only the redacted evidence your team needs.
Backed by the community
Sponsorships fund development and keep it that way.
Keep the unused value of a paid debugging-tool license, validate Rockxy beside your current tool, and roll out only after your must-pass workflows succeed.
25% off
First eligible Rockxy Pro purchase
Up to 12 months
Unused Team license time offset
A controlled migration path
Fit
Confirm seats, renewal date, constraints, and three must-pass workflows.
Baseline
Agree on the setup, evidence, and success criteria before testing.
Parallel pilot · 2–4 weeks
Use Rockxy beside the current tool. No forced cutover.
Decide
Review evidence and choose go, pause, or “not yet.”
Roll out
Apply the verified offer and onboard one team at a time.
Rockxy Developer Partner Network
Join the people and companies helping developers adopt Rockxy in real projects.
For individuals
Creators, consultants, and instructors can show reviewed work, get a Rockxy technical contact, and receive inquiries matched to their skills.
Build your partner profileFor companies
Tool companies, agencies, software houses, and schools can give customers a clear way to evaluate their Rockxy experience.
Join as an organizationFor resellers
Resellers and distributors can discuss territory, deal ownership, margin or revenue share, procurement, support, and renewals in a signed agreement.
Discuss a reseller agreementQuestions, bugs, and team evaluations all go through the same public channels. Reach out if you want to try Rockxy in a real workflow.