You don't need one to use Harpax. The app is local-first — it runs entirely on your machine with no sign-up. The only place a Cambric account comes in is billing: if you're on a paid plan, you manage it from a lightweight account at cambric.ai/account, completely separate from the app itself.
Why there's no sign-up
Harpax is designed around a local-first principle: the sessions it captures, the detections it runs, the rules it loads, and the configuration it stores all live on your machine, under your user account, in a directory you control (~/.harpax/). There is no cloud backend that needs to authenticate you, no shared workspace to provision, and no per-seat license to validate.
To run the app, there's nothing to sign up for — download it, install it, and you're done. (Paid-plan billing is the one exception — see below.)
What "local-only" means in practice
- No email or password. Harpax doesn't ask for credentials at install time and doesn't store them.
- No identity service. The daemon's internal "identity" is a fixed magic string baked into every Harpax binary, used only so the GUI can verify it's talking to a real Harpax process on your loopback interface. It is not a user identifier and nothing about it is transmitted off your machine.
- No multi-device sync. Sessions, rules, allowlists, and config don't sync between machines — each install is its own independent universe. (If you want your custom rules on a second machine, copy the files manually.)
- No usage telemetry, by design. The app doesn't phone home. Paid-plan billing is the one place a Cambric account exists (see below), and it only ever touches plan and payment data — never your sessions.
Where your data actually lives
Your "Harpax universe" on a given machine is everything under ~/.harpax/:
~/.harpax/sessions/— captured session JSONL files~/.harpax/rules/— your custom JavaScript detection rules~/.harpax/allowlist.yaml— patterns you've approved~/.harpax/config.yaml— your settings~/.harpax/logs/— daemon logs
Back up that directory and you've backed up your install. Delete it and you've reset everything. No remote service is involved.
Install Harpax on the new machine, then copy ~/.harpax/rules/, ~/.harpax/allowlist.yaml, and ~/.harpax/config.yaml from the old machine. Sessions are large and machine-specific — most people leave them behind.
What about contacting Cambric AI?
Reaching out for support, sending feedback, or asking about a custom deployment doesn't require an account either. Use any of these channels:
- The service desk at cambric.atlassian.net/servicedesk — create a ticket without signing up if your email is sufficient
- Email [email protected] for general feedback
For details, see How do I connect with the Cambric team?
What about paid plans?
Paid Harpax plans do have a lightweight Cambric billing account — but it's separate from the app and covers billing only. Access it at cambric.ai/account by signing in with your email (we verify by email; there's no separate password to manage). From there you can view your plan, change plans, update your payment method, see invoices, and cancel.
That billing account never holds your Harpax session data — that stays local on your machine, as described above. The app is local-first and account-free; billing is just a thin record of your plan and payments.
To cancel or switch plans, see How do I cancel my Stripe subscription?