This was my first thought as well. This isn't a replacement for portainer agents on mulitple docker hosts, hopefully that's something that is doable in the future.
I ditched portainer earlier this year to use the command line only, and don't miss it at all. If you're only using docker compose, I really don't see the point of it.
A lot of smaller things, at least for me. The biggest grievance I have with it is the garbage tier UX between hitting "Deploy" on a stack and getting ito to do so. Error messages in the notification bubble get cut off, are unhelpful amd/or disappear too fast. That and the L9g Voewer sucking ass are my main problems with it and why I'll definitely check this out.
UI, just too many annoyances. Fkr example the cut off unhelpfull error messages
compose files, like this project calls it are taken hostage by portainer
git, while you can use a repository there is no comfortable way to test out changes and commit them to git. Would portainer use a sinple file structure for compose files that would not be a problem
Ads, they try to promote there business version via the UI.