Enterprise Rollout
Comet's Company-Wide Rollout Goes
From One Machine at a Time to One Click
Perplexity's enterprise AI browser, Comet, now supports bulk deployment through MDM (mobile device management). IT teams no longer need to set up each machine individually — they can push a silent install to macOS and Windows at once. Here's what changed, and how it fits existing audit requirements.
What Happened
From Manual Installs
to MDM Bulk Deployment
Perplexity added silent, bulk deployment of Comet Enterprise to macOS and Windows via MDM. Per Perplexity's own Help Center guide, admins can also use offline installers and manage rollout status from a central dashboard. On top of that, the browser supports more than 500 Chromium-based browser policies, letting IT control exactly which domains are blocked and which actions the agent is allowed to take.
Comet launched broadly in July 2025, with Comet for Enterprise Pro following in August 2025. This MDM bulk-deployment feature lowers the adoption barrier for that enterprise line specifically. Reporting also indicates the security controls were built in partnership with Crowdstrike.
Comet Enterprise's admin controls
Work that used to mean one machine at a time
now fits inside a single dashboard.
Why It Matters
An "AI browser" finally learns
enterprise-software manners
Until now, rolling out Comet meant setting up each machine individually — a real burden for IT, and a real barrier to adoption.
A browser with autonomous agent capabilities is harder to govern than an ordinary one — it can act on the web on its own, which raises the "how much do we let it do" question that tends to block company-wide rollout. What this update shows is that Comet has adopted the same playbook as ordinary enterprise software: bulk distribution via MDM, hundreds of granular policies, and inheriting existing audit-log and retention policies rather than introducing new ones. The novelty of being an "AI browser" matters less here than the more mundane question of whether it can be distributed and governed like any other piece of business software — and that, increasingly, is the real gate to enterprise adoption.
Who It Affects
Who feels this, and how
IT and system administrators
No more per-machine setup — even a rollout of hundreds of devices can be managed from one central dashboard. With 500+ policies, you can tailor permissions team by team.
Security and compliance teams
Because it's designed to inherit your existing audit-log and retention policies, adopting an AI browser doesn't have to mean building a new compliance process from scratch.
Individual Comet users
This update is about enterprise deployment mechanics, not new consumer-facing features — individual usage is unaffected.
What to Do Next
If IT is evaluating this
Check your existing MDM's compatibility
Confirm whether your MDM tool (Jamf, Intune, etc.) already has a distribution profile for Comet Enterprise.
Draft a baseline policy set first
Tuning 500+ policies per team individually is a lot of work — start from a company-wide baseline and layer exceptions on top.
Confirm log retention requirements with legal/compliance
Even though it inherits existing policies, re-check with each department how much logging of the agent's autonomous actions they actually need.
Risks & Open Questions
The flip side of bulk deployment
Easier rollout is welcome, but it cuts both ways: a misconfigured policy now propagates company-wide just as fast as a correct one. Because deployment to hundreds of machines can happen silently within minutes, skipping thorough testing before a production push could mean an unintended domain-access rule or an over-permissioned agent spreads across the whole organization instantly. And since the agent acts autonomously on the web, organizations still need to work out, before rollout, who's responsible when the agent does something a policy didn't anticipate.