Two ways to run the service
You can operate Staying Alive from our console, or trigger it from your own dispatch software without your operator changing screen. Most services start with the first and move to the second.
Standalone
Your operators use our console. Nothing to connect, nothing to develop on your side. Live in a matter of weeks.
Integrated
The alert is created by your dispatch software through our APIs. Your operator never leaves their usual interface. Timeline depends on your software and its APIs.
Standards we speak
Interoperability has been a design constraint since launch, not an afterthought.
- EDXL, the Emergency Data Exchange Language.
- EMSI, the emergency message structure used by European civil protection systems.
- JSON over HTTPS for everything else.
- Proprietary endpoints where a client system needs something the standards do not cover.
If your national crisis management system already exchanges EDXL or EMSI messages, we plug into it rather than asking you to build an exception for us.
The alert API
The defibrillator API
Beyond the API, the database can be delivered as a customised RSS or JSON feed, or as an embedded map inside your own web pages and GIS. A live map can be displayed in the dispatch room to monitor defibrillator status.
Security
Staying Alive was designed with the cybersecurity constraints of the emergency world built in from the start.
- Signed token authentication on every API call, with no server-side session storage.
- Encrypted connections, with IP address restriction available per client.
- Database encryption at rest.
- Automatic daily backups.
- Two-factor authentication available for back office accounts.
- Redundant servers behind a load balancer, with automatic scaling.
What we deliberately do not publish
Runtime versions, component inventories and infrastructure topology are shared under a non-disclosure agreement during procurement, not on a public page. Ask and we will send the full technical dossier to your security team.
Hosting and availability
Your data stays yours
Everything the system records can be exported and shared.
- Nationally, to assess programme efficiency and to decide where AEDs and training should go.
- Internationally, to feed European Resuscitation Council studies and to comply with the 2025 guidelines, and to contribute to AHA and ILCOR work.
- To your own analytics, to feed models that improve out-of-hospital cardiac arrest management at country level.
How a deployment runs
- Standalone: a few weeks from decision to live service. The work is configuration, responder recruitment and training your operators.
- Integrated: the timeline depends on your dispatch software and the APIs it exposes. We scope it with your software vendor before committing to a date.
Licence model. An initial fee covers configuration, customisation and training. The annual licence is then based on the population covered.
Indicative order of magnitude
The annual licence typically depends on scope, integration and the services included. We give a firm figure once we know your coverage area and your dispatch system.
Send us your coverage area, your dispatch software and whether you want standalone or integrated. We will come back with a scoped proposal.