Self-host deployment

This guide targets organisations whose IT policy forbids installing extensions from Chrome Web Store or Firefox Add-ons.

Typical use cases

  • Air-gapped networks — IT teams without outbound Internet access to public stores.
  • Financial institutions under ACPR or a critical-infrastructure framework.
  • Public sector and critical infrastructure operators subject to NIS2.
  • Sovereignty policy excluding non-EU CDNs.

How it works

M-KIS provides signed artifacts (.crx for Chrome, .xpi for Firefox), an auto-update manifest, and a distribution endpoint dedicated to your organisation. Setup happens with our team: deployment-strategy audit (GPO, Intune, Workspace, MDM), out-of-band artifact delivery, cryptographic verification (SHA256), and pilot rollout support.

Start a self-host project

Self-host deployment is sized per use case: no public self-service in V1. Reach out with the number of target endpoints, the browser(s) to equip, your deployment platform (Intune, GPO, Workspace, MDM) and your network constraints (air-gap, proxy, etc.).

Start a self-host project

Back to documentation