Padloc

Storing shared credentials in a spreadsheet or a chat thread stops working the moment a team grows. Padloc handles password and data management for individuals and teams, with the whole stack published as source so an organization can run its own server rather than trusting someone else to hold the vault.

The repository is a monorepo split by target. A core package holds the logic, an app package holds the web UI components, and a server package is the backend. Separate packages wrap the same client as a progressive web app, an Electron desktop build, a Tauri native build, Cordova projects for iOS and Android, and a browser extension. A locale package carries translations, and a security whitepaper in the repository documents the design.

Running your own instance comes down to a handful of components.

• Server: the backend, listening on port 3000 by default and configurable through environment variables.
• Web client: a progressive web app on port 8080, the minimum pairing with the server.
• Desktop builds: Electron and Tauri packages producing cross-platform native applications.
• Mobile: a Cordova project used to build the iOS and Android apps.
• Browser extension: a separate package for working with credentials in the browser.

A local test instance takes a clone, an npm install, and npm start. Unit tests and Cypress end-to-end tests come with the repository, and every component is built and released through a single GitHub workflow driven by one project-wide version number.