Hey Product Hunt — I'm Matt, and I built Telos-OS because I kept seeing the same pattern everywhere: teams making critical allocation decisions with spreadsheets, gut instinct, or hundreds of lines of imperative code that nobody could audit. I thought: what if you could describe what you want in plain YAML — your variables, your constraints, your objective — and a solver just figured out the optimal answer? And what if that answer could automatically drive your infrastructure? That's Telos. It's "Infrastructure-as-Physics" — you declare the laws of your system, and the solver obeys them. What makes it different: - Declarative, not imperative. A 30-line .telos manifest replaces 200+ lines of PuLP/OR-Tools boilerplate. - Actuators close the loop. Solver outputs don't just sit in a notebook — they drive Docker containers, Kubernetes replicas, or your own custom systems. - Expression safety by design. No eval(). Every expression is parsed through a linear-safe grammar. Fuzz-tested in CI. - 16+ ready-to-use templates across energy, traffic routing, manufacturing, k8s autoscaling, and portfolio management. Try it right now: pip install telos-os telos run examples/router_minimal.telos --actuator none --params examples/params/router_minimal.json Or play with the interactive browser playground at telos-os.com/playground. I'd love your feedback — what domains would you want to see templates for? What's confusing? What's missing? This is an early-stage project and community input shapes the roadmap. telos-os.com | pypi.org/project/telos-os | github.com/MatthewEngman/telos-framework

Telos-OS

Declarative optimization that turns YAML into decisions

Declarative optimization that turns YAML into decisions