This document discusses different developer support models for public safety technology platforms. It presents a cost vs commitment matrix that outlines the types of support and enablement provided at each level from self-service to premium support. The matrix shows that higher touch premium support costs more but provides more resources like direct access to engineers. The document also notes how the chosen support model can impact a program's strategy by exploring tradeoffs between broad ecosystem support vs more limited sophisticated partnerships. It provides best practices examples from IBM and Cisco developer programs.