Compass Pro overview
Enterprise plugins for Parlant
Compass Pro is the official set of enterprise plugins for Parlant. It gives the agent you already have more accuracy on long policies, a deeper review of its replies, a hard ceiling on what a conversation can spend, and a voice interface for phone and browser calls. It installs next to the open-source package and plugs into the same server, agents, policies, and tools. Nothing about how you build an agent changes.
- The four things Compass Pro adds to your agents
- How it installs as a one-line change you can undo
- How to get access and whether you need it
Compass Pro comes from the Parlant team. Its job is to give your agents more accuracy, more reliability, a hard ceiling on spend, and a voice interface, without asking you to rebuild anything.
It plugs into the same server, the same agents, and the same policies and tools you have already written. What changes is what the engine can do with them.
Pro adds four things:
| Capability | What it adds |
|---|---|
| Accuracy | A policy distiller in the matching stage, so long procedures and multi-clause policies are judged precisely on every turn. |
| Reliability | A deeper review path at high effort: the reviewer restates the customer's requests, maps the governing instructions and tools, and carries the remaining tasks across steps. |
| Large-scale cost control | A session circuit breaker that stops a runaway conversation from spending, mid-turn if necessary, without anyone deciding anything. |
| Voice | A native voice interface over LiveKit, so any agent can take a browser call or a phone line with your choice of speech providers. |
How it plugs in
Now that we know what Pro adds, let's look at how it gets into your project.
Pro's install path is designed to make it cheap to evaluate. Adopting Pro is a one-line change, and so is going back. You run the agent you already have on the Pro engine, compare, and keep whichever serves you better, with no rewrite either way.
Once Pro is installed, ask your coding agent to serve with ProServer in place of Server:
import parlant.sdk as p
from parlant.pro import ProServer
async with ProServer(models={"*": "openrouter"}) as server: # the only line that changes
agent = await server.create_agent(
id="support",
name="Support Agent",
instructions="Help customers with orders, returns, and billing.",
)
ProServer is a drop-in for p.Server: the same constructor, the same arguments for models, prompts, stores, auth, and the container hooks. Your config.py from parlant init changes in one line.
Underneath, ProServer binds the Pro matcher, responder, and reviewer into the container, the registry that maps each engine component to the implementation serving it, in place of the open-source ones.
This is the same mechanism Overriding engine behavior describes for swapping in your own components. Pro does it for you.
What stays the same
Once you are serving with ProServer, you may wonder what else you need to relearn. The short answer is: nothing.
Everything in these docs outside this section applies unchanged. Policies, observations, tools, retrievers, canned responses, reviews, effort, sessions, customers, authentication, and self-hosting all work the same on the Pro engine.
Your project moves between the two engines by swapping the server class, and back again if you choose.
Note that Pro's prompts are customizable through the same prompts mechanism as the open engine's. They live under their own section names.
Getting access
Compass Pro is licensed commercially. Contact the Parlant team to get a license, or ask in the community Discord if you are unsure whether your deployment needs it.
A good sign that it does: the policies that carry your business are long procedures, a wrong reply has a real cost, spend needs a hard ceiling, or your customers call rather than type. For example, if your returns policy runs to a dozen conditional steps, that alone is a reason to try the first row of the table above.