How Milestone Technology Partners Get Certified and Published on the XProtect Marketplace

What a Milestone Technology Partner is

Milestone Systems doesn't build every capability a video management deployment needs. Analytics, access control, LPR/ANPR, alarm handling, PSIM, and industry-specific workflows are largely built by third parties who extend the core XProtect platform. Milestone formalises that relationship through its Technology Partner Program — an open program, free to join, for vendors whose applications, hardware or services complement and extend XProtect. Partners get access to the MIP SDK, developer documentation, and — once at least one integration is verified — joint marketing activities and a listing that puts their solution in front of Milestone's installer and integrator network.

Becoming a Technology Partner is a business relationship on top of a technical one. The company accepts Milestone's Technology Partner Program Terms and Conditions at enrollment, and the actual admission into the program is gated on passing certification for at least one integration — not just signing up.

How partners connect to the XProtect ecosystem: the MIP SDK

The technical bridge between a partner's solution and XProtect is the Milestone Integration Platform Software Development Kit (MIP SDK). It exposes three distinct ways to integrate, and the right one depends on how deeply the solution needs to sit inside XProtect:

• Protocol integration — the most basic method, communicating with XProtect over its APIs without a compiled dependency on the SDK. Well suited to non-Windows environments and loosely coupled integrations.
• Component integration — the partner's Windows application references MIP SDK's .NET libraries directly, pulling XProtect functionality (configuration, events, video) into their own application shell.
• Plug-in integration — the deepest integration mode: the partner's plugin is embedded directly inside XProtect Smart Client, Management Client, or Event Server and runs as part of the Milestone application itself, rather than as a separate program talking to it.

Most of the plugin work we do at Xplug.in — Smart Client view items and side panels, Event Server sources, Recording Server device drivers — falls into plug-in integration, because that's the mode that gives operators a native, in-product experience instead of a bolt-on application. We've written separate technical walkthroughs on building a Smart Client plugin and building an Event Server plugin with the MIP SDK if you want the code-level detail.

What kinds of solutions Technology Partners actually build

The Technology Partner ecosystem spans a wide range of categories, all of which extend what an XProtect deployment can do out of the box:

• Video analytics and AI — object detection, people counting, intrusion detection, and other analytics engines that feed metadata and alarms back into XProtect.
• Access control and LPR/ANPR — integrations that tie door controllers, card readers, or license-plate recognition systems into the same operator interface as video.
• Alarm and notification routing — solutions that take XProtect events and push them into external alerting, PSIM, or communication channels.
• Storage, cybersecurity, and infrastructure — hardware and software that XProtect depends on operationally, certified separately as IT infrastructure components.
• Vertical and industry-specific workflows — retail, transportation, critical infrastructure and similar sector-specific extensions built on top of the core platform.

What unites them is the same requirement: before Milestone will call any of it a "Milestone Certified Solution," it has to go through the certification process below.

How Milestone certifies a solution

Milestone's Solution Certification Program tests and evaluates a partner's integration against four areas: functionality (does it do what it claims to do against XProtect), usability, performance, and a broader partner assessment. Certification isn't a paperwork exercise — Milestone actually runs the integration against a real XProtect environment.

There are three ways a certification project can run, each with a different split of responsibility between the partner and Milestone's engineers:

• In-House — the partner ships their solution to a Milestone test facility, along with the information Milestone's engineers need to work with the product directly.
• Remote — testing happens without shipping hardware, coordinated remotely between the partner and Milestone.
• Self-Test — the partner runs a defined test suite themselves and submits the results for Milestone's review.

Once a certification project starts, Milestone targets roughly 60 calendar days to a completion decision. Passing certification is also the gate for program admission: at least one integration has to be successfully verified before a vendor is formally welcomed into the Technology Partner Program, at which point they receive the Milestone Partner Badge and are recognised as an official Milestone Technology Partner. A certified solution's profile in Milestone's Solution Finder is marked with "Milestone Certified Solution" status, and the partner is authorized to use the "Certified Solution for Milestone" logo in their own marketing.

From certified to published: Milestone Marketplace and Solution Finder

Certification and Marketplace publication are related but not identical steps. Every application, piece of hardware, or service listed on Milestone Marketplace first goes through a Milestone verification review. Milestone's own definition is precise about what that verification actually promises: it means Milestone reviewed the partner's verification documentation and, as of that review, the solution was compatible with the specific XProtect version used in the test environment — it does not guarantee the product's functionality, and it does not certify compatibility for installations that don't match that tested environment. That distinction matters for anyone specifying a solution: "listed on Marketplace" is a starting point for due diligence, not a substitute for it.

Separately, being discoverable in Milestone's Solution Finder — the searchable directory integrators use to find partner solutions — requires the partner to hold a MyMilestone login, submit a completed Solution Finder entry, and have a finalized solution with at least one proven installation behind it. In practice, a Technology Partner's path runs: build on the MIP SDK → pass Milestone's solution certification → get admitted to the Technology Partner Program and receive the certified-solution badge → complete Marketplace verification and a Solution Finder listing so integrators can actually find and specify the solution.

Where this fits for plugin engineering teams

None of the certification process replaces good engineering — it audits it. A plugin that's architected cleanly against the MIP SDK, handles XProtect version upgrades gracefully, and is documented properly moves through Milestone's functionality, usability and performance review far faster than one bolted together to pass a demo. That's the same bar we hold our own Milestone XProtect plugin work to at Xplug.in, whether we're building the integration from scratch or hardening an existing one ahead of a partner's certification submission.