Proxaradocs
Guides/Endpoint Protection

The full install

What the full device install puts on a Mac, every prompt the install shows, and how the trial removes itself when it ends.

Updated June 2026

InstallerFileEditViewWindowHelpMon 9:41 AM
Proxara: Private Demo×
+
trial.proxara.ai/setup
Proxara
Installing on macOS
Proxara Docs ↗✦ Demo environment
Look for this in your Downloads
ProxaraTrial-Mac.pkg
24.5 MB · Just now
proxara-bootstrap.json
355 B · Just now
Open Finder → Downloads, then double-click the installer. The bootstrap JSON is along for the ride. The installer reads it automatically.
Your installer is downloading.
  1. Open the installer.Go to Downloads and double-click ProxaraTrial-Mac.pkg.
  2. Approve the admin prompt.Your Mac will ask once. This lets Proxara install securely.
  3. Wait about a minute.Your dashboard opens automatically when the agent is ready.
Waiting for agent · downloading
Need help? Something not installing?
If something doesn't go to plan
Quick fixes for the three things that occasionally trip up an install.
Nothing downloaded?
Re-download either file with one click. A fresh click is never blocked.
macOS says it can't verify the installer?
Privacy & Security → Open Anyway, then double-click it again.
Closed a system prompt by mistake?
Just double-click ProxaraTrial-Mac.pkg again. It restarts cleanly.
None of the above?
Reply to your invite email. A human reads every reply.
Install Proxara Agent
Introduction
Destination Select
Installation Type
Installation
Summary
The installation was successful.
The software was installed.
Close
Installed. One step left

This page covers the full install: the real Proxara agent on your own machine. If you want a lighter, self-contained look first, the sandbox app opens real ChatGPT and Claude in their own window with nothing to install. For a side by side, see the two ways to try Proxara.

The trial demo is a private, invite-only installation of the real Proxara agent on one machine, inside an isolated tenant, for fourteen days. There is no separate "demo build": the agent and the companion app that install are the same signed binaries a customer fleet runs. The walkthrough above plays the whole macOS install on a loop, exactly as it happens, including every system prompt macOS shows along the way.

How a trial starts

A trial begins with an email invitation. The email carries a one-click link and a sixteen character demo key. Opening the link and entering the key unlocks a short two-step setup: one page that names what is about to be installed, and one page with the install button. The whole pre-install flow runs at trial.proxara.ai and works only with a valid invitation. The trial is not self-serve and the pages are not indexed.

What the install button does

Clicking Install Proxara provisions the trial tenant on the server and starts two downloads in the same click:

FileWhat it is
ProxaraTrial-Mac.pkgThe signed, notarized installer. Identical for every trial.
proxara-bootstrap.jsonA single-use credential, unique to the trial. The installer reads it from the Downloads folder so the agent can fetch its own enrollment.

Because two files arrive from one click, Chrome asks once whether the site may download multiple files. Allowing that is part of the normal path. Both files need to be in Downloads before the installer runs; the setup page offers fresh one-click re-downloads if a browser drops one.

The three approvals

The installer is a standard macOS package. Opening it shows the familiar Installer steps with nothing to configure, and the install itself asks for exactly three things:

  1. Your password. macOS asks before any software installs. This is the standard Installer prompt, answered with Touch ID or the account password.
  2. Access to the Downloads folder. The install step copies proxara-bootstrap.json out of Downloads so the agent can enroll. macOS asks before any installer touches that folder. Choosing Allow here is what lets the trial activate itself; there is no manual fallback step to type or paste.
  3. The trust certificate. After the install finishes, Proxara asks to turn on protection. Approving it adds the per-trial certificate that lets the agent inspect AI traffic on this machine. Current macOS requires this to be an explicit user approval, so it arrives as one more password prompt. The certificate is unique to the trial tenant and carries name constraints in the certificate itself.

If any prompt is cancelled by mistake, double-clicking ProxaraTrial-Mac.pkg in Downloads runs the whole sequence again cleanly. Nothing needs to be undone first.

What happens right after

The setup page that started the download keeps polling while the installer runs. The moment the agent enrolls and reports in, the page advances on its own to the trial console. There is nothing to open manually and no restart.

The first console visit lands on a small set of seeded sample events so the surfaces read correctly before the machine has produced any real activity. Seeded events carry a demo-data marker on the record, so they stay distinguishable from organic activity and can be filtered out. Real events join the same feed as soon as an AI tool is used on the machine.

If something does not go to plan

The installing page keeps a recovery panel below the fold covering the failure modes that actually occur:

  • Nothing downloaded. Fresh re-download links for both files. A direct click is never blocked by the browser, whatever happened to the automatic downloads.
  • macOS says it cannot verify the installer. System Settings, Privacy & Security, then Open Anyway, and run the package again.
  • A prompt was closed by mistake. Run ProxaraTrial-Mac.pkg from Downloads again. The installer restarts cleanly without a fresh download.
  • Anything else. Replying to the invite email reaches a person.

How a trial ends

A trial ends in one of three ways: it expires after fourteen days, the person ends it early from Settings with End trial, or the inviter revokes it. In every case the agent uninstalls itself and deletes its entire local data directory, and the server purges the trial's data plane: prompts, redacted file evidence, signed ingest envelopes, behavioural records, and the identity vault for that tenant. What survives is metadata only, with the per-trial secrets shredded, and the purge itself is recorded as a signed entry on the trial's audit chain.

Scope of a trial tenant

A trial runs the full product, with the tenant scope, retention, and integrations constrained to the trial window. Every page in the trial console shows a persistent demo-environment marker so it is always clear this is a demo tenant rather than a production install. For how the production deployment differs, see MDM rollout and the Trust Center.