Use this form to propose a partnership. Otukan’s partnership team and an engineer from the product you want to work with read it together and reply by email. We work with three kinds of partner: technology companies whose products live inside mobile apps or devices, channel and reseller partners who bring Otukan to their clients, and device makers building protected or managed hardware. Tell us what you offer, who buys it and which Otukan product fits. We qualify every joint project on its platforms and devices before anything is agreed or announced.
Where your offer meets Otukan
A good partnership starts from the point where your work and ours touch the same mobile flow. Pick the one that describes you in the first field of the form.
- Technology partnership. Your SDK, service or platform runs inside your customers’ apps or devices, and you want it to run cleanly next to Otukan protection or management. How SDK providers protect their own code inside customers’ apps is covered on mobile SDK protection.
- Channel or reseller partnership. You sell, integrate or operate security and mobility services, and you want to add Otukan Application Security, Device Security or Device Management to your portfolio.
- Device maker partnership. You build or source devices and want firmware-level protection engineered for your models and chipsets, or management built into the devices you ship.
If none of these fits, choose Something else and describe the idea in your own words.
What to tell us
A short, concrete description gets a more useful first reply than a general introduction.
- Product area. Application security, device security, device management or more than one.
- Your customers. The sectors and the kind of organisation you serve, without naming individual customers.
- Platforms and devices. Android, iOS, Flutter or React Native apps; the device models or chipsets you work with; or the fleets you run for others.
- Your role in delivery. Whether you would configure, integrate, operate or resell, and which part stays with the end customer.
Otukan builds each control separately for Android and iOS, and scopes device work per model and chipset. Knowing your platforms early lets us bring the right engineer to the first conversation.
Do not send customer data, device lists, binaries, source code, signing keys or credentials. In any joint project, the end customer keeps its signing keys, its release decisions and its management data.
After you send
The form confirms your request only once it has been received. If a field needs attention, it tells you which one and keeps everything you entered.
- The partnership team and a product engineer read your request and reply by email with questions or a proposed call.
- On that call we agree the scope of a first joint project: platforms, devices, who does what and what evidence the customer will see.
- Otukan confirms that scope in writing before any work starts. We name partners in public only with their written approval.
How the programme works for customers is explained on partners. For a customer enquiry about your own apps, devices or fleet, see contact.