Babylon is an open-source Swift capture client that an app links in debug builds. It sends HTTP, HTTPS, WebSocket, gRPC, and runtime trace data to Rockxy for inspection.

Does Babylon require a system proxy or CA certificate?

No. Babylon captures from inside the app and pairs directly with Rockxy, so it does not require proxy settings or a man-in-the-middle certificate.

Can Babylon capture certificate-pinned requests?

Yes. Babylon observes requests inside the app before they leave the networking layer, so certificate pinning does not block this capture path.

Does Babylon run in production builds?

Babylon is designed for debug configurations. Babylon.start() is a no-op in non-DEBUG builds, and integrations should also wrap startup in a DEBUG compilation check.

Open-source Swift capture client

Capture app traffic and runtime traces without a proxy.

Babylon links to your app in debug builds and sends HTTP, HTTPS, WebSocket, gRPC, and runtime trace data to Rockxy over an authenticated encrypted local connection.

Get Babylon on GitHub Download Rockxy

Rockxy showing app traffic and runtime trace events captured through the Babylon client — Babylon traffic appears in Rockxy’s normal inspector; correlated runtime events appear in the Runtime Timeline.

Two capture paths, one inspector

Use the proxy for apps you do not control. Use Babylon for your own app.

The capture paths run side by side and merge into Rockxy’s traffic list. Babylon adds code-level runtime context that a network proxy cannot observe.

No proxy or CA setup

Capture from inside the app without changing device proxy settings or installing a man-in-the-middle certificate.

Pinned traffic becomes visible

Because Babylon observes requests before they leave the app, certificate pinning does not block the capture path.

Runtime context beside traffic

Correlate sessions, traces, steps, marks, events, and errors with the requests produced by an app or agent workflow.

How it works

A debug package paired directly with Rockxy.

Babylon uses Bonjour discovery or a direct localhost connection, then encrypts each frame with AES-GCM using the pairing token held by Rockxy.

1
Add the Swift package
Link github.com/RockxyApp/Babylon to the app target and keep startup inside a DEBUG compilation check.
2
Pair with Rockxy
Open Babylon → Pairing in Rockxy, copy the local pairing token, and supply it from a developer-only configuration source.
3
Inspect traffic and traces
Review requests, responses, WebSocket frames, gRPC calls, timing, and runtime events in Rockxy’s native Mac interface.

Built for app and agent debugging

iOS Simulator

Connect directly over localhost and inspect app-owned traffic without simulator proxy configuration.

Physical Apple devices

Discover Rockxy on the local network from iOS, tvOS, watchOS, or macOS debug builds.

Certificate-pinned APIs

Observe requests inside the app instead of substituting the server certificate.

Agent runtime traces

See which workflow step produced a request, how long it took, and where an error entered the run.

FAQ

What is Babylon?

Babylon is an Apache-2.0 Swift capture client that sends app traffic and runtime traces to Rockxy during development.

Does it replace Rockxy’s proxy?

No. Use the proxy for apps and devices you do not control. Use Babylon for your own app; both capture paths can run together.

Does captured data go to a cloud service?

No. Babylon pairs with Rockxy over the local network and encrypts the capture frames in transit. Sharing remains an explicit user action.

Where is the integration guide?

Start with the Babylon quick start, then read the architecture walkthrough.

Add the capture path your proxy cannot see.

Install Babylon in a debug target, pair it with Rockxy, and inspect the first pinned request or runtime trace locally.

Open Babylon on GitHub Read how it works