Partners
Run Nmonic for your partners or your customers.
Nmonic is an on-device meeting copilot. We hand it to partners free, gated to their verified email domains, and roll up the usage so partner ops can see who's actually using it. Four shapes fit under one program: a referral partner who sends customers our way for a cut, a reseller who sells managed Nmonic into their own book, a systems integrator who bundles it into a security or productivity engagement, and an MSP who runs it for their managed customers as part of the stack. Referral and MSP are the shapes we've built most against. Reseller and SI are aspirational — we'll wire them up the moment a credible partner asks.
i. The four shapes
Referral — built
You send your customers or your network at us. We attribute the activation to your domain and pay a referral cut on managed conversions.
Reseller — aspirational
You sell managed Nmonic as a line item inside your own quote, on your paper. We bill you wholesale; you bill your customer retail.
Systems integrator — aspirational
You're delivering a security or productivity engagement and want Nmonic embedded as the copilot layer. We provision a domain-scoped tenant and you operate it as part of the gig.
MSP — built
You run Nmonic for your managed customers' meeting workflows. Your team gets free managed copilot, attributed to your domain, with usage rolled up per customer org.
ii. What partners get
i.
Free managed Nmonic, gated by domain
Anyone with a verified partner-domain email gets the managed copilot — we provide Deepgram and Anthropic, you bring nothing. Real economics: per-token monthly caps, rate limits, a cheap-model allowlist, and a kill switch. Free for partners is not an open bill.
Security posture is here.
ii.
Per-org usage rollup
Partner ops gets a live read on adoption. Hit GET /v1/admin/partners/:id/usage for active users, hours transcribed, copilot calls, and cost — your team, your customers, your sub-orgs. It is what your board wants to see.
iii.
Domain-attributed tokens
Every token the relay mints is tagged to the partner that drove the activation. Every transcript, every copilot call, every billable minute rolls up to a partner org. No spreadsheet reconciliation later.
iv.
Same security posture as the consumer product
Local-first audio, memory-only relay, tokens in the Keychain, an internal adversarial audit completed 2026-06-15. Nothing softer for partners; nothing harder either. Read
/trust and the audit doc for the long version.
iii. How activation works
Three steps. Manual today, by design — we want to talk to every partner before we mint a token.
01
Request domain verification
Email us from an address on the domain you want activated. We confirm the domain belongs to you.
02
We mint a partner-admin token
Domain added to the partner allowlist. Mick sends you a nmonic://redeem?token=… link your team can share internally.
03
One-click into the app
Any employee on the verified domain clicks the link, lands in the macOS app via
/signin, and is live. Their usage rolls up under your partner org.
No self-serve onboarding form yet. The activation is a real conversation. That is on purpose for now — the partner program scales when the conversations stop being the bottleneck, not before.
iv. Partners we're already working with
One live partner today. More on the way.
v. Talk to us
If any of the four shapes sounds like you, write us a sentence about what you'd do with the copilot and the domain you want activated. We'll write back the same day.