Accounts, not shared logins
Create individual accounts. Teams, invitations, and fixed project roles are included in self-hosted Free. Use the access each person needs.
Read the details
Your applications deserve a clear operating model.
Understand what is
protected, who has access, and what remains yours to manage.
Security is a set of concrete decisions. Hakopod brings account access, service connections, secrets, and recovery into view so those decisions can be made deliberately.
Create individual accounts. Teams, invitations, and fixed project roles are included in self-hosted Free. Use the access each person needs.
Read the detailsUse scoped API credentials for automation. Human sessions and CI credentials have different permissions; container terminals require an authorized human session.
Read the detailsBind named secrets to the services that need them. Secret values are write-only and are excluded from TOML, secret-list responses, and revision history.
Read the detailsKeep service ports private by default and make public exposure deliberate. Named networks and explicit peer grants define allowed connections.
Read the detailsSupported database backups are encrypted before upload to object storage. Keep the recovery key outside the installation and test a restore.
Read the detailsReview application configuration and deployment history. Paid actor audit history adds oversight; custom roles and organization MFA enforcement remain planned.
Read the detailsSelf-hosted operators own the cluster, host updates, storage, ingress, and recovery. Network policies are not encrypted tunnels or a hostile-tenant isolation guarantee.
DNS, certificate readiness, and public reachability need separate checks on your infrastructure. Hakopod is a development release; local tests do not establish production acceptance for your installation.
Review the operating requirements