I wasn’t aware of this rule. I’ve updated the post accordingly!

It’s a bit different for SQLite, though, because it is not a server-based database engine: it is ultimately just a file.

For databases, you only need to provide the URL, port, and credentials. Portabase then connects using the database’s standard protocol, making it hosting-agnostic (so you can backup databases hosted in self-managed Docker environments, Kubernetes clusters, or cloud platforms).

You can already enable encryption through the web UI. Differential backups are not available yet but they are on our backlog (we do not have an estimated release date for now).

Feel free to give it a try if you have time, and don’t hesitate to open GitHub issues if you run into any bugs.

There are a few other tools. Docker Desktop has some backup-related tooling, but not through a web UI. Portainer may cover part of it too, but I’m not 100% sure.

You can also use generic file-level backup tools, since Docker volumes are basically files at the end of the day.

Portabase is more focused on backup and restore workflows. The goal is to have the full ecosystem around that: storage providers, notifications, retention policies, RBAC, agents, homogenous migration, etc.

Thanks for the feedback! Feel free to open issues for these ideas. A PR for SECRET_FILE support would be very welcome.

Thanks for adding Portabase to OpenAltFinder! I missed your message earlier, but I appreciate it.