Technical Overview

The LiveSafe Platform rests entirely on Amazon Web Services and also utilizes other third-party services (Open Market, Pubnub, etc.). This makes the platform highly available and highly scalable (machines autoscale based on demand).

Architectural Redundancy

The LiveSafe Platform is housed in a virtual private cloud (VPC) within the AWS’s U.S. infrastructure. Web and database resources are replicated across multiple availability zones and multiple regions for redundancy.

High Capacity

The LiveSafe Platform is architected to handle massive volumes of incoming and outgoing events, chats, and broadcasts in the event of a large-scale incident.

Lightweight Install

The LiveSafe Mobile App and implementations of the LiveSafe Mobile SDK use less than 20MB of device memory. Access the cloud-based dashboard via an Internet browser with no hardware or software install required.

Real-Time Location Service

In standby mode, the LiveSafe Platform updates location at least every 50 meters based on speed and movement of the employee. In active mode, which is when an emergency option has been invoked or when the SafeWalk feature is in use, location is updated every 10-15 seconds. LiveSafe serves as a steward of employee privacy, and the employee’s location information is only passed through when the employee has initiated an emergency action, and even then the employee is alerted before location sharing begins.

Low Battery Consumption

The value that the LiveSafe Solution can deliver goes up enormously when accurate location is maintained. The ability for employees to get help when an emergency option is invoked; the ability for friends to virtually accompany one another safely to their destinations; the ability to benefit from Geofenced Broadcast Messages — all of these scenarios require maintaining accurate location, and this is tied to battery consumption.

LiveSafe innovates to attain the right balance between the need to preserve battery life with the need to maintain accurate location for users, while safeguarding their privacy. That balance is achieved via architectural approaches as well as the discipline to embrace best practices and drive new innovation. This two-pronged approach ensures that the LiveSafe Mobile App does everything possible to “sip” battery power, while also unlocking the true value of the platform for both companies and for their constituencies.

Internet Browsers

  • Google Chrome (latest version)
  • Mozilla Firefox (latest version)
  • Safari (latest version)
  • Microsoft’s Internet Explorer & Edge (latest versions)

Mobile OS

  • Apple phones and tablets: iOS 8 and up
  • Android phones and tablets: Android 4.1 and up

Enterprise Structures

Flexible platform configuration for large, complex organizations — to better align with existing internal processes and flows of communication. Departments, offices, and regions can have customized instances of the LiveSafe Platform, all feeding into the global Security Operations Center.

Multi-Tenant Architecture

Incident reporting, chat, and other data are logically separated and secured by limiting and auditing access to each organization.


All data is encrypted in transit using industry standard HTTPS/TLS. Core organization system data is encrypted at rest. To protect personal data, high-speed row level encryption of personal information — including first and last names, email addresses, and phone numbers — is employed. Data at rest is encrypted (AES-256) at the database level as well as at row level using a customer specific key that is managed by Amazon KMS.

Activity Audit

All dashboard actions are automatically logged and time stamped to the admin that performed the action. Audits are stored separately from regular data and are not directly accessible by clients.

Administrator Privileges

Command and Communications Dashboard users can be assigned or restricted access to specific administrator functions and hierarchical views.

SSO Login

A user will be linked to their organization’s login page to allow for Single Sign-On to verify their access to the organization through a third-party federated identity tool (SAML 2.0 assertions).

Verified Email Domain

The user must add a verified email from a specific organization owned domain (for example, if this option is selected.

Access PIN

A 4-digit numeric pin, determined by the organization, must be entered to gain access if this option is selected.

SCIM Integration & Automated User Management

Via SCIM integration and Automated User Management, share user data from internal systems to keep LiveSafe user data in sync.

CSV Uploader

Via CSV uploader to bulk add large groups of people.

LiveSafe Mobile SDK

Embed essential functions of the LiveSafe Platform into existing iOS or Android app, seamlessly connecting people to help without having to download multiple apps.


Have the LiveSafe Command and Communications Dashboard data feed into any platform of choice— seamlessly integrating into existing workflows and without requiring multiple app downloads.