Both platforms can run CMDB-Kit's schema, but the experience is different.

JSM Assets starts from a blank canvas. You define every type, every attribute, every relationship from scratch. This is an advantage for product-delivery schemas because there are no built-in assumptions to work around. The downside is that you build everything yourself.

ServiceNow has a massive built-in CI class hierarchy. Infrastructure types (Server, Database, Network) map to existing tables. Product-delivery types (Product, Feature, Baseline) need custom CI classes because the built-in Application and Database classes require hosting relationships that do not fit the product-centric model.

If you are evaluating platforms for a product-delivery CMDB, what factors are driving your decision?