Why Prompt Verse runs no model

Most tools in this space start by putting a model inside the product and selling credits. Prompt Verse did the opposite in the pre-beta, and it is worth explaining why.

The thing people actually have a problem with#

People do not struggle to get a model to answer. They already have Claude, ChatGPT or Grok, and they pay for it. They struggle to keep, change and trust the prompts they use with those models. That is a storage, history and testing problem, and it does not need a model to solve.

So the first version solves that problem and leaves the answering to the AI you already use.

What it saves you#

• No second subscription for the same job. Your AI runs the prompt on your own plan. There are no tokens or credits to buy from us.
• No lock-in to one model. A prompt is rendered text. It works with whichever assistant you use next year.
• No surprise costs. Rendering, versioning and sharing are plain code. The plans are priced for the workspace, not for compute.

What it costs you#

You have to connect your AI. Through MCP that is a one-time step of a few minutes, but it is a step. And things that need a model inside the product, like running an eval and keeping the scored run, are switched off in the pre-beta. Your AI can score cases for you in a conversation, but the result does not land in the app by itself.

We think that is the right trade for now. We would rather be exact about what works than ship a half-built runner to look complete.

What changes later#

The Premium and Max plans carry the AI features of the app, running prompts, agents, workflows and evals inside Prompt Verse. The code exists and is switched off during the pre-beta. When that changes, the changelog will say so.

The short version#

If you take only the storage and history parts of Prompt Verse and nothing else, you still have something useful: a library, versions, evals and sharing. The model is a guest, not the landlord.