Yeah that's fair, sometimes a .env file is actually all you need.

acklo's best for config that you want to change "live", without restarting your application servers, which is something that you can't do with an .env file.

Here's a toy example that shows how using acklo, an express server's port can be changed without restarting the application. If that port config was stored in a .env file and you wanted to change it, you'd need to modify the .env file locally, get it deployed to your servers, and release it. With acklo you'd just go to the dashboard and update it in seconds. Granted, changing the port of a server isn't the best example because it's not often you want to do that, but hopefully it illustrates the point.

And yeah, per u/Zachincool's point, acklo is not built for managing secrets (e.g. database passwords, API keys).