> ## Content Index
> Fetch the complete content index at: https://blog.esadax.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Passbolt
- URL: https://blog.esadax.com/en/passbolt-en-6/
- Published: 2026-11-15T04:53:59.000Z
- Updated: 2026-11-15T04:53:59.000Z
- Author: Esadax 
- Tags: #tr-apps-03-catalog-passbolt, #en, #mdx-imported, Apps

# What is Passbolt?

Passbolt is an open-source, self-hosted password and credential management platform designed for teams and organizations that need to securely store, manage, and share sensitive information.

It provides a centralized environment for managing passwords, API keys, database credentials, server access information, and other confidential data.

Unlike traditional password managers designed primarily for individual users, Passbolt focuses on secure collaboration. Users can organize credentials into folders, share them with individuals or groups, and control access through configurable permissions.

Passbolt uses OpenPGP encryption to protect sensitive information. Encryption and decryption of user secrets take place locally through the browser extension or compatible client applications, ensuring that the server stores encrypted credentials rather than readable passwords.

The platform provides browser extensions, mobile applications, command-line tools, and an API for integrating credential management into existing workflows.

Passbolt is particularly suitable for development teams, IT departments, system administrators, and organizations that need centralized and secure credential sharing.

## History of Passbolt

Passbolt was created to address the challenges of managing and sharing credentials within organizations.

The project was designed around open standards and cryptographic security, with an emphasis on collaboration and user-controlled encryption keys.

Its architecture uses OpenPGP for encryption, digital signatures, and authentication, allowing team members to share credentials without exposing their private keys to the server.

Passbolt has evolved into a password management platform with user and group administration, browser integrations, mobile applications, credential organization, and automation capabilities.

The Community Edition is distributed under the GNU Affero General Public License version 3 (AGPLv3), with additional commercial editions offering advanced organizational features and support.

## Key Features of Passbolt

Passbolt provides a comprehensive set of features for managing credentials and securely sharing them across teams.

- **Password Management:** Store and organize passwords in a centralized encrypted vault.
- **Secure Sharing:** Share credentials with individual users or entire groups.
- **OpenPGP Encryption:** Protect sensitive information using public-key cryptography.
- **End-to-End Encryption:** Encrypt and decrypt user secrets locally through compatible client applications.
- **Shared Folders:** Organize credentials into folders with configurable access permissions.
- **User Management:** Create, invite, suspend, and manage team members.
- **Group Management:** Organize users into groups for easier credential sharing.
- **Granular Permissions:** Assign owner, update, and read permissions to shared resources.
- **Password Generator:** Generate strong, random passwords using configurable options.
- **Secure Notes:** Store confidential notes alongside passwords.
- **TOTP Management:** Store and manage time-based one-time passwords.
- **Custom Fields:** Store additional confidential information associated with credentials.
- **API Keys:** Manage API credentials and other application secrets.
- **Browser Integration:** Automatically fill login forms and save credentials through browser extensions.
- **Mobile Applications:** Access credentials through supported Android and iOS applications.
- **Command-Line Interface:** Integrate password management into developer and administrative workflows.
- **Activity Tracking:** Review resource activity and sharing operations through supported functionality.
- **Authentication Security:** Use OpenPGP-based authentication and additional authentication factors.
- **REST API:** Integrate credential management with external applications and automation systems.
- **Self-Hosted Deployment:** Operate the password management infrastructure on your own servers.

## Use Cases

Passbolt is suitable for organizations and individuals who need secure credential management across multiple users and systems.

Common use cases include:

- **IT Infrastructure Management:** Store SSH credentials, server passwords, and infrastructure access information.
- **Development Teams:** Share database credentials, API keys, deployment secrets, and development environment configuration.
- **System Administration:** Manage credentials for Proxmox, storage systems, network devices, and monitoring platforms.
- **DevOps Workflows:** Organize CI/CD credentials, deployment tokens, and infrastructure secrets.
- **Business Operations:** Securely share access to business applications and administrative accounts.
- **Database Administration:** Store database connection credentials and access information.
- **Network Management:** Manage credentials for routers, switches, firewalls, and network services.
- **Team Collaboration:** Provide controlled access to shared credentials across departments.
- **Remote Teams:** Allow authorized employees to access shared credentials from different locations.
- **Application Integration:** Automate credential retrieval and management through APIs and CLI tools.

## Benefits of Passbolt

- Open-source password management with self-hosted deployment
- Designed specifically for team collaboration
- OpenPGP-based encryption and authentication
- Secure credential sharing between users and groups
- Granular permissions for shared resources
- Browser extensions and mobile applications
- Password generation and credential organization
- Support for secure notes, TOTP, and custom fields
- REST API and command-line integration
- User and group management
- Integration with existing infrastructure
- Greater control over credential storage and hosting
- Community Edition available without per-user licensing fees

## How to Install Passbolt

To install Passbolt through Esadax, follow these steps:

1. Purchase the application through Esadax.
2. After purchasing, you will be prompted to provide the required configuration parameters.
3. Configure the public application URL using your domain or subdomain.
4. Configure the MariaDB database connection and credentials.
5. Configure SMTP settings for invitations, notifications, and account recovery emails.
6. Ensure that HTTPS is enabled for the application.
7. Configure persistent storage for the database, application configuration, and GPG server keys.
8. Click **Deploy** to launch the application.
9. Access Passbolt through its assigned application URL.
10. Register the initial administrator account.
11. Install the Passbolt browser extension.
12. Complete the initial account setup and generate your personal OpenPGP key pair.
13. Download and securely store your account recovery kit.
14. Invite additional users and organize them into groups.
15. Start creating and sharing credentials.

Once configured, Passbolt provides a centralized environment for managing and sharing credentials securely.

## Password and Credential Management

Passbolt allows users to store different types of sensitive information within a centralized credential management interface.

Each resource can contain information such as:

- Credential name
- Username
- Password
- Website URL
- Description
- Additional custom fields
- TOTP authentication information
- Related metadata

Resources can be organized into folders and shared with authorized users.

The platform also supports standalone secure notes, TOTP entries, PIN codes, and other credential formats.

Users can search, filter, edit, copy, and organize their credentials through the browser extension or compatible applications.

This makes it easier to maintain a structured collection of access information without relying on shared spreadsheets, text files, or unsecured communication channels.

## Secure Credential Sharing

One of Passbolt's main advantages is its credential-sharing architecture.

Instead of sharing a common vault password between team members, Passbolt uses individual OpenPGP key pairs.

When a credential is shared:

1. The owner selects a user or group.
2. Passbolt retrieves the public keys of the intended recipients.
3. The credential is encrypted separately for each authorized recipient.
4. The encrypted copies are stored by the server.
5. Each recipient uses their own private key to decrypt the credential.

The server does not need access to users' private keys to distribute shared credentials.

This allows organizations to share sensitive information while maintaining individual cryptographic identities.

Credentials can be shared with individual users or groups, making it easier to manage access across departments and teams.

## Folders and Access Permissions

Passbolt provides folder-based organization for managing credentials.

Folders can represent departments, projects, infrastructure environments, or other organizational categories.

For example, an IT organization might create the following structure:

- Infrastructure
  - Proxmox
  - Networking
  - Storage
  - Backup Systems
- Development
  - Production APIs
  - Database Credentials
  - CI/CD Systems
- Security
  - Monitoring
  - Administrative Accounts
  - Security Tools
- Operations
  - Internal Applications
  - Cloud Services
  - Service Accounts

Passbolt supports three primary resource-level permission roles:

| Permission | Description                                                                    |
| ---------- | ------------------------------------------------------------------------------ |
| Owner      | Can view, edit, delete, and manage sharing permissions.                        |
| Update     | Can view, edit, and delete the resource but cannot manage sharing permissions. |
| Read       | Can view and use the resource without modifying it.                            |

These permissions help administrators enforce the principle of least privilege.

Users should receive access only to the credentials required for their responsibilities.

## User and Group Management

Passbolt provides user and group management functionality for organizing access across an organization.

Administrators can create users, send invitations, manage account status, and assign administrative roles.

Groups allow multiple users to receive access to the same credentials without individually configuring every permission.

Typical groups include:

- Infrastructure Administrators
- Developers
- Database Administrators
- DevOps Engineers
- Support Team
- Security Team
- Management

Each group can have one or more group managers responsible for maintaining its membership.

Group-based sharing makes it easier to manage permissions when employees change responsibilities or new team members join.

Users can be invited through email and complete their initial registration by configuring their personal OpenPGP keys.

## OpenPGP Encryption and Security Architecture

OpenPGP is the foundation of Passbolt's security model.

Each user has a public and private key pair.

The public key is shared with other users so they can encrypt credentials for that person. The private key remains under the user's control and is protected by a personal passphrase.

When credentials are shared, Passbolt encrypts them for each authorized recipient.

The main security components include:

- **Public Keys:** Used by other users to encrypt information for a recipient.
- **Private Keys:** Used by individual users to decrypt their credentials.
- **Digital Signatures:** Help verify the authenticity and integrity of shared information.
- **Personal Passphrases:** Protect access to private keys.
- **Server GPG Keys:** Support server authentication and other cryptographic operations.
- **Encrypted Storage:** Ensures that shared user secrets are stored as ciphertext.

Encryption and decryption of user secrets are handled locally through the browser extension or compatible clients.

The server stores encrypted credential data and does not receive users' private keys in cleartext.

Passbolt also supports encryption of resource metadata, such as names, URLs, and descriptions, when the corresponding organization setting is enabled.

The browser extension is an important part of the security architecture because it separates the cryptographic client from the web application served by the server.

## Password Generator

Passbolt includes a password generator for creating strong and random credentials.

Users can generate passwords according to their requirements rather than relying on predictable or reused passwords.

Available generation options include:

- Password length
- Uppercase letters
- Lowercase letters
- Numbers
- Special characters
- Custom character selection
- Password generation modes supported by the client

Generated passwords can be saved directly as new resources.

Using unique passwords for individual services reduces the impact of credential exposure and helps improve overall account security.

## Browser Extensions and Autofill

Passbolt provides browser extensions that integrate credential management into everyday browsing.

Supported browser extensions include:

- Google Chrome
- Mozilla Firefox
- Microsoft Edge

The extension provides access to the user's encrypted credentials and performs client-side cryptographic operations.

Browser integration includes:

- Searching stored credentials
- Autofilling login forms
- Saving new credentials
- Updating existing credentials
- Generating passwords
- Copying usernames and passwords
- Accessing shared resources
- Managing credentials through the browser interface

The extension also plays an important role in Passbolt's security architecture.

It is responsible for handling private keys and performing encryption and decryption operations locally.

Users must install the appropriate browser extension to complete their account setup and use the full browser-based experience.

## Mobile Applications

Passbolt provides mobile applications for accessing credentials from smartphones and tablets.

Mobile clients allow users to retrieve shared credentials while away from their desktops.

Depending on the mobile platform and application version, capabilities include:

- Accessing password resources
- Searching stored credentials
- Viewing shared folders
- Copying credentials
- Generating passwords
- Managing supported secure resource types
- Authenticating through the user's cryptographic identity

Mobile applications are useful for system administrators and employees who need access to credentials while working remotely or managing infrastructure on location.

## Multi-Factor Authentication and Account Security

Passbolt uses OpenPGP-based authentication as part of its security architecture.

Users authenticate by unlocking their private keys and completing the cryptographic authentication process.

The platform also supports additional authentication factors to strengthen account protection.

Depending on the configured edition and authentication settings, additional security options can include:

- Time-based one-time passwords
- Additional verification steps
- Security policies
- Authentication integrations
- Session management

Administrators can configure organization-wide authentication policies to improve credential security.

## API and Developer Integrations

Passbolt provides a REST API that allows external applications and automation systems to interact with the credential management platform.

API access is useful for integrating password management into existing development and infrastructure workflows.

Common integration scenarios include:

- Retrieving authorized credential metadata.
- Automating resource management.
- Managing users and groups.
- Integrating internal administration tools.
- Automating credential rotation workflows.
- Building custom management interfaces.
- Connecting infrastructure automation systems.
- Integrating external applications with credential management.

Passbolt also provides a command-line interface for interacting with the platform.

The CLI can be particularly useful for developers and system administrators who need to automate credential operations within scripts and infrastructure workflows.

API and CLI authentication should use dedicated credentials and appropriate permissions rather than unrestricted administrative access.

## Security / Administration / Configuration

Passbolt is designed specifically for managing sensitive information, so its deployment requires careful attention to security.

Important security practices include:

- Use HTTPS for all application access.
- Configure a strong, unique database password.
- Protect the server's OpenPGP private key.
- Keep application configuration and encryption keys backed up securely.
- Require strong user passphrases.
- Encourage users to download and protect their recovery kits.
- Use group-based sharing instead of individually granting unnecessary access.
- Follow the principle of least privilege.
- Restrict access to administrative functionality.
- Configure SMTP securely.
- Synchronize the server clock using NTP.
- Keep Passbolt and its dependencies updated.
- Restrict database access to trusted infrastructure.
- Review user access when employees leave the organization.
- Monitor credential-sharing activity and available audit information.

The browser extension and mobile applications perform encryption and decryption operations locally.

The server also maintains its own GPG key pair for authentication and server-side cryptographic operations. This key pair must be protected and included in backup procedures.

Losing the server's GPG private key or an individual user's private key can affect access to encrypted information.

## Best Practices for Passbolt

- Organize credentials into meaningful folders.
- Use groups to simplify permission management.
- Assign access according to team responsibilities.
- Use unique passwords for every service.
- Generate strong passwords using the built-in generator.
- Avoid sharing credentials through email or messaging applications.
- Protect personal OpenPGP private keys.
- Store recovery kits in secure locations.
- Configure an administrator-approved account recovery process where available.
- Enable additional authentication factors.
- Review shared credential permissions periodically.
- Remove access when users leave the organization.
- Configure secure SMTP delivery for invitations and notifications.
- Maintain accurate server time using NTP.
- Back up the database and GPG server keys.
- Test account and server recovery procedures regularly.
- Keep the application and client extensions updated.

## Configuration Parameters

After purchasing this application on **Esadax**, you will be prompted to provide the configuration parameters required by the deployment.

Esadax adds the supplied variables to the deployment so the application can be launched with the configuration it requires.

The official Passbolt Docker deployment supports the following environment variables:

### Application Configuration

| Parameter              | Description                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------- |
| APP\_FULL\_BASE\_URL   | Complete public URL of the Passbolt instance, including HTTPS and the domain name. |
| APP\_BASE              | Optional application base path when running Passbolt in a subdirectory.            |
| APP\_DEFAULT\_LOCALE   | Default interface language and locale.                                             |
| APP\_DEFAULT\_TIMEZONE | Default application timezone.                                                      |
| DEBUG                  | Enables debugging output. Should be false in production.                           |
| PASSBOLT\_SSL\_FORCE   | Forces HTTPS access. Should be enabled for production deployments.                 |

### Database Configuration

The default Docker deployment uses MariaDB.

| Parameter                      | Description                             |
| ------------------------------ | --------------------------------------- |
| DATASOURCES\_DEFAULT\_HOST     | MariaDB server hostname.                |
| DATASOURCES\_DEFAULT\_PORT     | Database server port. Defaults to 3306. |
| DATASOURCES\_DEFAULT\_DATABASE | Database used by Passbolt.              |
| DATASOURCES\_DEFAULT\_USERNAME | Database username.                      |
| DATASOURCES\_DEFAULT\_PASSWORD | Database password.                      |

The accompanying MariaDB container uses:

| Parameter             | Description                                |
| --------------------- | ------------------------------------------ |
| MYSQL\_DATABASE       | Database created for Passbolt.             |
| MYSQL\_USER           | Database account created for Passbolt.     |
| MYSQL\_PASSWORD       | Password assigned to the database account. |
| MYSQL\_ROOT\_PASSWORD | MariaDB root account password.             |

The database credentials configured in the Passbolt application must match the corresponding MariaDB credentials.

### Email Configuration

SMTP configuration is required for invitations, notifications, and account recovery messages.

| Parameter                           | Description                          |
| ----------------------------------- | ------------------------------------ |
| EMAIL\_DEFAULT\_FROM\_NAME          | Sender display name.                 |
| EMAIL\_DEFAULT\_FROM                | Sender email address.                |
| EMAIL\_TRANSPORT\_DEFAULT\_HOST     | SMTP server hostname.                |
| EMAIL\_TRANSPORT\_DEFAULT\_PORT     | SMTP server port.                    |
| EMAIL\_TRANSPORT\_DEFAULT\_USERNAME | SMTP authentication username.        |
| EMAIL\_TRANSPORT\_DEFAULT\_PASSWORD | SMTP authentication password.        |
| EMAIL\_TRANSPORT\_DEFAULT\_TLS      | Configures TLS for SMTP connections. |

### OpenPGP Configuration

Passbolt uses a server-side GPG key pair for authentication and other cryptographic operations.

| Parameter                               | Description                                                                                                        |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| PASSBOLT\_GPG\_SERVER\_KEY\_FINGERPRINT | Fingerprint of the server's GPG key. Automatically detected during standard Docker initialization when applicable. |
| PASSBOLT\_GPG\_SERVER\_KEY\_PUBLIC      | Path to the public server GPG key.                                                                                 |
| PASSBOLT\_GPG\_SERVER\_KEY\_PRIVATE     | Path to the private server GPG key.                                                                                |
| PASSBOLT\_KEY\_EMAIL                    | Email address associated with the generated server key.                                                            |
| PASSBOLT\_KEY\_NAME                     | Name associated with the generated server key.                                                                     |
| PASSBOLT\_KEY\_LENGTH                   | Key length used when generating the supported RSA key configuration.                                               |
| PASSBOLT\_KEY\_EXPIRATION               | Expiration period for the generated key.                                                                           |

The GPG server key fingerprint is normally detected automatically during a standard Docker initialization when no custom configuration file or fingerprint is supplied.

When mounting a custom `passbolt.php` configuration file, configure the fingerprint explicitly as required by the official documentation.

Protect the GPG key directory and preserve its contents across container replacements.

The exact configuration parameters depend on the Esadax deployment package. Use the values presented during the purchase and deployment process.

Once the required values are configured, click **Deploy** to launch Passbolt.

## Database and Storage

Passbolt uses a relational database to store application information, users, groups, encrypted resources, and configuration.

The default Docker deployment includes MariaDB, while PostgreSQL can also be configured through the documented alternative database setup.

Database information includes:

- User accounts
- Groups and memberships
- Encrypted passwords and resources
- Folder structures
- Resource permissions
- Application configuration
- Authentication-related information
- Sharing information

The application also requires persistent storage for configuration and cryptographic keys.

Important locations include:

| Path                       | Description                                       |
| -------------------------- | ------------------------------------------------- |
| /etc/passbolt/gpg          | Stores the server's public and private GPG keys.  |
| /etc/passbolt/passbolt.php | Custom application configuration file, when used. |
| MariaDB data directory     | Stores the persistent database contents.          |

For reliable operation:

- Configure persistent database storage.
- Preserve the GPG server keys.
- Back up the database regularly.
- Back up application configuration.
- Protect backups using encryption.
- Store backups outside the primary server.
- Test database and cryptographic key restoration procedures.

**Important:** A database backup alone is not sufficient for a complete Passbolt recovery. The server GPG keys and configuration files must also be preserved.

Individual users should separately protect their recovery kits and private keys.

## Docker Deployment

Passbolt provides official Docker images and Docker Compose configurations for Community and Pro editions.

The standard deployment consists of:

- **Passbolt Application:** Provides the web interface and API.
- **MariaDB:** Stores application data and encrypted credentials.
- **Persistent Volumes:** Preserve the database, GPG keys, and application configuration.
- **SMTP Server:** Delivers invitations, notifications, and recovery emails.
- **Reverse Proxy:** Provides HTTPS and external access when required.

The official Docker image is:

`passbolt/passbolt`

For production deployments, use a specific version tag rather than relying on the `latest` tag.

The official Docker deployment also recommends using a working NTP service because accurate system time is important for GPG authentication.

## Community and Commercial Editions

Passbolt offers different editions depending on organizational requirements.

**Community Edition (CE)**

The Community Edition is free and distributed under AGPLv3.

It includes core password management functionality such as:

- Password storage and sharing
- Private and shared folders
- User and group management
- OpenPGP-based authentication
- Additional authentication factors
- Browser extensions
- Command-line interface
- Open API
- Role-based access control
- Password expiration

**Pro Edition**

The Pro Edition includes Community Edition functionality alongside additional organizational capabilities, such as:

- LDAP user and group provisioning
- Single Sign-On integrations
- Account recovery with administrative approval
- Advanced audit and activity logs
- Additional enterprise administration features
- Commercial support

Feature availability depends on the selected subscription and current licensing terms.

## Conclusion

Passbolt is an open-source, self-hosted password management platform designed to simplify secure credential sharing across teams and organizations.

With OpenPGP-based encryption, shared folders, user and group management, granular permissions, browser extensions, mobile applications, and API integration, it provides a comprehensive environment for managing sensitive credentials.

Its client-side cryptographic architecture helps protect user secrets while allowing teams to collaborate without exchanging passwords through insecure channels.

Passbolt is a practical solution for development teams, IT departments, system administrators, and businesses that need centralized credential management while maintaining control over their infrastructure and security.