Internal Tools Deployment Platform

Hypermedia based low-code internal tools for teams. 
Runbook automation like Rundeck, custom apps like Retool.



Gif with Clace intro commands


Comparison with other low-code solutions

There are many low-code solutions for building internal tools. Most are JavaScript focused solutions which providing UI components which can be configured using a drag and drop UI builder. Backend teams stick to using tools like Rundeck for web interfaces to avoid heavyweight UI solutions.

Clace provides a solution which is focused on providing simple UI for backend actions. Clace allows customizing the UI using server rendering, without requiring any client side JavaScript code. Clace is implemented in Go, avoiding the JavaScript dependency challenges.

Comparison with other deployment solutions

Using Kubernetes for internal tools deployment requires glueing together CI/CD with ArgoCD/FluxCD and IDP(Internal Developer Portal) for app lifecycle management. Managing the infrastructure requires more work than the actual app code.

Clace provides a integrated solution focused on supporting deployment of internal tools. Clace handles GitOps, container image management, blue-green staged deployment and OAuth based app access controls.

How is Clace different?

Clace is built for teams to be able to securely develop and deploy internal tools. Code and config changes are blue-green staged for deployment. Multiple apps can be updated atomically (all-or-nothing), there is no broken state after deployment failures.

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