Side by side
These are typical focus areas. Individual products and deployments vary.
Scroll horizontally to see the full comparison.
| Capability | Artifact registry | Agent gateway | Skill scanner | ElixirHub |
|---|---|---|---|---|
| Version and access control | Artifact versions and access policies | Workspace access | Package review | Pinned releases and trust tiers |
| Security review | Package scanning depends on the registry | Runtime guardrails | Scan findings | Scan evidence linked to a release |
| Curated sources | Upstream mirrors and caching | Connector and tool registration | Review of supplied packages | Review upstream releases before adoption |
| Signing and provenance | Registry signatures and build metadata | Runtime identity and policy | Scanner reports | Publisher attestations and version evidence |
| Behavioral evaluation | External testing | Runtime observability | Security-oriented analysis | Functional, adversarial, and regression testing |
| Control over installation | Repository permissions | Agent and tool access | Review decisions | Workspace policy by trust tier |
| Decision traceability | Artifact metadata | Executed actions | Scan history | Skill version linked to ElixirData decision records |
When to choose what
Artifact storage and review
Use familiar registry and scanning tools when the main requirement is knowing which artifact was downloaded and how it was checked.
Governed agent releases
Choose a workflow with evaluation and traceability when auditors need evidence about what a skill did and which release shaped a decision.
Book an assessment