openrun

the container build and startup. There are lots of tools which simplify web app deployment. Most of them use a UI driven approach or an imperative CLI approach. That makes it difficult to recreate an environment. Managing these tools when multiple people need to coordinate changes is also difficult. Any repo which has a Dockerfile can be deployed directly. For frameworks like Streamlit/Gradio/FastHTML/Shiny/Reflex/Flask/FastAPI, OpenRun supports zero-config deployments, there is no need to even have a Dockerfile. Domain based deployment is supported for all apps. Path based deployment is also supported for most frameworks, which makes DNS routing and certificate management easier. OpenRun currently runs on a single machine with an embedded SQLite database or on multiple machines with an external Postgres database. I plan to support OpenRun as a service on top of Kubernetes, to support auto-scaling. OpenRun implements its own web server, instead of using Traefik/Nginx. That makes it possible to implement features like scaling down to zero and RBAC. The goal with OpenRun is to support declarative deployment for web apps while removing the complexity of maintaining multiple YAML config files. See https://github.com/openrundev/openrun/blob/main/examples/uti... for an example config, each app is just one or two lines of config. OpenRun makes it easy to set up OAuth/OIDC/SAML based auth, with RBAC. See https://openrun.dev/docs/use-cases/ for a couple of use cases examples: sharing apps with family and sharing across a team. Outside of managed services, I have found it difficult to implement this type of RBAC with any other open source solution.

the container build and startup. There are lots of tools which simplify web app deployment. Most of them use a UI driven approach or an imperative CLI approach. That makes it difficult to recreate an environment. Managing these tools when multiple people need to coordinate changes is also difficult. Kubernetes is the standard for declarative deployment. OpenRun supports only web apps, there is no plan to add support for deploying databases or queues etc with OpenRun. That makes OpenRun much simpler, a single binary which implements the web server and application server with GitOps driven deployments. Deploying and managing stateful database type services is much more complex. Declarative web app deployment is much easier. The goal with OpenRun is to support declarative deployment for the web apps while removing the complexity of maintaining multiple YAML config files. See https://github.com/openrundev/openrun/blob/main/examples/uti... for an example config, each app is just one or two lines of config. OpenRun currently runs on a single machine with an embedded SQLite database or on multiple machines with an external Postgres database. I plan to support OpenRun as a service on top of Kubernetes, to support auto-scaling. OpenRun implements its own web server, instead of using Traefik/Nginx. That makes it possible to implement features like scaling down to zero and RBAC. OpenRun makes it easy to set up OAuth/OIDC/SAML based auth, with RBAC. This makes it possible to share your apps securely, see https://openrun.dev/docs/use-cases/ for a couple of such use cases. Outside of managed services, I have found it difficult to implement this type of RBAC with any other open source solution.

AML insanity. Running a command like clace sync schedule --approve --promote github.com/claceio/clace/examples/utils.star is all it takes to setup full GitOps, starting a background sync which creates new apps and updates existing apps with three way merge.

insanity. Running a command like clace sync schedule --approve --promote github.com/claceio/clace/examples/utils.star is all it takes to setup full GitOps, starting a background sync which creates new apps and updates existing apps with three way merge.