Version prompts beside code
ConnectPromptHub
Prompts, shipped like code
SPIRITT puts your PromptHub projects to work. It runs committed prompts inside real workflows, pins exact versions, tests branches against your test cases and tracks cost, usage and timing for every run.

What you can do with PromptHub.

Prompts at work in your apps
Committed prompts generate replies, descriptions and summaries inside live workflows.
Releases tested first
Branches are compared with the default head on your own test set before anyone switches.
Cost you can see
Usage, cost and timing from every run are logged and reported.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the AI features and content workflows you run on your prompts.

02
Connect PromptHub
Connect PromptHub with your API key so SPIRITT can list projects and run committed prompts.

03
Delegate an outcome
Name the workflow and quality bar. SPIRITT runs the prompts, tests changes and reports cost.

Hand over a mission.
Choose a mission. Make it yours.
Put PromptHub to work.
Your best prompts, in production.
Questions
PromptHub, with SPIRITT.
01What can SPIRITT do with PromptHub?+
List projects, read a project's committed head with model configuration, run committed prompts with variables, branches or exact commit hashes, and identify your team.
02How do I connect PromptHub?+
Connect it with your PromptHub API key.
03Can SPIRITT pin a prompt version?+
Yes. Runs can target a branch or an exact commit, so production stays on an approved version.
04Does running prompts use my plan?+
Yes. Each run uses your PromptHub request quota, and SPIRITT records the reported cost and usage.
05Can SPIRITT keep prompts in Git?+
Yes. It commits each project's latest prompt and model configuration to your repository and opens a pull request when anything changes.
06Can it compare prompt versions?+
Yes. It runs different branches on the same inputs and reports quality, cost and latency side by side.





