Webapp Management for Internal Tools

Platform for securely developing and deploying web tools across a team. 
Application server for containerized webapps. Create and share webapps for CLI applications.



Gif with Clace intro commands


Comparison with other tools

Open source PaaS solutions are built on top of reverse proxies (Traefik/Nginx) and work on Linux only. They support prod deployment only, not use in dev. They aim to be a simplified Kubernetes, providing pre-packaged apps, including support for deploying stateful applications like databases.

Clace is simpler because it does not aim to be a PaaS solution. Compared to other AppServers, Clace supports all languages and does not require any code changes in the app. Running in containers gives better isolation across apps. Clace is a single binary and runs natively on all platforms.

Comparison with cloud services

Google Cloud Run/AWS AppRunner allow easy deployment of containerized web apps. They run outside your infrastructure, making it difficult to talk to your existing systems. When deploying multiple small apps, cost can become a factor, especially when larger instances are required.

Clace provides a similar easy to use interface, including scale down to zero, on your own hardware. Hundred of apps can be hosted on a single Clace serve. Apps are lazy-initialized and scale down to zero when idle. Costs are fixed, there are no unexpected bills when API volume increases.

How is Clace different?

Clace provides a Cloud Run type experience on your hardware. Code and config changes are blue-green staged for deployment. Multiple apps can be updated atomically (all-or-nothing), no broken state after deployment failures.

Clace is built for the application management lifecycle across a team, not just the initial installation. Clace has OAuth support and security sand-boxing features which allow operations teams to easily manage applications through GitOps while allowing development teams to freely make code changes.