Using Phoenix Prompt for Library, Versioning & Maintenance

·Jul 31, 2025 01:40 PM

Hello team, I have a question.. is the Phoenix Prompt management be used as prompt library, versioning, maintenance? How is this backed?

6 comments

· Sorted by Oldest

RunLLM
APP
·
Yes, Phoenix Prompt Management is designed to serve as a prompt library with full versioning and maintenance capabilities. You can create, store, modify, and tag prompts, track changes over time, and collaborate with others. Each prompt has a linear version history, supports tagging (e.g., "production", "staging"), and can be cloned or edited from any version. All prompt data, including versions and tags, is stored and managed within the Phoenix backend, accessible via the UI or SDKs, and is backed by the Phoenix server’s persistent storage system for reliability and auditability. Prompt management is accessible via the Phoenix UI and both Python and TypeScript SDKs, allowing you to pull prompts by name, version, or tag, and use them programmatically in your applications. This system is designed for high availability, with planned support for caching and fallback mechanisms to ensure reliability even during network issues. For more, see <https://arize.com/docs/phoenix/prompt-engineering/overview-prompts/prompt-management|Prompt Management>, <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts|How to: Prompts>, and <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts/using-a-prompt|Using a prompt>. Would you like more detail on how to use the SDKs or how versioning works internally? Sources: - <https://arize.com/docs/phoenix/prompt-engineering/overview-prompts/prompt-management|Prompt Management> - <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts|How to: Prompts> - <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts/using-a-prompt|Using a prompt>
💡 Hint: Mention RunLLM in the thread for followups.
Naga M.
·
where are these prompts stored? in the Postgres DB? what is the recommendation to update the prompts? form UI or from code?
Naga M.
·
thanks Dylan, how is these records stored in Postgres, is it like a Blob or what is the datatype and also can we control how they are stored?
Naga M.
·
sorry its self hosted option
Naga M.
·
thank you, that answers my question
acloudguy
·
·
🔒[private user] - We are not able to update the promts. Its self hosted solution having Azure postgres as DB. Old Prompts are getting updated but new ones are not getting updated. Strange. What are we missing here ? I saw an GitHub Issue which increased the limit to 200 (https://github.com/Arize-ai/phoenix/issues/7648) How can it be increased as we are unable to update the prompts.

Using Phoenix Prompt for Library, Versioning & Maintenance | Arize AI Community

RunLLM
APP
·
Yes, Phoenix Prompt Management is designed to serve as a prompt library with full versioning and maintenance capabilities. You can create, store, modify, and tag prompts, track changes over time, and collaborate with others. Each prompt has a linear version history, supports tagging (e.g., "production", "staging"), and can be cloned or edited from any version. All prompt data, including versions and tags, is stored and managed within the Phoenix backend, accessible via the UI or SDKs, and is backed by the Phoenix server’s persistent storage system for reliability and auditability. Prompt management is accessible via the Phoenix UI and both Python and TypeScript SDKs, allowing you to pull prompts by name, version, or tag, and use them programmatically in your applications. This system is designed for high availability, with planned support for caching and fallback mechanisms to ensure reliability even during network issues. For more, see <https://arize.com/docs/phoenix/prompt-engineering/overview-prompts/prompt-management|Prompt Management>, <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts|How to: Prompts>, and <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts/using-a-prompt|Using a prompt>. Would you like more detail on how to use the SDKs or how versioning works internally? Sources: - <https://arize.com/docs/phoenix/prompt-engineering/overview-prompts/prompt-management|Prompt Management> - <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts|How to: Prompts> - <https://arize.com/docs/phoenix/prompt-engineering/how-to-prompts/using-a-prompt|Using a prompt>
💡 Hint: Mention RunLLM in the thread for followups.
Naga M.
·
where are these prompts stored? in the Postgres DB? what is the recommendation to update the prompts? form UI or from code?
Naga M.
·
thanks Dylan, how is these records stored in Postgres, is it like a Blob or what is the datatype and also can we control how they are stored?
Naga M.
·
sorry its self hosted option
Naga M.
·
thank you, that answers my question
acloudguy
·
·
🔒[private user] - We are not able to update the promts. Its self hosted solution having Azure postgres as DB. Old Prompts are getting updated but new ones are not getting updated. Strange. What are we missing here ? I saw an GitHub Issue which increased the limit to 200 (https://github.com/Arize-ai/phoenix/issues/7648) How can it be increased as we are unable to update the prompts.