Saykai

Deterministic safety gate for AMR and warehouse robot deployments.

On every pull request, Saykai audits your Nav2/ROS 2 configuration against your approved Safety Spec (saykai-policy.yml), runs behavioral safety scenarios, and scans for leaked secrets — then blocks changes that fall below your safety bar.

For teams deploying physical AI, AMR fleets, and warehouse robotics on ROS 2.

Example output: 3/3 audit rooms passed. Safety Pack sealed and signed. Blocks only when your Safety Spec is violated.
CI_PIPELINE // PR-829
Commit
PASSED
Deploy
Status: PASSED Time: 14s
BUILT FOR TEAMS USING:   ROS 2  •  Nav2  •  GitHub Actions  •  ROS 2 Humble/Jazzy

Safety Spec = versioned thresholds  •  Safety Pack = signed JSON evidence per run

Stop guessing if your latest PR will break physical hardware.

Saykai turns CI into the first safety line before anything reaches production, acting as a versioned, audit-ready evidence artifact for every gated release

How it fits into your pipeline.

Commit → Saykai Gate → Deploy
Runs as a required check on every pull request.

Drop Saykai into your existing CI as a required check.

  • Every PR runs Saykai's 3-room audit: secret scan, behavioral simulation, and Nav2 policy check
  • Results are checked against your approved Safety Spec (saykai-policy.yml)
  • A signed JSON Safety Pack acts as an immutable audit trail
  • The PR passes or blocks based on policy, not gut feel

Runs entirely inside your own CI. No data leaves your pipeline.

> Drop in Saykai once, then every change is screened against the same safety bar.

description saykai-policy.yml
hard_limits: max_speed: 0.45 min_bubble: 0.15 max_accel: 2.50
Saykai Gate
Required • Passed in 14s
3/3 audit rooms passed
No policy violations detected
Safety Pack sealed: sp-8a7b9c.json (signed)

Start with one CI integration.

Step 1

Configure your policy (saykai-policy.yml)

Set approved hard limits — max speed, acceleration, and safety buffer — for your robot class. Lives in version control next to your Nav2 config.

Step 2

Install the GitHub Action

Run Saykai as a required check on every pull request in one critical repo.

If you are not on GitHub Actions, we will help you wire it in during the pilot.

Step 3

Get a Safety Pack on every PR

Each run produces a signed JSON Safety Pack recording every finding and the exact Safety Spec version used — a clear pass or block decision you can hand to safety and risk.

Private beta. Accepting a small number of pilot teams deploying Nav2/ROS 2-based robots.

Pilot with Saykai

  • Define your Safety Spec (saykai-policy.yml): Work together to set approved safety thresholds for your robot class and write the first saykai-policy.yml.
  • Integrate the CI gate: Wire the gate into a single pipeline, starting with GitHub Actions.
  • See value fast: Start receiving Safety Packs on every PR within 2 weeks.
No lock-in. If it is not catching useful issues in the first month, you stop.
GUARANTEE.TXT

NO_LONG_TERM_CONTRACT

IF VALUE == FALSE:
  EXIT(0)

No lock-in, no long-term contract.

Gate your next deployment.

The first step is simple: add saykai.yml and the Saykai CI check to one critical pipeline. From there, every change to that system is screened through the same deterministic safety bar.

Request pilot access View GitHub reference examples
Security Policy