Solo
For individuals getting started.
- / moCurrent pricing shown in app- A set number of profiles
- Single seat
- Local storage
- Full fingerprint engine
- Community support
Pricing
Plans that grow with your account count
Start free, then upgrade when you need more profiles, seats and cloud sync.
MonthlyAnnual
Team
For growing teams.
- / moCurrent pricing shown in app- Everything in Solo
- More profiles
- Multiple team seats
- Cloud sync
- Roles and permissions
- Priority support
Enterprise
For agencies and scale.
CustomTailored to your team- Everything in Team
- High-volume profiles
- Advanced access controls
- Dedicated support
- Onboarding assistance
Exact profile counts, seats and prices are shown in the app and may change. This page reflects plan structure only.
Compare plans
| Feature | Solo | Team | Enterprise |
|---|---|---|---|
| Browser profiles | Included | More | High volume |
| Fingerprint engine | Yes | Yes | Yes |
| Proxy per profile | Yes | Yes | Yes |
| Team seats | 1 | Multiple | Custom |
| Roles and permissions | - | Yes | Yes |
| Activity audit | - | Yes | Yes |
| Cloud sync | - | Yes | Yes |
| Local API and automation | By request | By request | Included by scope |
| Support level | Community | Priority | Dedicated |
Secure checkout - Cancel anytime
Payment methods to be confirmed. Placeholders shown until checkout details are final.
What changes the final quote?
Pricing conversations stay simple when the buying team knows which inputs matter.
Profiles
Profile count is the main sizing factor. Teams usually start with one market or workflow, then expand once standards are clear.
Seats
Seat needs depend on how many operators create, launch, review and maintain profiles inside the workspace.
Automation
API and scripted launch workflows belong in the Scale conversation so support and rollout expectations are clear.
Onboarding
Migration, naming rules, proxy review and permission setup can be scoped into the rollout.
FAQ
Billing questions
Need a scoped quote for your team?
Send the number of profiles, operators, markets, proxy workflow and API needs. Sales can map that into the right rollout path.