tenantplaneBook a demo Artifact checks
A pinned source revision and file inventory, format-aware scans, license records, and documented exceptions for the model package and accompanying code.
Know what you’re deploying.
Get a traceable model release, documented security checks, and signed evidence your team can verify in your own registry.
Three outputs. One defined release.
Runtime vulnerability inventory
A software bill of materials and dated CVE report for the exact serving image and dependencies, with findings, exclusions, and responsible owners.
Signed release handover
Evidence bound to model and runtime digests, verification instructions, and an approved promotion path into your registry.
- PinSource, files & runtime
- ScanChecks & exceptions
- SignDigest-bound evidence
- VerifyIdentity & policy
- PromoteYour approved registry
Your registry. Your release decision.
You control the cloud account, registry, production approvals, and operator access. Tenantplane staging is optional and requires your approval; the deployment needs no Tenantplane control plane. Model use and redistribution remain governed by the original license, which does not transfer model intellectual property to you.
Implementation includes the agreed access, network, and request controls. This release-security add-on adds the checks and signed handover above; it is quoted per model and runtime, in addition to either implementation package. Optional rescans specify the covered inventory, cadence, notification and response responsibilities in a separate maintenance scope.
Technical scope & verification requirements
“Verified” means the identified release meets an agreed, versioned policy at the recorded time. Scans do not certify universal safety or the absence of backdoors. Model behavior and application leakage require separately scoped evaluations; host drivers and infrastructure require their own inventory.
Failed, unsupported, skipped, and incomplete checks cannot count as passed. Record tool versions, database timestamps, coverage, exceptions, approvers, and expiry. Review custom remote code, loading paths, egress, scanner telemetry, and third-party data handling before granting access.
Verification checks the exact artifact digest, trusted signer identity and issuer or key, signed attestation contents, policy version, evidence freshness, and withdrawal status. Copy the evidence with the artifacts and verify again at the destination before deployment. A signature alone does not authorize promotion; withdrawal must reach deployment policy and the named operator.
Rescan frequency is separate from human response and remediation time. Maintenance does not imply continuous monitoring or 24/7 incident response.
Download the release-policy template (JSON)
Technical references: Sigstore, CycloneDX, Hugging Face.