For independent developers
Keep a dated record of the artifact your application depends on. Check whether it is reachable and whether its bytes still match the expected fingerprint before investigating a new deployment issue.
MODEL X / SOLUTIONS
Keep your model dependencies within reach.
Practical monitoring and preservation workflows for developers, teams, and model owners.
Create account Explore solutions ↓REAL WORKFLOWS
Keep the model behind your work in view.
For AI teams
Track models across supported hubs and direct URLs in one workspace. Review revision, configuration, license, and dependency notices when supported instead of treating every upstream change as equivalent.
For private model owners
Use supported encrypted source connections for restricted artifacts. Access still depends on valid credentials and provider permissions. Enrolling a private URL does not make its source public.
For preservation workflows
For models you are authorized to copy, use optional Pro recovery to keep a retained package and inspect recovery-drill evidence. A monitored URL alone is not a stored backup.
SECURITY IN YOUR WORKFLOW
Know what needs a closer look.
A dependency gains an advisory
A scheduled OSV check can surface a newly reported vulnerability in a collected, exactly pinned Python package. Review the advisory and affected dependency in Security Gate.
A file contains risky code
Static code checks and supported artifact-content scans flag potentially dangerous operations or serialized references. JSON configurations that request custom code or contain suspicious file references also receive review findings. Use the affected file, rule and available source location to investigate.
An inspection loses coverage
An unavailable scanner, oversized artifact or unsupported format is shown as incomplete. Reduced coverage is highlighted so disappearing findings are not mistaken for a fix.
A risk remains or clears
Compare dated inspections. Existing REVIEW and BLOCK results remain visible; new findings receive change alerts. When configured checks return to PASS, history records that transition.
These are example review workflows. Security results and alerts arrive with daily inspections, not instant upstream event notifications. Your team makes the deployment decision.
Explore the Security Gate →WHEN SOMETHING CHANGES
Move from a notice to a decision.
EXAMPLE WORKFLOW
A model’s upstream revision changes.
Start with the repository notice. Compare the available before-and-after metadata, then inspect artifact verification results and the model’s dated history. Decide whether to keep your pinned version or evaluate the update.
Revision noticeEvidence reviewYour release decision
Illustrative workflow, not a report from a customer account.
CHOOSE YOUR STARTING POINT
Start with monitoring. Add recovery when you need it.
Security Gate inspections, dashboard alerts and dated findings are included across all plans. Free includes one monitored model and one snapshot page. Starter expands this to five. Pro supports 25 monitored models and 25 snapshot pages, plus optional recovery and audit evidence.
Paid checkout is not open yet. Starter and Pro allowances require an active subscription or trial. See the current plans for full limits and availability.
Compare the plans →YOUR NEXT STEP
Your models. Your workspace.
Start with one model on the Free plan.