App Deployment Simplified.

Open source alternative to Google Cloud Run and AWS App Runner. 
Easily deploy internal tools across a team.

Installation
Install OpenRun:
curl -sSL https://openrun.dev/install.sh | sh
Start OpenRun server (in a new window):
openrun server start &
GitOps in One Command
Schedule a sync:
openrun sync schedule --approve --promote github.com/openrundev/openrun/examples/utils.star
Starts a background sync which automatically creates new apps and updates existing apps, reading latest app config and code from Git.

Comparison with other self-hosted solutions

Compared to solutions like Coolify, CapRover, Dokploy, Dokku etc, OpenRun has:
➣ Declarative GitOps interface, for code and for config. New apps can be added through config updates in git, without CLI commands or UI operations
➣ OAuth access controls for apps and API audit logging features required by teams for internal tools
➣ Single binary, Docker/Podman is only dependency, does not depend on a third party webserver like Traefik/Nginx

OpenRun is built as a self-hosted Google Cloud Run/AWS App Runner alternative as against full PaaS solution. OpenRun does not support deploying auxiliary services like databases and there is no Docker Compose support.

Comparison with Cloud services

Compared to Cloud services like Google Cloud Run and AWS App Runner, OpenRun provides:
➣ Easy app provisioning on your hardware, in your network, enabling network level security controls
➣ Better cost management for apps requiring custom hardware or higher instance limits
➣ Add OAuth/OpenID access controls to apps, with zero app level changes

Compared to heavyweight solutions built on Kubernetes, OpenRun provides:
➣ Single service as against glueing together services like ArgoCD/FluxCD for CI/CD, IDP for app management etc
➣ Simple declarative config, no YAML files, no webserver DSLs.

Common use cases

OpenRun can be used by teams to:
➣ Deploy web apps with zero config required for most common frameworks like Streamlit/Gradio/FastHTML/NiceGUI etc.
➣ Replace Jenkins/Rundeck jobs, using OpenRun Actions for automating operational scripts
➣ Expose web apps for internal REST APIs, replacing manual curl commands

While the auth and auditing features of OpenRun are built for use by teams, OpenRun can also be used by individuals for:
➣ Zero-config dev env setup locally
➣ Host web apps exposed publicly, with OAuth enabled or otherwise