There is too much friction in deploying internal tools. I have been building https://github.com/openrundev/openrun to solve that. Full GitOps (create/update your app through GitOps, not just updating app source code), staged deployments, service bindings (for getting a managed database credential, instead of creating a new database per app) and OIDC/SAML with RBAC.

▲

aleqs an hour ago | parent [-]

Very interesting project! I haven't fully read through yet - does it deploy to existing resources/infra, or does it handle resource/compute provisioning as well? How are you handling keys/creds?

Do you have any real users yet?

I'm working on a open resource/compute provisioning protocol/system (not released yet), targeting both cloud platforms as well as internal, which may go hand-in-hand with what you're building.

	▲	ajayvk 21 minutes ago \| parent [-]
		OpenRun runs on a single machine, with either Docker or Podman. All apps runs on that one machine. Idle apps are scaled down to zero, so resource usage is low even when hundreds of apps are installed. For scaling up, OpenRun can be deployed on Kubernetes. Each app deployed through OpenRun gets created as a Kubernetes deployment, again with scaling down to zero. Same declarative config moves from singe node to Kubernetes, no changes required. I don't have any telemetry, so not sure about number of users. Based on issues filed, lots of users using the single node deployment (which is good enough for most use cases). Started with Streamlit/Gradio type apps, now users are actually using it for deploying vibe coded internal tools. See https://github.com/openrundev/openrun/issues?q=is%3Aissue%20...