Peji and Comet on iPhone, side by side.

The rows below come from two places: the App Store page of each app and its own documentation, read on 30 October 2026. Prices are the list prices on that date and may change. Where a fact comes from the App Store privacy label rather than from the company's own words, the row says so.

If a row says nothing, it means we could not confirm it from a public page and did not want to guess. A comparison with a hole is more useful than one with a guess in it.

Both apps are built on WebKit on the iPhone, because iOS gives a browser no other engine. The difference is the machine that reads the pages. Comet's iPhone app does not run its agent inside the app: it opens a virtual browser in Perplexity's cloud, moves the cookies it needs into it to browse as you, and deletes them when the task ends. MacStories documented it in March 2026 and Comet's own prompt told us the same on 30 October 2026.

Peji runs the agent in the tabs already open on your iPhone. It opens pages, reads them, clicks and types in the same WebKit session you can use by hand, so the sites you are signed into on the phone work without an account elsewhere and the pages you see are the pages the agent reads.

On Peji the page text and the images the agent reads travel to the model and nowhere else. With the built-in provider they pass through the Peji server, which counts usage and forwards them; with your own endpoint the server receives nothing. Chats stay as files on the iPhone.

On Comet an agentic run leaves the phone as a whole session: a cloud browser does the clicking, and it can act on sites your cookies unlock. Comet's explanation in the app says the cookies are deleted when the task is done. What the cloud machine reads while the task runs is the part to weigh, especially on a shop, a bank or a mailbox.

In Peji a run stops before any action that sends, buys, books, pays, publishes or deletes, and asks you. The tools behind those actions go through one gate, and the confirmation names what is about to happen. You can also stop a run at any step and continue it later.

Comet also lets you watch what the assistant is doing and step in: its own materials describe the actions as they happen. What differs is what Peji guarantees by construction: a control that sends, buys, books, pays, publishes or deletes does not run until you answer the prompt in front of it.

Peji stores chats, attachments and files as local files in the app folder on the iPhone. With the built-in provider a request passes through the Peji server, which counts the usage and forwards it, and neither the server nor the model provider keeps a copy. With your own endpoint the server receives nothing at all.

Comet's App Store privacy label, in its October 2026 version, declares browsing history, usage data, diagnostics, contact information and approximate location collected and not linked to your identity. That is a label, not a promise about what the company can read; for the details the Perplexity privacy policy is the document that counts.

Comet is the better choice if you want research more than action. Deep Research, the integrated search, a desktop app with sync and the account you already have with Perplexity are real advantages, and on a Mac the browser has had a year longer to mature.

It is also the better choice if you want one browser for every device you own, and if a desktop browser with cross-device sync matters more to you than an agent that stops to ask.

Peji is the better choice if the work happens on sites where you are already signed in and you do not want an agent to act without you: a purchase, a form, a post, a booking. It is also the choice if you want to bring your own model, or if you want the chats to be local files you can delete with the app.

The trade is scope. Peji is an iPhone app first, with no desktop browser and no cross-device sync, and its free plan runs on a monthly usage allowance rather than a research product behind it.