TrianaLab

TrianaLab / pacto

Public

Pacto (/ˈpak.to/ — from Spanish: pact, agreement) is an open, OCI-distributed contract standard for cloud-native services.

trianalab.github.iopacto contract development oci pacto platform-engineering
10
3
100% credibility
Found Mar 12, 2026 at 10 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Go
AI Summary

Pacto lets people create simple descriptions of their cloud services, check them for issues, and share them easily for teams to use.

How It Works

1
🔍 Discover Pacto

You hear about Pacto, a friendly way to clearly describe what your cloud service needs and does.

2
📥 Pick up the tool

Grab the Pacto helper app quickly and easily to start working.

3
✨ Make your first service description

Create a simple file that outlines your service's basics like name and setup with just a few details.

4
📝 Add your service details

Fill in what ports it uses, what it connects to, and how it behaves – like telling a story about your service.

5
✅ Double-check everything

Run a safety scan to ensure your description is spot-on and ready to go.

6
📤 Share it widely

Put your description in a shared online spot so your team can grab and use it anytime.

🎉 Team in sync!

Now everyone understands your service perfectly – no more confusion on how to run or connect it.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 10 to 10 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is pacto?

Pacto, Spanish for "pact" or agreement like a pacto de silencio, is a Go-based YAML standard for defining cloud-native service contracts—covering interfaces, runtime behavior, dependencies, config schemas, and scaling intent. It acts as OpenAPI for service operations: write a single pacto.yaml file, validate it through structural, cross-field, and semantic checks, then push as OCI artifacts to registries like GHCR or ECR. Platforms pull these oci-distributed pacts to auto-generate manifests, resolve dep graphs, or catch breaks—no agents or sidecars needed.

Why is it gaining traction?

Unlike Helm charts or OpenAPI specs that guess runtime needs, Pacto declares everything in one machine-readable file: stateful vs. stateless, health checks, typed deps with semver ranges, even scaling min/max. CLI commands like `pacto diff` classify changes as breaking/non-breaking across versions and transitive deps, while `pacto graph` visualizes trees—perfect for CI gates. OCI distribution means it slots into existing pipelines without new infra, echoing standards like pactos for services.

Who should use this?

Platform engineers building internal developer platforms who reverse-engineer services from READMEs or Slack. App devs shipping microservices wanting to catch misconfigs pre-CI and document ops intent once. DevOps teams enforcing policies across OCI registries, especially in Kubernetes-heavy setups tired of hardcoded manifests.

Verdict

Try Pacto if you're standardizing cloud-native contracts—solid docs, full test coverage, and MCP for AI tools make it production-ready despite 10 stars and 1.0% credibility score. Still early; watch for adoption before betting the farm.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.