Pay for reach, not for runs.
Unlimited installs and unlimited executions on every tier — including the free one — because execution happens on your machines and costs us nothing. What you pay for is how far your skills are allowed to travel.
Free
Prove it works, on one machine
Free/ forever
- 1 seat
- 1 machine
- 1 Conxa Execute seat
- 25 compile credits/month
- 500K AI Usage Credits/month
- Internal distribution only
- No ops dashboard
- No analytics retention
Starter
Run it across your team
₹19,999/ monthly
- 3 seats
- 3 machines
- 25 Conxa Execute seats
- 200 compile credits/month
- 2M AI Usage Credits/month
- External distribution, Conxa-branded
- Basic dashboard
- 90-day analytics retention
Pro
Ship it to your own customers
₹49,999/ monthly
- 10 seats
- 10 machines
- 100 Conxa Execute seats
- 500 compile credits/month
- 10M AI Usage Credits/month
- External distribution, Conxa-branded
- Full dashboard, drift detection, audit export
- 365-day analytics retention
Enterprise
Ship it under your own brand
Custom/ contract
- Seats agreed per contract
- Machines agreed per contract
- Conxa Execute seats agreed per contract
- Unlimited compile credits/month
- Contracted AI Usage Credits reserve
- External distribution, white-label
- Full dashboard, drift detection, audit export
- Custom analytics retention
- Bring your own key (Azure OpenAI)
Compile credit
One fresh compile through Conxa Cloud consumes one credit. Recording, editing, and testing workflows locally stay unlimited on every tier — only turning a workflow into a runnable skill draws from the pool.
Unlimited runs per install
Execution is local. Once a skill is on a machine, running it costs nothing extra — on any tier, at any volume.
Model access by tier
Free runs on a Conxa-hosted open model at no cost. Starter and Pro compile on managed premium models we pay for and include in the price. BYOK is an Enterprise option, for teams that need their own key for compliance or cost control.
Human Edit credit
Token pool for selector repair, semantic repair, and re-anchoring after a compile — separate from the compile credit that creates the workflow in the first place.
Before you ask.
The questions every enterprise team asks ahead of a demo.
Where do our logins and credentials live?
On your machine, encrypted in the operating system keychain. They are never sent to Conxa and never included in published skills.
Do you run our workflows in your cloud?
No. Execution is 100% local. Our cloud only hosts, versions, and coordinates skills — it has no way to run them.
What data does Conxa receive?
Compact event signals only: a step succeeded, recovered, or failed, and when. No screenshots, no page content, no personal data.
What happens when the software's screen changes?
Each step knows its target several ways — its text, its role, its position, how it looks. Most changes are handled on the spot at zero AI cost. Harder cases get an assisted fix, and drift shows up on your dashboard so nothing breaks silently.
Do we need engineers to create a skill?
No. Anyone who can do the workflow can record it. You demonstrate it once in a real browser — no scripting, no setup.
What software does it work with?
Anything that runs in a browser: Salesforce, SAP, cloud consoles, and the internal tools that never got an API.
Why not just build an API for the system we need to connect to?
For the one system you own, that's often the right call. It's not true for the other four systems in the process that you don't control, and it's not true for the long-tail workflow that's too small to ever get its own sprint. We can put a number on it: the hours this process costs you per month against what building and maintaining five integrations would take, versus recording it once.
What if the software we need to automate blocks bots or requires MFA?
We check before we promise. Aggressive bot protection targets datacenter traffic, not an employee's own machine on a corporate IP in a real browser — most line-of-business software has none of it. A fresh one-time code on every login is the one thing that genuinely can't be automated unattended, so we screen for MFA policy, bot protection, terms of service, and session lifetime before any workflow is qualified.
How is this different from Comet or Claude in Chrome?
Different category, not a better version of the same one. Those assistants rediscover the interface every run — per-session, non-deterministic, token cost each time — which is right for a person doing a one-off task. Conxa compiles a workflow once and replays it deterministically, with recovery, for a process that runs unattended a thousand times.
What platforms are supported?
Windows today. macOS is on the roadmap.
How does pricing work?
You pay to build and publish skills. Running them is free and unlimited — your cost doesn't grow with usage.
What if Conxa's cloud goes down?
Your skills keep running locally. Only new skill updates wait until the cloud is back.
Do you have SOC 2 or similar certifications?
Not yet — we're early. But our architecture keeps sensitive data on your machines, so most of it never reaches us in the first place.
See it on your own software.
Record your first workflow in minutes — or walk through it with us on the tools your team uses every day.