Pacto Operator

Kubernetes operator that deploys and manages the Pacto service, which records each service's ownership, dependencies, and API details as a single YAML…

  • Development
  • Infrastructure
  • Tools & Utilities
Kubernetes operator that deploys and manages the Pacto service, which records each service's ownership, dependencies, and API details as a single YAML operational contract validated and published to your container registry. It gives platform teams one verifiable source of truth for service facts that are usually scattered across wikis, Helm values, and tribal knowledge.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 14 days ago
Popular
3238 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
38
Open issues
20
Last commit
2026-11-07
Latest release
v4.4.2
License
MIT
Activity
steady

Checked 14 days ago - source: GitHub (TrianaLab/pacto)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Installation Deploy the pacto-operator Helm chart from Artifact Hub (linked) to your Kubernetes cluster, then follow the Quickstart in the Pacto documentation at pacto.run to publish your first service contract. source

Fetched 33 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Will the Pacto operator accept two entries with the same name in its configuration?

No. The operator rejects two entries claiming the same name when it reads its configuration.

Which dashboard data sources are listed as possible Pacto entry-name collisions?

The docs name the live cluster, OCI, and the disk cache as dashboard data sources that can collide with a Pacto entry name.

When does the Pacto dashboard refuse a colliding name?

A colliding name is refused by the dashboard before a snapshot is built, rather than published as one name.

Is the Pacto contract standard distributed through OCI?

Yes. The troubleshooting docs describe Pacto's contract standard as open and OCI-distributed.

Answers sourced from pacto.run, pacto.run

Community

Collected 48 days ago - public community threads