Skip to main content
Prompt Hub is OpenLIT’s prompt management platform: a place to create prompts, save them as explicit versions, and fetch them at runtime from your application instead of hardcoding prompt text in your codebase. It’s built for teams who want prompt changes to ship independently of a code deploy, with a full history of what changed and when. At a high level, Prompt Hub covers three things: creating and editing prompts in a dedicated editor with variable support, versioning each save as either a draft or a permanent published version, and fetching a prompt (by name or ID, optionally a specific version) from the SDK or API with {{variableName}} placeholders compiled in for you.

Manage Prompts

Create, edit, tag, and delete prompts from the list and detail pages

Versioning

Drafts, semantic versions, and how the Versions tab tracks history

AI Prompt Improvement

Let Otter review a prompt and suggest edits directly in the editor

Rules

Link a prompt to Rule Engine rules so it’s returned automatically at evaluation time

Retrieve a Prompt

Fetch and compile prompts at runtime via the SDK or API

​
Frequently asked questions

Prompt Hub lets you treat prompts as versioned artifacts - create them once, save changes as a draft or a permanent version, and fetch them at runtime via SDK or API instead of hardcoding prompt text in your application.
There’s no rollback or restore button in the UI - viewing an older version on the Versions tab is read-only. To bring old content back into the editor, you’d copy it into a new edit and save it as a new version. If you just want your application to use an older version’s text, fetch that specific version directly via the SDK/API version parameter without touching the published history in the UI.
Use {{variableName}} placeholders anywhere in a prompt’s content, then pass a variables map when fetching it via the SDK or API with compilation enabled - OpenLIT substitutes the values into the text at request time.
Both are supported. Saving as a Draft keeps your work private and repeatedly editable without publishing anything. Choosing Major, Minor, or Patch always publishes a new, permanent version - publishing never overwrites an earlier one.

Manage LLM secrets

Centrally store LLM API keys that applications can retrieve remotely without restarts

LLM playground

Run a saved prompt across multiple LLMs side-by-side and compare cost, speed, and quality

Rule Engine

Match runtime inputs against conditions to return prompts and other linked resources automatically