Skip to main content
Version: 1.2.0

Introduction to SAFE

Security Audit For Erlang/Elixir​

SAFE is a vulnerability scanner for Erlang and Elixir applications to identify issues that would make the code susceptible to cyber attacks. If you have any queries, please contact safe@erlang-solutions.com

SAFE is brought to you by Erlang Solutions and ELTE Soft.

info

If you have an open-source repository, we can provide you a free license, please send us an email at safe@erlang-solutions.com specifying the open-source repository where you'd like to use SAFE (e.g., include the GitHub link). This will help us ensure the right license is sent for that specific repository and provide any necessary support. You do not need to continue with the installation and setup.

Installation Guide

Step-by-step guides to setting up your system and installing SAFE.

Open Source

SAFE is free for open source projects, click here to request a license. Make sure to include the URL of the project in the email.

Erlang Ecosystem Foundation

Recommendations and vulnerabilities defined by the Erlang Echosystem Foundation security WG.

Click here for more information

Erlang Solutions

We’re the world-leading experts at building massively scalable distributed systems

More details

Pricing​

Enter your Effective Lines of Code (ELOC) to calculate pricing:

Pricing Calculator

Monthly Price£84.00
Yearly Price£924.00
tip

You can use cloc or scc as an estimate for the effective Elixir and Erlang lines of code for your project.

Who is it for?

All users of Erlang and Elixir, but especially those businesses that require high availability and resilience of their mission-critical applications for many different reasons:

  • Business continuity—where there is an impact to the operation of the business if an Erlang/ Elixir node, system or application goes down.

  • Legislation—industries where system availability is mandatory and failure to meet requirements would lead to non-compliance and significant financial consequences.

  • Customer experience—guaranteeing systems are available for customers to carry out their daily lives.

  • Corporate reputation—where system downtime or any form of security breach negatively impacts the reputation of the business, affecting its trading performance and potentially its responsibility to shareholders.

  • Businesses that have already been impacted by a security vulnerability within their Erlang or Elixir code base and want to investigate what other parts of their system may be vulnerable.

  • Anyone launching new Erlang or Elixir code, that would benefit from the reassurance that an audit can provide before going live.

  • Anyone concerned about the impact of a cyber-attack.

Contents