Contact
Talk to the people
who wrote the code.
Kirra Systems doesn't route you through a sales layer — inquiries go to the engineering that builds the governor. Pick the door that matches your question; each one tells you exactly what to expect.
Contact channels
Commercial & partnerships
Deploying Kirra in a vehicle program, robotics fleet, or industrial platform — or exploring a strategic partnership or platform integration. Tell us your machine class and what proposes commands to it; we'll tell you honestly whether the governor fits today or belongs on the roadmap.
justin.looney@kirrasystems.comTechnical evaluation & due diligence
Evaluating the platform seriously? Start where a diligence team should: the repository, the 27 blocking CI lanes, and the safety-case evidence bundle attached to every tagged release. Then bring us your hardest questions — we prefer evaluators who arrive skeptical.
Or touch it now — two live demos, no install: the Verdict Playground runs the real frozen checker in your browser; the operator console demo runs the full Next.js console on a simulated fleet.
Security disclosure
Found a vulnerability — or got an unsafe command past the checker? Coordinated disclosure with a documented 48-hour first response. If you can break the envelope, we want the writeup more than you do.
Read the disclosure policy ↗Open source & community
Bug reports, feature discussions, and contributions run through GitHub in the open — the same gates apply to everyone, including us. Long-form engineering notes ship on Field Notes.
What to expect
The same honesty you see on this site
If a capability is experimental, we'll say so before you commit anything to it — the repository labels its spikes and drafts, and so do we. Security reports get a first response within 48 hours; everything else gets a direct answer from the people building the system, not a qualification funnel.