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
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.
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.
Clicking Install Proxara provisions the trial tenant on the server and starts two downloads in the same click:
| File | What it is |
|---|---|
ProxaraTrial-Mac.pkg | The signed, notarized installer. Identical for every trial. |
proxara-bootstrap.json | A 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 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:
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.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.
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.
The installing page keeps a recovery panel below the fold covering the failure modes that actually occur:
ProxaraTrial-Mac.pkg from Downloads again. The installer restarts cleanly without a fresh download.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.
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.