Pricing
Scoped per engagement, during early access
Elenchia does not publish a price list yet. The platform is in early access, and engagements are scoped individually while the reporting layer is being finished with design partners.
What an engagement is priced on
| Driver | What it means |
|---|---|
| Device hours | Total time devices spend running your workflows, including AI discovery runs and deterministic replays. |
| Concurrency | How many devices run at once. This sets the ceiling on how fast a matrix completes rather than its total cost. |
| Residential egress | Whether devices need network egress from specific countries to reach geo-gated behaviour. |
| Retained evidence | Storage for screen video, traffic captures, screenshots and session backups, and how long they are kept. |
Design partners
We are working with a small number of teams who run mobile security testing today and recognise emulator false negatives as a problem worth solving. Partners get favourable commercial terms and direct influence over the findings model, the MASVS mapping and the report format.
In return we ask for real applications, real test cases and blunt feedback on output that is not yet good enough.
Frequently asked questions
Why is there no price list?
Because publishing one now would be guesswork. Elenchia is in early access and engagements are scoped individually while the reporting layer is finished. Design-partner terms are deliberately favourable in exchange for detailed feedback and real test cases.
What drives the cost of an engagement?
Three variables: device hours consumed, how many devices run concurrently, and whether per-device residential egress is required for the markets under test. Storage for video, traffic captures and session backups is the fourth, smaller, factor.
Is there a free trial?
Early-access participants get a scoped pilot rather than a self-serve trial, because onboarding an application and defining the flows worth testing is a conversation rather than a signup form.