Commercial supply is offered only where the vendor, territory, product, delivery and support terms are confirmed in writing.
Start with the requirement
The right tool depends on the devices and evidence questions in front of your team. A large compatibility number does not tell you whether a method works on your device population or produces the artifacts your examiners need.
Before recommending a product or licence, we document:
- the Android and iOS devices, versions and states you expect to encounter;
- available credentials and permitted acquisition methods;
- applications and artifact classes that matter to the work;
- expected case volume, examiner roles and review process;
- deployment, storage, access-control and network constraints;
- reporting, export, validation and support requirements.
This becomes the basis for evaluation and procurement. It also records what the proposed tool is not expected to cover.
How we evaluate a requirement
The evaluation plan identifies representative devices, acquisition conditions, known data and required outputs. Record successful and failed methods, prerequisites, device-state changes, parser behaviour, timestamps, source references and export quality. Vendor claims remain separate from results reproduced in the client environment.
Before purchase, confirm workstation, storage and network requirements, licence administration, updates, user access and evidence movement. The proposal should also name who handles installation, workflow questions and vendor escalation.
What to compare
| Area | Questions to answer |
|---|---|
| Acquisition | Which methods are supported for the relevant model, OS, state and credentials? What prerequisites and device changes apply? |
| Analysis | Can the examiner trace a parsed item to its source? How are timestamps, deleted records and unsupported artifacts handled? |
| Reporting | Can the team produce the exports, references and technical detail its reviewers require? |
| Security | Where is evidence processed and stored? Which users, services or vendor systems can access it? |
| Operations | What hardware, network access, updates, validation and operator skills are required? |
| Support | Who owns first response, technical escalation, replacement, renewal and end-of-life communication? |
Products and availability
Zeno Forensics will publish only products and hardware that it is authorised to supply. Current availability, licence terms, delivery territory and support scope will be confirmed during the enquiry.
No product will appear as available until written rights, a current SKU and a named support owner are in place.
For procurement teams
Ask for a proposal that states:
- product, edition, licence metric and term;
- OEM authorisation or manufacturer-authorisation-form availability where required;
- GeM or other procurement-portal status, or confirmation that the product is not listed there;
- included modules, hardware and accessories;
- delivery method, installation site, import responsibility and expected lead time;
- implementation, paid proof-of-concept and acceptance scope where applicable;
- training seats included with the purchase;
- hardware or dongle custody, replacement and return conditions;
- warranty, updates, renewal and annual-maintenance terms;
- first-line support and vendor-escalation ownership;
- exclusions, dependencies, taxes and commercial validity.
Request a licensing discussion
Questions buyers ask
Do you resell mobile forensic software and hardware?
We supply only products and SKUs covered by current written commercial rights. Ask us for the current catalogue and territory. If a requirement falls outside that scope, we will say so.
Which mobile forensic tool is best?
There is no universal choice. Send the representative device, OS and application list with the required outputs. We will state what can be tested and where a second tool or manual review may be needed.
Can you prove that a tool supports our devices?
A current vendor matrix is a starting point. For a material procurement, use representative devices and known data to test the methods and outputs that matter to your team. Coverage can change with device, OS, security patch, state and credentials.
Do you support tools bought from another vendor?
Only where the work and escalation rights are agreed. We will not present ourselves as a vendor support channel when we do not hold that role.
Can training be included with implementation?
Yes, where an approved course and qualified instructor are available for that product. Product enablement is not an OEM certification unless the OEM authorises the curriculum and credential.
Can you provide an OEM authorisation letter or MAF?
Only where the manufacturer or authorised channel has issued the required document for the product, territory and procurement. We will confirm document availability before participating in a bid or technical evaluation.
Are the products available on GeM?
GeM status will be stated for the specific SKU and seller. If a product is not listed, the proposal will identify the available procurement route rather than implying portal availability.
Can we run a proof of concept on representative devices?
Where the vendor, licence and security conditions allow it, a paid evaluation can be scoped around agreed devices, known data and acceptance criteria. A demonstration is not a promise of support for every device state or future software version.
Who handles a failed dongle, renewal or technical escalation?
The proposal will separate Zeno’s first-line role, hardware replacement, licence administration and OEM escalation. Response times and exclusions must be agreed in the commercial terms.
Final call to action
Tell us what the tool must cover
Tell us about the devices, work, environment and team. We will identify what needs to be evaluated before a commercial recommendation can be made.