The Endpoint pilot
The device-pilot route: a demonstration, one meeting, one test laptop, then a small pilot group for fourteen days measured from activation, ending in a decision in writing.
Updated July 2026
The Endpoint Protection pilot is the device-side evaluation, and it runs in four steps ending in a decision in writing: a live demonstration, one meeting, one test laptop, then a small pilot group for fourteen days. Each step has to pass before the next begins, the price is confirmed in the meeting, and the decision meeting goes on the calendar before anything installs. Pilots run on Windows devices, deployed through the management tooling the firm already uses.
The no-install route is different and simpler: the evaluation runs Proxara Connect on the firm's own tenant with nothing installed anywhere. This page is for the firm evaluating the device agent.
The demonstration
The first step involves nothing of the firm's: a live demonstration on Proxara's machines. Client details typed into a real AI tool are caught and replaced before they leave, the reply comes back intact, and the record shows both versions. It exists to answer one question: whether this is worth an hour with the firm's decision maker and its IT contact in the same room.
The meeting
One hour: the person who owns the decision, whoever manages the firm's Windows laptops (in-house IT or the firm's IT provider), and Proxara. The agenda is fixed:
| Topic | What gets answered |
|---|---|
| The fleet | Which Windows laptops, how many, and whether they are managed through Microsoft Intune, another management tool, or an IT provider's system. |
| The AI in use | Which AI tools employees already use, and what client information must never reach them. |
| Traffic and decryption | What the agent touches on a device, what it decrypts on positive AI evidence, and what it never touches. |
| Coexistence | How the agent sits beside the firm's VPN, endpoint security, and web filtering. |
| Install and removal | How the silent install runs, and the exact removal motion. |
| Success criteria | What the firm needs to see by the end for a yes. |
| The price | $30 per person per month for device-wide protection, confirmed in this meeting. |
| The decision | Who approves the rollout and the purchase if the test passes. |
The device security review goes to the firm's IT contact the same day, and the decision meeting is scheduled on this call, so the pilot ends in a decision rather than a follow-up.
One test laptop
Before anything reaches an employee, the agent goes onto one machine IT controls, for three to five business days, deployed through the firm's own management tool rather than by hand, so the motion being validated is the same motion the rollout would use. The checklist is Single-device validation: the install lands silently, the VPN, endpoint security, and filtering are unaffected, AI tools behave, redaction shows on the record with made-up data, and removal restores the device. A failure here stops the pilot before any employee device is touched.
The pilot group
A small group chosen to reflect how the firm actually works: typically a partner or the compliance lead, an advisor, and someone in operations, with more people only where they add a distinct workflow. The push is the same motion as any rollout, expanding the same device group that held the test laptop.
Before the group starts, the pilot agreement puts the whole thing in writing: the exact devices, the AI workflows being evaluated, who receives events, what counts as successful redaction, the acceptable disruption threshold, the uninstall procedure, the price, and who makes the purchase decision.
The fourteen days are measured from the day all pilot devices report in, so a slow rollout does not eat the evaluation window.
Nothing in the window needs tending. The console fills in as the firm works:
| What builds | From when |
|---|---|
| The usage map | Minute one. Which AI tools are actually in use, filled in as employees work. |
| What almost left | The first catch. Each redaction lands on the record as it happens. |
| The Evidence Pack | The last day. It drafts itself from the pilot record, exportable and verifiable offline. It never sends itself. |
The decision
The meeting scheduled at the start has three honest outcomes:
- A purchase. The pilot converts under the subscription agreement. The same environment keeps running: the certificate, the audit vault, and the record carry forward with no migration and no re-enrollment, so the firm's evidence starts on pilot day one.
- A no, with the reasons stated.
- A written list of what was missing. What would have made it a yes, in writing.
If the firm stops, the agent comes off through the same management tool (Rollback and uninstall is the exact restore), and Proxara deletes the environment's data and certifies the deletion in writing.
The governing terms are the Endpoint Protection Pilot Terms: fourteen days, no automatic renewal and no automatic conversion, and the firm owns its data throughout. The pilot runs in a dedicated, single-tenant environment provisioned for the firm, the same model a paid deployment gets; see The private environment.