Gantry vs Harness Internal Developer Portal

Gantry is an open-source internal developer platform for teams that need a service catalog and self-service workflows without dedicated platform engineering staff. Its catalog brings together services, APIs, teams, infrastructure components, and environments, including ownership and dependency relationships. Teams can create executable runbooks and workflows with schema-driven forms for tasks such as deployments and environment provisioning. Catalog entities can be written in YAML and applied with `gantry apply`, supporting version control, review, diffs, and rollback. Search uses SQLite FTS5, so Elasticsearch is not required. Official integrations include Kubernetes, GitHub, and ArgoCD; PagerDuty, Datadog, Grafana, and Flux are planned. Gantry ships as a Go binary with embedded SQLite and no external runtime dependencies. It can be installed from a binary, run through Docker or Docker Compose, or built from source. The documentation describes JWT authentication and requires installers to set an admin password. Gantry is self-hosted, licensed under Apache 2.0, and free. Its documentation says it is in active development and that APIs and schemas may change before its first stable release.

Harness Internal Developer Portal has no write-up on Specifiction yet; its figures are above.