Self-hosted secrets manager

Dopbase runs as one self-hosted executable with SQLite storage and an embedded Admin UI.

dopbase server start

Fresh startup prints a protected web setup link. Complete setup once; later starts reuse the instance. On a headless host, use DOPBASE_ROOT_EMAIL=admin@example.com dopbase server start and save the generated password. Explicit CLI setup remains available. See server setup. Operators still need to configure networking, TLS, master-key storage, backups, monitoring, upgrades, and recovery.

What you operate

A self-hosted installation owns:

• The Dopbase process and its network exposure
• The SQLite database and filesystem permissions
• Master encryption key material
• TLS termination
• Backups and restore testing
• Updates, monitoring, and incident response

Dopbase Cloud is planned to handle these responsibilities for its managed endpoint. It will not manage independent self-hosted servers.

Start small

For local evaluation, bind the server to localhost and keep the database and master key in separate protected locations. Do not expose an evaluation instance to the public internet.

Before a production deployment, read:

• Storage and backups
• Encryption keys
• Operations
• Security model