What Legal IT Teams Ask Before Rolling Out Ajax
The rollout request lands in your queue on a Tuesday. The billing committee has already picked a timekeeping tool, and they'd like it on every machine by month-end. Nobody has yet asked whether it survives Citrix, passes a security review, or buries your help desk in tickets. That part is yours.
The questions below are the ones IT directors and the MSPs who run firm networks actually raise before a law firm IT software rollout. Ajax, the timekeeping tool we build, gets asked all five constantly, so here are the straight answers, including the places where the answer is a flat no.
How does it deploy?
It's a per-user application that installs on Mac and Windows, starts automatically at login, and runs quietly in the background while people work. For a single attorney, that's a download and a run. There's nothing to provision on a server, because Ajax is cloud software with no on-premise component to stand up.
For a firm rolling out to fifty timekeepers at once, you don't want to touch fifty machines by hand, so you can push the installer through the same MSI or MSIX tooling you already use for everything else. To be clear about what we do and don't hand you: there's no managed enterprise installer or vendor-run console. You deploy it with your own infrastructure, which is the part your team already has dialed in.
We're on Citrix. Does this break?
No. This is the question that kills a lot of capture tools, so it's worth explaining why Ajax is fine. Ajax reads what's on the screen at the endpoint, the physical laptop or desktop in front of the lawyer, rather than hooking into each application. Because it works at the local device level, it doesn't need to live inside the Citrix VM or the published app. Whether a lawyer's Word session is running locally or streamed through Citrix, Ajax sees the same pixels and captures the same work. The same logic holds for other virtualized or published-app setups.
Does it support SSO?
Yes. Ajax works with all major identity providers, including Okta, Microsoft Entra, and Google. Timekeepers sign in with the credentials they already have, and you manage access the way you manage everything else, so onboarding or offboarding a user is the same motion you run for any other app.
Will it fight our DMS or other desktop tools?
Not in our experience. Ajax captures from the screen without installing plugins or add-ins into your other software, which is where desktop conflicts usually begin. It runs alongside document management systems like NetDocuments and iManage, and we haven't seen it fight them for resources in real deployments. It reads work from those tools the same way it reads anything else on the screen, so there's no separate connector to configure or break; you can see how that plays out across iManage, NetDocuments, and Worldox. And because there's no Word or Outlook add-in to load, there's nothing new to collide with the add-ins your firm already runs.
What about data handling?
This is the section your security reviewer cares about, and it's usually where a tool either clears the bar or stalls. The short version: data is encrypted in transit and at rest, and captured screen data is deleted automatically on a rolling basis rather than kept around indefinitely. The AI subprocessors that help generate entries are contractually barred from training on your firm's data, under zero-data-retention agreements.
There's also a privacy line that matters inside the firm as much as outside it. Draft entries and raw activity are private to each timekeeper until that person releases them. Partners and administrators see rolled-up reporting, things like timekeeper capacity, unreleased hours, and firm-wide activity, never another lawyer's screen or unreleased drafts. For the full write-up, we keep security documentation available for review, and we've mapped the questions that come up most in our law firm AI security-review checklist and a plain-language piece on whether AI timekeeping is safe for law firms.
FAQ
Does Ajax work with Citrix?
Yes. Ajax runs at the local device level and reads the screen, so there's no agent to install inside the Citrix VM or a published application. Capture is identical whether a lawyer's apps run locally or stream through Citrix.
Is there an on-premise version?
No. Ajax is cloud software, so there's no on-premise build for your team to host, patch, or back up. The only thing that lives on firm hardware is the lightweight per-user capture application.
Can we deploy Ajax firm-wide silently?
Yes. You can push the installer through your own MSI or MSIX deployment tooling and it starts silently at login, so a firm-wide rollout doesn't mean visiting each machine. You supply the deployment infrastructure; Ajax supplies the installer.
What does IT have to maintain after rollout?
Very little. We push updates ourselves, the way most modern SaaS desktop apps do, so nobody on your team has to run a patch cycle for Ajax. The day-to-day settings (narrative style, task codes, blacklist rules for excluding an app or a sensitive window) live in the product, and each timekeeper or a firm admin can change them without opening a ticket.
If a rollout is on your desk and you'd rather stress-test these answers than take them on faith, book a demo; we'd rather field the hard infrastructure questions before rollout than after.
