Workspace beta

Debug together without giving up local-first control.

Capture on the Mac. Redact secrets before upload. Share a browser link with the exact scope: public, team-only, or selected teammates.

Workspace is optional. The proxy, TLS interception, filtering, and first review still run locally in Rockxy.

api-login captureTeam only

12 redacted fields · 2 reviewer notes

Local review first

Inspect and redact before a capture leaves the Mac.

Browser handoff

Send one link instead of screenshots, HAR files, or a screen share.

Clear access state

Every shared capture shows who can open it.

Review in a browser

A shared capture should still feel inspectable.

The viewer keeps the important debugging context together: request list, selected request, headers, body, timing, and redaction status.

6 requestsRockxy

POST /api/auth/login

200 OK · 120 ms

GET /api/users/me

200 OK · 45 ms

DELETE /api/session

204 · 34 ms

POST 200 OKTeam only2 notes

https://api.rockxy.io/api/auth/login

Request body

{ "email": "[member-email]", "token": "[redacted]" }

Reviewer note

Looks like the refresh token expired before retry. Check device clock drift.

Share with scopes

No guessing who can see the capture.

Workspace makes the access decision visible before sharing. That is the useful part: fewer side channels, fewer accidental raw files.

Public link

For bug reports

Anyone with the link can inspect the sanitized capture.

Team only

For internal APIs

Only members of the Rockxy Workspace can open it.

Selected users

For narrow review

Invite a teammate or contractor without opening the whole workspace.

Owner

Workspace and billing

Creates the workspace, manages billing, and archives shared captures.

Admin

Members and defaults

Invites teammates and sets retention or default access rules.

Member

Share and review

Uploads sanitized captures and reviews links from the team.

Guest

Explicit access

Opens only the captures that were shared with their email.

Privacy model

Say exactly where the boundary is.

Rockxy should not imply enterprise certifications or customer logos it does not have. The promise is narrower and more useful: local capture, local review, deliberate sharing.

Local-first capture

Traffic interception and initial inspection stay in the native macOS app.

Redaction before upload

Sensitive headers, cookies, tokens, and fields are reviewed before sharing.

Visible access scope

Every capture states public, team-only, private, or selected-user access.

Activity trail

Shared captures can show who created, viewed, updated, or archived them.

FAQ

Short answers for careful teams.

Does Workspace replace local capture?

No. Rockxy still captures and inspects traffic locally first. Workspace is for sharing sanitized evidence when another person needs to review it.

What gets uploaded?

Only the capture you choose to share. The review step should make redacted headers, cookies, tokens, and selected fields visible before upload.

Can Workspace stay optional?

Yes. The core proxy workflow remains local-first. Workspace is an optional collaboration layer for teams.

Ready to try the Workspace flow?

Open Workspace to review the current direction, or use GitHub discussions to shape the sharing model.