Three ways to experience the platform, with no calendar bottleneck unless you want one. Run a real sandbox tenant against a vulnerable demo repo, watch a 9-minute end-to-end walk-through, or book a 30-minute call with a solutions engineer. Same product on each path.
Self-serve, video, or live. None of the three is a marketing-gated PDF — every path lands on the actual product.
7-day expiry · no card
A real tenant pre-loaded with a deliberately vulnerable demo monorepo and the full Safeguard stack pointed at it. Lino runs in your local CLI and VS Code, Eagle sweeps the repo on the cloud side, and the full Griffin lineage reasons over every finding. Same engine as production, scoped to a sandbox-only audit log.
9 minutes · no signup
A 9-minute end-to-end walk-through of a representative customer workflow. A real PR enters the pipeline, Lino fires inline, Eagle ranks the candidates, Griffin reasons and proposes a fix, the auto-fix campaign opens, and the regulator export drops at the end. Watch it on a coffee break.
30 minutes · 1:1
A 30-minute live session with a solutions engineer. Bring your own repo and we will point a temporary scan tenant at it; otherwise we will walk a demo flow on Safeguard's own infrastructure. Either way, you get to ask the questions a video can't answer.
The walk-through covers four representative moments along a single commit. Every path lands on the same audit log.
The 1B Lino head runs on your laptop and surfaces a verdict inline as you type the patch — sink, sanitiser, CWE class, and a one-line rationale. p95 inline latency is under 100 ms; the developer never leaves the editor.
A CI gate evaluates the policy DSL, fails the build with a reasoning-trace link, and posts a Griffin-authored auto-fix PR against your branch. The bot opens its own PR; the human reviews the trace and approves or rejects.
The web console reads from the same audit log every other surface writes to. Trend lines for finding burndown, policy adoption by team, time-to-fix SLA, regulator-export readiness — one tab, not five.
When Griffin Zero turns up a credible upstream vulnerability, the disclosure workflow drafts the maintainer email, an embargo timer, and the CVE reservation. The draft is in front of you; the send is in front of you.
Honest about scope. The sandbox is for evaluation; production-shape requirements are scoped on a call.
Zero. No credit card, no trial-to-paid auto-conversion. The tenant expires after 7 days unless you convert it to a paid plan or extend it during a live demo session.
Operational telemetry on the platform itself — latency, error rates, which surface produced a finding. The vulnerable demo repo is open-source and seeded by us; we do not ingest any code you push into the sandbox tenant. If you upload your own code into a sandbox project, that data stays inside your tenant.
Active for 7 days from signup. After expiry, the tenant is decommissioned and the audit log, SBOMs, and findings are purged within 30 days unless you convert to a paid plan, in which case it migrates intact.
Yes — at any point in the 7-day window. Conversion preserves the audit log, the policy you authored, the SBOM history, and any auto-fix PRs the bot opened. The sandbox-only flag is removed and standard tier limits apply.
Async support in the in-product chat (median first response under two business hours). Live demos and structured onboarding are gated to scheduled sessions; the sandbox is genuinely self-serve, but a solutions engineer is one click away.
A real tenant against a vulnerable repo is the fastest path to a real opinion. Seven days, no card, no email gauntlet.