Need help with leapp?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

330 Stars 23 Forks Mozilla Public License 2.0 431 Commits 28 Opened issues


Leapp is the tool to access your cloud; It securely stores your access information and generates temporary credential sets to access your cloud ecosystem from your local machine.

Services available


Need anything else?

Contributors list


Github All Releases Language grade: JavaScript - Website: - Roadmap: Roadmap - Wiki: Wiki - Chat with us: Slack


Leapp is a Cross-Platform Cloud access App, built on top of Electron.

The App is designed to manage and secure Cloud Access in multi-account environments.

Leapp App

Key features

We Strongly believe that access information to Cloud in

files are not safe, and we prefer to store that information in an encrypted file managed by the system. Credentials will be hourly rotated and accessible in those files only when they are needed, so only when Leapp is active.

All the covered access methods can be found here.

Leapp App animation


Get here the latest release.


Please read through our contributing guidelines and code of conduct. Included are directions for opening issues, coding standards, and notes on development.

Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at


Development on Leapp can be done on Mac, Windows, or Linux as long as you have NodeJS and Git. See the

file located in the project for the correct Node version.
Initial Dev Setup

This repository is structured as a monorepo and contains many Node.JS packages. Each package has its own set of commands, but the most common commands are available from the root package.json and can be accessed using the npm run ... command. Here are the only three commands you should need to start developing on the app.

# Install and Link Dependencies
npm install

# Start App without Live Reload
npm run electron-dev

If Electron is failing building the native Library Keytar just run before npm run electron-dev:

# Clear Electron and Keytar conflicts
npm run rebuild-keytar
Editor Requirements

You can use any editor you'd like, but make sure to have support/plugins for the following tools:

  • ESLint – For catching syntax problems and common errors


By default, Leapp writes logs to the following locations:

  • on Linux:
  • on macOS:
  • on Windows:
    Logs are structured in the following way:
    [YYYY-MM-DD HH:mm:ss.mmm] [LEVEL] [rendered/system] [COMPONENT] MESSAGE {Useful Object / Stacktrace Err Object}
    Note: please always add logs whenever possible to any issue you want to fill to enable the team identify the problem quickly


Here you can find our documentation.


We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.