diff --git a/docs/05-comparatives/vs-milestone.md b/docs/05-comparatives/vs-milestone.md
new file mode 100644
index 0000000..1377b50
--- /dev/null
+++ b/docs/05-comparatives/vs-milestone.md
@@ -0,0 +1,56 @@
+# vs Milestone XProtect
+
+## Snapshot
+
+| Dimension | Milestone XProtect | Blocao |
+|---|---|---|
+| Origin | Danish, ~25 years old, enterprise VMS | New, edge-AI-native, open-source-stack |
+| Platform | Windows Server | Linux (OpenWrt + Balena) |
+| AI | Plugin-based ("MIP plugins") + partner ecosystem | Built-in Frigate + custom enrichers |
+| Architecture | Centralized recorder server + workstation client | Distributed: router + Cell + optional hub |
+| Pricing | License per camera + maintenance + plugins | Hardware + optional support |
+| Customer profile | Mid-large enterprise, system integrators | SMB to mid, sovereignty-conscious |
+| Deployment | Software install on existing servers | Appliance (router + Cell) |
+| Multi-site | Possible with Federated Architecture | Native via hub |
+
+## Where Milestone wins
+
+- **Maturity**. 25 years of refinement. Edge cases handled.
+- **Integrator network**. Worldwide, deeply trained.
+- **Enterprise features**. PSIA / ONVIF Profile G/T compliance, RAID-aware recorder, redundant servers.
+- **Camera support**. Tested with thousands of camera models.
+- **Compliance certifications**. SOC 2, ISO, etc. for the corporate customer.
+- **Recognition**. CIO of a Fortune 500 will not get fired for choosing Milestone.
+
+## Where Blocao wins
+
+- **Modern stack**. Linux, MQTT, GitOps. Milestone is fundamentally Windows-centric, with all the Windows-server operational overhead that implies.
+- **AI as first-class citizen**. Frigate is built into Blocao. Milestone treats AI as a plugin layer, sold separately, often by third parties (BriefCam, IPConfigure, etc.). Plugin AI is not architecturally first-class.
+- **Cost**. Milestone Corporate license + maintenance + AI plugins for a 30-camera site easily reaches €15-25k upfront + €5-10k/year. Blocao is hardware + small support.
+- **GitOps**. Milestone configuration is in databases and registry. Blocao is in Git. Audit trail comparison is not close.
+- **Sovereignty**. Milestone Open Platform → cloud is now offered (Milestone XProtect on Microsoft Azure). Adopting it puts data on hyperscaler. Not the path for sovereignty-conscious buyers.
+- **Operational footprint**. Milestone needs Windows admins. Blocao needs Linux/network admins. The Linux talent pool is broader and more aligned with modern devops.
+
+## Where each is comparable
+
+- **Recording reliability**. Both handle 24/7 recording with proper hardware. Milestone has more enterprise-grade redundancy options out of the box; Blocao gets there with proper Cell + UPS + storage planning.
+- **Camera support**. Milestone's tested-list is wider; Blocao supports any ONVIF Profile S, which covers ~95% of cameras shipped this decade.
+
+## Sales conversation patterns
+
+When prospect mentions Milestone:
+
+1. **Ask: "Existing deployment or new?"** This is the key fork.
+2. **If existing**: don't try to displace. Position Blocao for the new sites or new use cases. Coexistence is fine.
+3. **If new and they're considering Milestone**: probe — is it because their integrator pushed it (most common), because they have Milestone elsewhere (lock-in), or because they evaluated and chose it?
+4. **If integrator-pushed**: counter with "modern stack, less ops overhead, comparable feature set, lower TCO". Get the prospect to evaluate Blocao directly.
+5. **If lock-in**: acknowledge the strength of the existing investment, propose pilot at a single new site.
+6. **If genuine evaluation**: emphasize sovereignty, GitOps audit, edge AI as first-class.
+
+## Honest assessment
+
+Milestone is a very capable product. For a customer with existing Milestone deployments and a strong relationship with a Milestone-trained integrator, switching is not a small ask.
+
+Blocao's wedge is **new deployments** and **sovereignty-conscious buyers**. We don't aim to replace Milestone in a Fortune 500 already running it. We aim to be the obvious choice for a new mid-sized deployment where Milestone would have been the default 5 years ago, and where modern stack + sovereignty + lower TCO actually matter.
+
+In LATAM specifically, Milestone has presence but the integrator network is thinner. There's a real opening.