Mobile security tooling for your team.

Equip your researchers with the tools they need to investigate mobile applications. We can provide our own tools or build new ones for your organization, all of which can run in offline environments.

For security teams that want to operate their own mobile analysis capabilities, rather than outsource an assessment.

You may already have the researchers, but their time goes into preparing devices, maintaining environments and adapting tools instead of investigating apps. And when your work must stay inside an isolated network, many tools are not an option because they depend on online services.

Our technology combines specialized tooling, Chameleon, our custom Android research environment, dedicated mobile devices and automated investigation workflows. We use that experience to identify which capabilities fit your team and what needs to be adapted or built:

  • Existing vulnit tools: the capabilities from our own research arsenal that fit your team's work.
  • Custom tool development: instrumentation, analysis utilities and automation designed around the questions your researchers need to answer.
  • Research environments: mobile device and analysis setups adapted to your workflows, infrastructure and data-handling requirements.
  • Workflow integration: connect the agreed tools to your existing investigation and evidence collection processes.

Your research environment should not need an Internet connection just to run its tools. We can design and deliver capabilities for isolated, air-gapped environments, where applications, evidence and analysis must remain inside your organization.

We define the offline requirements from the start. The tools we deliver for these environments work without external services, online license checks or outbound telemetry.

Your data does not leave your network to use AI. Our AI-assisted workflows run on language models hosted in your infrastructure. Cloud model services are also supported.

  1. Requirements: we understand which capabilities your team is missing, and the platforms, devices, infrastructure and connectivity they must work with. We agree confidentiality terms before you share details of your environment.
  2. Proposal: we send you a proposal that combines existing tools, adaptations or a custom build, with the functionality, supported environment and integration points.
  3. Development and delivery: we build or adapt the tools and deliver them through the process your environment requires.
  4. Handover: we check that the tools work as agreed in your environment, show your team how to use them and hand over the documentation.
  5. Maintenance and support: updates, fixes and support continue on the terms agreed in the engagement.

Tools that work in your environment

Checked in your environment against the functionality agreed before development.

Offline-ready delivery

Installation packages, dependencies and an update process planned around your approved transfer process.

Tool training and documentation

How to install, operate and troubleshoot each tool, so your team can use them from day one.

Agreed rights and support

Usage rights, maintenance and support defined for your engagement.

Tools we use in our own work

Our tooling comes from our own assessments and research, not from demonstrations. We know which capabilities save time in a real investigation because we rely on them.

Built by mobile security researchers

Our team specializes in reverse engineering, vulnerability research and app protections, and contributes to the OWASP Mobile Application Security project. We design tools around the questions researchers need to answer.

Isolation designed in from the start

Offline operation is a requirement we agree before development, not an adaptation after delivery.

Meet the team
Can we use your tools without commissioning an assessment?

Yes. Tooling is a separate service for teams that want to conduct their own investigations.

Can you provide tools for an air-gapped environment?

Yes. We can scope tools and research environments to operate offline. Installation packages, dependencies, activation and updates are planned around your approved transfer process, rather than assuming access to public repositories or cloud services.

Will our applications or findings leave our network?

For an isolated deployment, the agreed analysis runs locally and keeps applications and evidence within your environment. We define data flows and any support-access arrangements before delivery; external connectivity is not a prerequisite for that deployment.

Do we get access to everything on your Technology page?

Not automatically. That page describes the capabilities behind our own assessments. We identify which tools and components fit your requirements, confirm what can be provided and agree any adaptation needed for your environment.

Can you build a tool that does not exist yet?

Yes. Bring us the research problem or capability you need. We assess feasibility and agree the functionality before starting development. The engagement can be a focused utility or a broader research environment.

Does this require cloud-based AI?

No. Our AI-assisted workflows can run on models hosted in your own infrastructure. If your policies allow it, they can also use a cloud model service.

Who owns custom tools, and how are they maintained?

Ownership, licensing and maintenance are agreed in the engagement. For isolated environments, we also define how updates and fixes can be delivered through your approved process.

How is the price agreed?

It depends on whether we provide existing tools, adapt them or build new ones, the environment they must run in, including offline requirements, and the maintenance and support you need. You receive a proposal with scope, price and schedule before work begins.

Do you show our team how to use the tools?

Yes. Access to our tooling includes training on how to use the tools you receive, so your team gets the most out of them from the start. For training in mobile security techniques beyond the tools, see our separate hands-on training.

Tell us about your team, your environment and the capabilities you are missing. We reply within one business day to arrange a call.

Discuss your tooling needs

A necessary cookie remembers your choices for up to 180 days. Privacy policy.