Perplexity’s pricing page says Max includes 45,000 credits for Perplexity Computer, while Pro only promises access with “usage limits best for most users.”
That one line matters more than the launch clip.
The X post said Perplexity Computer was available for Pro subscribers, which is true in the loose marketing sense. But the pricing page does the real explaining. Pro gets access. Max gets the explicit meter. If you run ops at a 20-to-50 person firm, that tells you where Perplexity thinks heavy use starts getting expensive.
The announcement said access; the pricing page said budget
Perplexity’s announcement on X framed Computer as a new capability for Pro subscribers. Useful headline. Incomplete buying signal.
On the pricing page, the plan cards split the product much more clearly:
- Pro: $17 per month billed annually, with access to Perplexity Computer and usage limits “best for most users”
- Max: $167 per month billed annually, with 45,000 credits for Perplexity Computer
That turns Computer from a magic trick into a metered system. Once credits show up, you should stop thinking “chatbot upgrade” and start thinking “task budget.”
The boring constraint is what makes the product legible
Most coverage of agent products still treats availability as the whole story: can it click around a browser, fill forms, make files, run research, and hand back an answer.
The more useful question is simpler: what is the unit of spend once somebody on your team likes it enough to use it every day?
Perplexity answered that question more honestly than the launch post did. The answer is not “unlimited agent work.” The answer is a tiered meter, with the disclosed one living on Max.
That matters for a solo developer running a stack like Perplexity + Linear + Notion + Google Workspace. If Computer becomes your default tool for vendor research, competitive tear-downs, quoting, document prep, and browser-side admin tasks, the annual jump from Pro to Max is not abstract. It is $2,004 per seat per year. Five heavy users would put that at $10,020 annually before you count any adjacent tooling.
What an ops lead should copy from this launch
The product lesson here is not “buy Max immediately.” It is that Perplexity gave operators the right frame by accident.
If you are evaluating browser agents, force every vendor into the same worksheet:
- what counts as one unit of agent work
- where the visible cap appears
- whether the cheap plan is for sampling or steady-state use
- which workflows deserve premium credits and which should stay deterministic
That last point is the one teams usually miss. Browser agents are best at ugly, variable tasks: pulling pricing from inconsistent vendor sites, assembling first-pass research, or navigating one-off internal portals. They are terrible candidates for high-volume repeatable work that should have been an API, script, or Zap in the first place.
Perplexity’s pricing page quietly pushes you toward that same operating model. Use the agent where ambiguity is high. Keep routine throughput somewhere cheaper and more controllable.
The operator read is clearer than the product demo
The useful buried detail is not that Perplexity Computer exists. It is that Perplexity already had to put a number on heavy usage.
For an IT buyer or ops lead, that changes the decision. Test it, isolate it to messy research workflows, and do not budget it like a general-purpose productivity seat yet.