Three conversations the incumbents can't have
A partner's margin lives in the conversation the customer can't have with their existing vendor. Mirket gives you three of them.
One platform, both halves
MFA, single sign-on, self-service, privileged access, zero trust network access, the LDAP proxy and identity threat detection — one console, one directory, one audit trail. The customer running two vendors and an integration between them is your opening.
On-premise, still a first-class product
The large platforms are cloud-first, and Microsoft retired its own on-premise identity component in 2024. Every customer with Active Directory, LDAP applications and RDP/SSH servers on their own infrastructure has been told to re-architect. You can tell them they don't have to.
The identity nobody is protecting
Service accounts — the credentials applications use to bind to the directory — never change, read almost everything, and can't take MFA. Neither identity vendors nor PAM vendors cover them. It's a category with no incumbent in the account.
Ways to partner
| Model | What it means | Who it fits |
|---|---|---|
| Reseller | You sell and deliver the platform to your own customers — on their servers or from our cloud — and own the relationship end to end. | Security and infrastructure resellers with an identity or Microsoft practice. |
| Distributor | You carry Mirket for a territory and build a reseller network under you, with enablement and deal support from us. | Value-added distributors with a security portfolio and channel reach. |
| MSSP | You run identity security as a managed service for many customers from one multi-tenant console, billed monthly on usage. | Managed security providers, MSPs with a security practice, telcos and hosters. |
| Technology | Your product authenticates over RADIUS, SAML, OIDC or LDAP — we validate the integration together and publish the guide. | Vendors whose customers ask for MFA or SSO in front of their product. |
Managed service providers have their own page: MSSP partner program. Technology partners can see what's already integrated on the integrations page.
What you get
Deal registration and protection
Register the opportunity you uncovered and it stays yours to close. The process and the principles are on the deal registration page; the terms are in your agreement.
Competitive positioning
Vendor-by-vendor battlecards covering the identity and privileged-access incumbents your prospects already run — what they do, where they stop, and how to talk about the difference.
Technical enablement that's already public
Installation and upgrade guides, the reference architecture, every integration guide and every release note are on the documentation site. Your engineers can read them before you sign anything.
Proof of concept alongside you
You bring the customer; our engineers join the PoC. The platform is meant to be tested against a real environment, and we'd rather be in the room for it.
Direct access to the people who build it
A small team ships on a fast, public release cadence. When you raise something, it reaches an engineer, not a ticket queue.
Marketing material you can put your name next to
Solution briefs and datasheets written for a technical reader, with the mechanism explained rather than the adjectives.
What we look for
Partners who sell to organizations that keep part of their identity on their own infrastructure — an Active Directory, applications that authenticate over LDAP, servers reached over RDP and SSH — and who can either deliver an on-premise installation or run a managed service. A security or Microsoft-infrastructure practice helps. Geography helps too: distributor territories are agreed so partners aren't competing with each other for the same customers.
What we don't need: a minimum headcount, a certification wall, or a commitment before you've seen the product work in a customer's environment.
How it works
- 1
Tell us about your practice
The form below. Who you sell to, what you sell today, and how you'd position Mirket.
- 2
A conversation, not a webinar
We talk through your customers, your region and which way of partnering fits. If it's a distributor territory, we discuss coverage.
- 3
Agreement
Partner terms, including deal registration and pricing, set out in writing.
- 4
Enablement
A technical walkthrough of the platform for your engineers, battlecards for your sellers, and access to the material above.
- 5
Your first registered deal
You register it, we protect it, and we join the proof of concept.
Apply to partner
Tell us about your practice. We read every application and reply to each one.
Application received
A reply comes to the work address you gave. We read every application.
In the meantime: the feature matrix lists every capability with its deployment and status, and the documentation is public with no login.
