I Built a Cloud-Native Workflow Engine for Kubernetes - What Would You Use It For?

Hey everyone, I've been building an open-source workflow engine that runs natively on Kubernetes called Tiny Systems (still working on the name). Not "deployed on Kubernetes" - actually native. Flows are CRDs. Nodes are CRDs. So entire state lives in etcd. No external database. Think n8n or Node-RED, but designed for people who already run Kubernetes and want automation that feels like part of their cluster. Problems I'm solving right now These are ready-to-use solutions you can clone and deploy: Cluster Cost Saver — scales down your deployments every evening, brings them back every morning. Dead simple, saves real money. No Lambda functions, no cronjobs, no external schedulers - just a flow inside your cluster. Pod Failure Alerts — watches pods in real time, catches CrashLoopBackOff, OOMKilled, image pull errors, and sends a Slack message before your users start complaining. Yes, Alertmanager exists, but I get my slack message next second after the crash (not like 1-5min it takes for