What PromptOps does
PromptOps is the prompt registry for SchneeAI. It treats prompts as versioned, reviewable artifacts — not hardcoded strings buried in services. Prompts are stored separately from code, assigned to features, and resolved at runtime with full history.
Features
| Feature | What it gives you |
|---|---|
| Prompt registry | Central place to define and manage every prompt your services use |
| Version history | Every change is recorded; previous versions stay retrievable |
| Environment control | Promote a version to development, staging, or production independently |
| Rollback | Revert to a prior version quickly when a change underperforms |
| Approval flow | Require review before a prompt version goes live |
| Variables | Define typed variables so prompts render consistently across callers |
| Templates | Reuse prompt structure across features with parameterized inputs |
| Evaluations (coming soon) | Score prompt versions against test cases before promotion |
Why teams pick PromptOps
- Faster iteration. Update prompts without redeploying services.
- Safer releases. Roll back a misbehaving prompt in seconds.
- Clear ownership. Each prompt is tied to a feature and a version author.
- Less drift. Environments pull from the same registry with explicit promotion.
How it fits
PromptOps is the second surface in the SchneeAI platform. The AI Gateway resolves prompts by name at runtime; the Control Plane records which prompt version served which request. Together, the three surfaces give you a fully traceable path from prompt change to production usage.
Get started
Start building with PromptOps, or read the developer docs to register your first prompt.