Grapity vs Zally

Grapity is an open-source API governance platform for teams coordinating API contracts and their consumers. Its Registry compares each pushed specification with the previous version and blocks breaking changes with an explanation. It enforces semantic version increments and tracks deprecation lifecycles, including consumers and sunset dates. The Hub offers a searchable API list, endpoint exploration, side-by-side version comparisons, and a version timeline. Grapity governs OpenAPI and AsyncAPI formats, with CI/CD integration and role-based access control. For Kong, Grapity Gateway generates configuration from registered specifications, and the CLI provisions it through decK; Kong can also send access logs to the Registry using its http-log plugin for queries and traffic statistics. The project says it is licensed under Apache 2.0 and has no features locked behind paywalls. Self-hosted use costs nothing, billed forever, with unlimited APIs and team members. Cloud costs $29.95 a month and includes five APIs and five users.

Zally is an API linter and quality assurance tool for OpenAPI specifications. It supports OpenAPI 3 and Swagger OpenAPI 2, with a RESTful API, command-line interface, and web interface. Its standard configuration checks APIs against Zalando’s RESTful Guidelines, and the project says it can also be used out of the box by others. Teams can enable or disable server-side rules, configure some existing rules, or implement their own in Kotlin. An API definition can use the x-zally-ignore extension to disable rules for that API. The web interface lists implemented rules and can lint external files and API definitions in its online editor. The project describes starting the web UI, server, and database together using Docker Compose. It also lists an unofficial Zally Maven Plugin integration. Maintained by Zalando, Zally is offered under an MIT license with an exception. Its Open source plan costs nothing.