Ryan Zahrai
CEO & Co-Founder
Previously led incident response programs at logistics and fintech companies across APAC. Built Parachute because every team he worked with had the same bottleneck: the runbook was a document, not a system.
About Parachute
Built by security practitioners, for security practitioners
Parachute started in Sydney because we were tired of arriving late to incidents we could have contained.
Our story
Why we built this
Parachute started with a problem we lived for years before we had the tools to solve it.
Ryan Zahrai and the Parachute co-founders spent years running incident response for lean security teams at logistics and fintech companies across APAC. The tools existed. The runbooks existed. The processes were documented.
But when an alert fired at 3am, everything had to be done manually anyway. Log in, find the right runbook, gather context, isolate the host, pull the logs, draft the ticket. Twenty minutes later you had enough information to actually begin.
Parachute is the automated execution layer those teams were missing. The one that runs the runbook before your on-call finishes opening their laptop.
The people building it
The team
Sofia Chen
CTO & Co-Founder
Security engineer and systems architect. Spent six years building automation infrastructure for a cloud platform. Responsible for Parachute's execution engine and integration layer.
Marcus Webb
Head of Security Engineering
Red team practitioner and detection engineer. Helps customers encode their most complex playbooks and builds the runbook primitives that power Parachute's action library.
Principles
How we work
Speed is a security property
Every second of automation matters. When we ship a faster runbook action or a lower-latency intake path, that is a real security improvement for every customer who has a 3am incident.
Runbooks should be code
Versionable, testable, reviewable. A runbook that lives in a wiki is a document. A runbook that lives in Git, with CI tests, is a system. We build tools that make the second option as easy as the first.
Tools built for lean teams don't look like enterprise products
The team with two security engineers has different needs than the team with twenty. We build for the two-person team first. If the feature doesn't help you move faster during an incident, it doesn't ship.
Transparent about what we do and don't do
We list our compliance roadmap, not our certifications we haven't earned. We say what we do with your data. We publish our data handling practices in plain English. Security teams deserve honest vendors.
2024
Year founded, Sydney AU
3
Co-founders, all security practitioners
< 20s
Average alert-to-contained with Parachute
Want to see what we are building?
Try the product for free, or follow the thinking behind it on our blog.