Hey Product Hunt, I built Cueno because our prompts were scattered across the codebase, Notion, and Slack threads. Every small tweak meant a code change and a redeploy, with no history and no easy way to roll back when something broke. Cueno treats prompts like code, without making you ship code. Every edit is a commit, so you can diff versions, leave notes, and roll back in one click. You define typed variables once and reuse prompts everywhere. You promote changes from draft to staging to production, score them against test cases, and run A/B tests to pick the winner. When you are ready, you fetch the right version for each environment in one call over a typed SDK or REST API. Change a prompt and it goes live in seconds, no redeploy. It is free to start: npm i @cueno/sdk I would love your feedback, especially on the evals and A/B workflow. What does your prompt workflow look like today?

Cueno

Ship prompt changes to prod in one call, no redeploy

Ship prompt changes to prod in one call, no redeploy