Watch incidents right as they unfold, with live video, audio and location
Route incidents to email, phone, alarm, paging, dispatch, CAD, PSIM systems, TVs, notaries, social media and more
Archive, query and analyze incident data, like video, audio, location and more
In 2015, Parachute forever transformed personal safety by being the first to bring livestreaming to emergencies. In 2016, we did the same with emergency management by introducing the first and only livestream-enabled emergency management platform and API
The Parachute app has been battle-tested all around the world, by those facing danger every day. The Parachute Platform has been deployed in Safety, Healthcare, Command & Control Centers, Non-Governmental Organizations, Human Rights, Public Safety Answering Points (PSAPs) and more
Share your hotline's link. Users add the hotline to their emergency contacts simply by opening the link on their phone (Demo Hotline Link)
When users activate Parachute, their incidents show up in the hotline's Live tab. The hotline's endpoints are alerted according to its routing rules. All evidence is archived
Apps programmatically activate the Parachute app on behalf of the user using the iOS and Android APIs
The Parachute app acts as a hub for Bluetooth and WiFi-based panic buttons and devices (Beta only)
The Parachute Platform routes your hotline's incidents to custom endpoints within your organization, using the Platform API & Webhooks for full customization
Request access to the Parachute Platform
The Parachute Platform is for any organization or team that would like to receive live Parachute incidents. Teams get access to tools that previously cost hundreds of thousands of dollars or just simply didn't exist before. The Parachute Platform is currently deployed in safety, healthcare, insurance, news, transportation, human rights, as well as in many small organizations who are adding this functionality to their organization for the first time.
No. You can only receive and access Parachute incidents that have been sent to your hotline. When users add your hotline to their emergency contacts, all their subsequent incidents are sent to your hotline automatically, until they remove your hotline from their emergency contacts. You only have access to incidents in your hotline.
Yes. If you receive a link to a Parachute incident through other means (e.g. when a user forwards their incident email to your team), you can manually import the incident to a hotline through the Incidents panel
By default, Parachute data is stored in a proprietary blend of storage locations, which may include the United States. The Parachute Platform lets you fully control and customize how your data is stored and archived. We offer storage options in several countries across the world and additional storage features. You may also manage storage and archiving entirely on your own, thus relying on Parachute only to route the incident from a user's phone to your servers.
Much like a traditional telephone hotline, a Parachute hotline lets you receive Parachute incidents from anyone who adds your hotline to their emergency contacts. Parachute hotlines bring the concept of traditional phone hotlines into the future, providing you with very powerful functionality. Parachute hotlines let you see live video, audio, location, and other data straight from the scene; they let you route incidents to endpoints such as email, phone, alarm, paging, dispatch, TVs, notaries, social media and more; they let you archive the incidents you receive so they are never lost and easily searched; and they provide powerful incident-level and macro-level analytics on your incidents.
No. Because not all organizations wish to make their hotlines available to the wider public, it is up to each organization to disseminate their Parachute hotline links as they see fit. Organizations can also restrict who can send incidents to their hotline.
A Parachute endpoint is anything that can receive an emergency. When your hotline receives an emergency, the Parachute Platform routes (forwards) this emergency to all the endpoints you have configured. The endpoints can then act on the emergency. For example, a phone endpoint will text and call a number. An email endpoint will send out an email. A paging endpoint interacts with your paging system to send out a page. The Parachute Platform has several ready-to-use endpoints that you can configure in seconds. You can set the routing rules for when emergencies are routed to a particular endpoint. For example, you can have emergencies from different geographic regions routed to different phone numbers, or have emergencies sent to different email addresses depending on the time they are received. You add a new endpoint via the Parachute Platform's New Endpoint page.
When you would like to further extend the Parachute Platform, you create a custom endpoint. Custom endpoints use a very straightforward API to receive emergencies, and are then free to act on an emergency in whatever way the wish. For example, an insurance company can create a custom endpoint to automatically create a new claim and add the Parachute incident as evidence to the claim, or a transportation company can automatically alert nearby drivers.
Composites let you combine multiple Parachute incidents into a single incident in a matter of minutes. For example, when you receive 10 different incidents from 6 different people depicting the same event (e.g. a protest), you can combine all 10 incidents into a single composite. This lets you reconstruct an event and review the incidents together, in perfect sync. Just like incidents, composites are shareable via a web link. Composites are a very powerful tool that replaces painstaking manual work that would previously take weeks.
We offer API to programmatically activate Parachute from your own app. At the end of the incident, the Parachute app yields control back to your own app. While we do not offer a drop-in Parachute library, the perception to the end user is almost identical, since your app yields control to Parachute only when the incident is in progress. Not offering a drop-in Parachute library allows us to very quickly manage and patch the application for OS changes and new functionality, without having to rely on third-party developers updating their libraries and releasing new versions. This is very important for an application like Parachute. You register your app via the Parachute Platform's Register App page.
Yes (Beta only). Parachute has baked-in support for a wide range of Bluetooth and WiFi based devices, including simple buttons. This allows users to activate Parachute without using their phone. Using Parachute as the backend for a panic button you are developing lets you focus on designing great hardware and not having to worry about providing an app and infrastructure to handle the rest. You register your device via the Parachute Platform's Register Device page.
Once you receive access, you can be up and running in minutes. This means you can create hotlines, attach custom endpoints, connect your apps and your devices, and start receiving incidents in a matter of minutes. Before the Parachute Platform, such tools would take months to set up and would offer very limited functionality.
Parachute has no affiliation with any political, economic or social cause. Our role is to provide a reliable platform for emergencies, that, much like Twitter, is open to anyone, regardless of background and beliefs. The Parachute team will never access data unless specifically asked to do so by the initiator of the incident. Should we find ourselves unable to provide a neutral service for all, we will cease to operate. Please review Privacy and email email@example.com for your privacy concerns.
Have more questions? Email us at firstname.lastname@example.org