There can be 100% user-facing feature parity with differences on: + SLA and support models (including updates, delivery, integration, etc) + Hosted vs. self-h

There can be 100% user-facing feature parity with differences on: + SLA and support models (including updates, delivery, integration, etc) + Hosted vs. self-hosted + Procurement models + Compliance models + Legal, licensing, IP models The last 3 may be most applicable in the enterprise part of the market, but can be critical there. Enterprise also often has 'features' which are driven by admin, ops, security, procurement and compliance teams. These 'features' may make sense to limit to the SaaS, partially to keep the FOSS clean, and don't conflict with a mission of user-facing feature equivalence between FOSS and SaaS.