[akclace]

Thanks for taking the time to suggest an addition to awesome-sysadmin!

To ensure your Pull Request is dealt with swiftly, please check the following (check the boxes [x]):

• Submit one item per pull request. This eases reviewing and speeds up inclusion.
• Your addition is Free software.
• You have searched the repository for any relevant issues or PRs, including closed ones.
• Any software you are adding is not already listed at any of awesome-selfhosted, dbdb.io.
• Software you are submitting is not your own, unless you have a healthy ecosystem with a few contributors (which aren't your sock puppet accounts). (See disclosure below. I am the author; code contributions are mostly mine, but the project has been public and actively maintained since 2023, is listed in the CNCF landscape, and has an OpenSSF best practices badge and a user community beyond myself.)
• The file you are adding is formatted as described in addition.md.
• Demo links should only be used for interactive demos, i.e. not video demonstrations. If login credentials are required to access the demo, please link to the credentials directly.
• Comments and unused optional fields have been removed.
• The file you are adding uses kebab-case file naming, for example my-awesome-software.yml.
• Values for platform should match the platforms required to install and run the software.
• Any software project you are adding to the list is actively maintained.
• Any software project you are adding was first released more than 12 months ago. (First release Oct 2023.)
• Any software project you are adding has working installation instructions.
• You understand that your Pull Request will be merged at least ~1 week after approval, depending on maintainers time.

---

Disclosure: I am the author of OpenRun, so please weigh my answers below accordingly.

• Why is it awesome?

OpenRun brings declarative, GitOps-based management to web app deployment: app creation and config changes (not just app source) are done by updating config in Git, so the full state of the deployment is version-controlled and reviewable. The same config deploys apps on a single node with Docker/Podman or on a Kubernetes cluster, so there is a growth path without rework. OIDC/SAML auth, RBAC, and audit logging are built in rather than bolted on.

• Have you used it? For how long?

Yes. I'm the author and have run it in production since 2023 (the project was initially released as Clace and renamed to OpenRun).

• Is this in a personal or professional setup?

Professional/team setup, deploying internal tools.

• How many devices/users/services/... do you manage with it?

20+ apps, across single-node and Kubernetes deployments.

• Biggest pros/cons compared to other solutions?

Pros vs Dokku/Coolify/CapRover: fully declarative GitOps config (most alternatives manage app creation/config imperatively via CLI or UI); single-node and Kubernetes support with the same config; built-in OIDC/SAML auth, RBAC, and audit logs without extra components (OpenRun is itself the web server, with no separate Nginx/Traefik needed). Cons: apps must run in a single container (no Docker Compose multi-container apps); targeted at internal tools where databases are externally managed; smaller community than Dokku or Coolify.

• Any other comments about your use case, things you've found excellent, limitations you've encountered... ?

AppSpecs allow zero-config deployment of Streamlit/Gradio/FastHTML/NiceGUI-style apps (no Dockerfile needed); idle apps scale down to zero.