Qualifying Team migrations keep the unused value of a paid license. Individual developers can claim a 25% switch discount.
First prove Rockxy on real workflows. Roll out only when your team is ready.
For individual developers, startups, and engineering teams. Eligibility and offer terms apply.
AGPL-3.0 core
Public source
Native macOS
Not Electron
Local-first
No core cloud account
$9 / seat / month
Yearly · 3-seat minimum
14-day refund
Paid licenses
Commercial protection
A renewal date should not trap your team in the wrong tool. Rockxy uses two clear offers to remove the overlap cost.
Individual switch discount
25% off
Show a current paid license for an eligible competing network debugging tool. We will provide a one-time switch discount after verification.
The discount is calculated from the listed checkout price when approved. If another public Rockxy offer is lower, you receive the lower eligible price—not two stacked promotions.
Best for individual developers.
Full program terms →Team license bridge
Up to 12 months
Buy a new annual Rockxy Team term and we will add the verified unused whole months from your current paid tool—up to 12 months—for the same number of eligible seats.
Your old contract stays with its vendor; Rockxy adds time after the initial annual term, moving the first renewal date so the overlap is not wasted.
Full program terms →Prove the work, not the demo
The pilot scorecard is built around the jobs your developers perform today. Rockxy does not claim automatic import of proprietary settings from another tool.
A step-by-step migration, not a leap of faith
Keep the old tool available during evaluation. Move forward only when Rockxy passes the criteria your team agreed to.
Share the current tool, seats, renewal date, constraints, and three workflows Rockxy must not break.
Exit gate: the pilot scope and commercial eligibility are understood.
Rockxy delivers
Pilot brief + offer eligibility
Map certificates, devices, protocols, filters, team policies, and the current workflow before testing.
Exit gate: both sides agree on must-pass criteria and how results will be recorded.
Rockxy delivers
Fit matrix + pass/fail scorecard
A representative group uses Rockxy beside the current tool on real captures. No forced cutover.
Exit gate: every must-pass workflow has evidence or a documented blocker.
Rockxy delivers
Evidence log + blocker register
Review every requirement and classify gaps as supported, configuration, product candidate, scoped custom work, or not a fit.
Exit gate: the team chooses go, pause, or “not yet” with no unresolved blocker.
Rockxy delivers
Decision record + gap disposition
Apply the verified migration offer, onboard one group at a time, and keep a rollback path through the first checkpoint.
Exit gate: the first wave passes and another developer can repeat the setup from the checklist.
Rockxy delivers
Rollout plan + onboarding checklist
Have a real workflow ready to test?
Start with the tool, seats, renewal date, and three must-pass workflows. We will reply with eligibility questions and the next step.
What Rockxy commits to
A requirement-by-requirement view of what works now and what does not.
Help with proxy setup, certificates, devices, and repeatable onboarding.
A direct path to the people building Rockxy for pilot findings and questions.
Links and technical context so reviewers can inspect the public core and document open questions.
An explicit decision for each blocker—no vague promise that everything is “on the roadmap.”
When custom work is the right answer, scope, timing, ownership, and cost are agreed before work starts.
Trust that can be checked
Rockxy's public core is AGPL-3.0. Your engineers can inspect the source, build it, trace changes, and raise technical questions publicly. Open source is not a security certification—but it gives your reviewers evidence access that a black box cannot.
Paid components, licensing infrastructure, and optional Workspace services are governed separately and are not represented as open source.
Migration questions
Yes. The pilot is intentionally parallel. Your current tool remains the rollback path until the agreed workflows pass and your team chooses to proceed.
Rockxy verifies the remaining whole months and eligible seats from the current paid license or maintenance term. Approved time—up to 12 months—is added after the first paid annual Rockxy Team term.
After the initial fit check, Rockxy may request a redacted invoice, receipt, or license record showing the vendor, paid status, seats, and expiration or maintenance end date. Do not send payment details, license keys, or confidential captures.
The program stops at the decision gate. You still receive the evidence and gap disposition, including what works, what needs configuration, what requires separate scope, and what is not supported.
No. The public core is AGPL-3.0 and can be inspected and built from source. Paid components, licensing infrastructure, and optional Workspace services are governed separately.
Program terms