Komodo, a self-hosted tool for building and deploying containers across multiple servers, similar to Portainer but with extra CI features and solid GitHub integration, recently released version 2.3.
The headline change is the introduction of pagination for the resource and container list APIs. Until now, installations managing many resources could generate large queries, likely affecting responsiveness and performance.
With the new release, Komodo retrieves resources in smaller batches instead of loading an entire collection at once. The default limit is 50 resources per page, though API users can disable pagination by passing limit: 0 in the request body.
The developers have also introduced improved term-based searching and server-side sorting, making container pages more responsive and enabling efficient searches regardless of the number of containers managed.
Monitoring has also received attention as Komodo 2.3 adds a new top-level Stats page with charts covering multiple connected servers. Memory reporting is now also more detailed, with Komodo separating actively used RAM from filesystem cache instead of showing memory consumption as a single figure.
Another major improvement is the ability to cancel operations while running. All Komodo builds can now be interrupted by terminating the active build command, which is useful when a build started with incorrect parameters or has become unnecessary.
Moreover, build webhooks have become smarter, as when multiple Git pushes arrive quickly, a newly triggered webhook can cancel the running build before starting another.
The same cancellation support extends to Actions and Procedures, although their behavior differs slightly. Actions stop immediately by terminating the Deno process executing the script. Procedures finish their current parallel stage before cancellation takes effect, preventing the workflow from continuing to its next stage.
Komodo 2.3 also improves the distribution of build workloads. Server-type builders can now connect to multiple servers, enabling simultaneous builds across available machines.
For deployments, the release adds support for configuring custom container and Docker Swarm service names. Regarding stack management, users can now view the services associated with a Stack, even when it is down. As a result, an individual service can be deployed without first bringing up the entire Compose Stack.
Several smaller interface improvements accompany these changes. Stack services can now be found through Komodo’s omni-search, and users have a new option to clear omni-search automatically when it is closed. The permissions table performance has also improved.
On the authentication side, Komodo 2.3 strengthens its Google sign-in integration through ID token validation. Additionally, the release introduces optional reporting of Komodo usage, disabled unless users explicitly enable it.
Finally, Komodo now produces a clearer log message when Git is missing from a system, rather than reporting an error that does not directly identify the absent executable. Responsive overflow affecting resource descriptions in the interface has been corrected as well.
For additional details, see the changelog.
