[ LEGAL TECH ]
The open-source Clio and MyCase connectors run on one laptop, for one person. Firm-Wide Deployment runs the same connection from a single place your firm controls: each attorney signs in as themselves, every action carries their name, and there is one audit log for the whole firm.
One place
every attorney connects to
ABA 512
one audit log, names attached
Yours
on a server your firm owns
There is no price on this page on purpose. The number depends on how many attorneys, which practice management system, and where the server lives — so it is scoped per firm and quoted fixed after one call. Ask, and you'll have it.
[ WHY FIRMS ASK FOR THIS ]
We built the open-source Clio and MyCase connectors, and for a solo attorney or a first pilot they are exactly right. A firm hits three walls with them.
The npm install lives on a single laptop and holds a single attorney's credentials in that machine's keychain. That is by design — and it means the setup ends where that laptop ends.
A firm means five installs, five configs, five machines where something can break — and the least technical attorney is the one stuck at 6 p.m. before a filing, with nobody accountable for the error on their screen.
Each laptop keeps its own log. Nobody can answer "what has AI touched in our case files this month" for the whole firm — and that is the question a managing partner, and ABA Opinion 512, actually asks.
[ WHAT FIRM-WIDE LOOKS LIKE ]
The connector runs as a service on a server your firm owns or controls — your cloud account or your office hardware. Attorneys connect their Claude to it. No per-laptop installs to babysit, no re-doing setup when someone gets a new machine.
Each attorney authorizes with their own Clio or MyCase account. When Claude creates a task or a note, the record shows which attorney did it. No shared logins, no office account everyone hides behind.
Every action, every attorney, one append-only record your firm keeps — mapped to ABA Opinion 512 supervision duties. When someone asks what AI touched and who approved it, the answer is in one place.
We build it, document it, onboard each attorney, and hand your firm a runbook your IT contact can operate. Errors get a person to call instead of a search through GitHub issues.
[ HOW IT RUNS ]
This is an engagement, not a download. The open-source connectors stay free; this is the work of turning one of them into your firm's shared, supervised setup.
Step 1
How many attorneys, Clio or MyCase or both, where the server should live, which Claude plan the firm holds, and which workflow proves it on real matters. You get a fixed quote after this call — the quote is the price.
Step 2
We stand the connector up in your environment, wire per-attorney sign-in and the firm audit log, and test the first workflow against real matters with your champion attorney.
Step 3
Each attorney connected and shown the ropes, runbook delivered, your IT contact trained, and a support window for the wobbly first weeks. Your firm owns and operates what we leave behind.
[ WHERE THIS SITS ]
The open-source connector from npm. One attorney, one laptop, five minutes if you are comfortable in a terminal. MIT licensed, yours forever.
We configure one attorney's machine with you: scoped credentials, audit log destination, a first workflow, and training. The fastest way to prove the value to the partners.
One central deployment on a server your firm owns. Every attorney signed in as themselves, one audit log, a runbook, and someone accountable.
[ WHO YOU'LL TALK TO ]
No SDR, no handoff. The people who built the connectors scope the deployment. Vet us on LinkedIn first if you like, or follow Oktopeak on LinkedIn.
Every client we lost to a cheaper option came back with a broken codebase and a missed compliance deadline. Ten years of watching the same mistake. So we quote a fixed price, put senior engineers on it, and don't move on until it passes. Regulated software has to work the first time. No second chances with HIPAA.
Co-founder & CEO, Oktopeak
Same pattern everywhere: great companies stuck with bad software options. SaaS that doesn't flex. Agencies that bill hourly and disappear. We built the opposite. Fixed price, compliance-first, shipped. Every project, I'm on the call and in the codebase. That won't change.
Co-founder & Technical Lead, Oktopeak
[ FAQ ]
The free open-source connector is the same foundation, built for one person: it installs on one laptop, holds one attorney's credentials in that machine's keychain, and keeps its log on that machine.
Firm-Wide Deployment is an engagement where we run that connection from one central place your firm controls, with each attorney signing in as themselves and one audit log for the whole firm. Same open-source core you can read on GitHub, deployed for a team instead of a laptop.
Guided Setup gets one attorney's machine configured properly, with scoped credentials, an audit log destination, and training. Firm-Wide Deployment replaces per-laptop installs entirely: one central deployment every attorney connects to.
Many firms start with one guided attorney to prove the value, then go firm-wide once the partners have seen it work.
On a server your firm owns or controls, in your firm's cloud account or on your office hardware. We build it, configure it, and hand over the runbook; your firm holds the credentials, the tokens, and the audit log.
If you want us to administer it on an ongoing basis we can agree that separately, but the default is that you own and operate what we deliver.
It depends on which Claude plan your firm holds, which is why we ask on the scope call. On Claude Team and Enterprise with training disabled and zero data retention, your prompts and case data are not used to train models and are not retained by Anthropic.
The deployment adds firm-side controls on top: each attorney sees only what their own practice management login allows, and every action is recorded in an audit log your firm keeps. We cover this in detail in Which Claude plan should a law firm buy.
There is no list price because the number depends on your firm: how many attorneys, Clio or MyCase or both, where the server lives, and which workflows you want verified on real matters.
You get a fixed quote after one scope call, and the quote is the price. No hourly billing.
Yes, and it is a permissions question rather than a seat count. Paralegals and admin staff sign in with their own accounts and see exactly what their practice management permissions allow, with their actions in the same audit log.
Scoping who gets access to what is part of the deployment, not an extra product.
If your practice management system has an API, the same architecture applies: a connector deployed centrally, per-user sign-in, one audit log. Clio, MyCase, and Filevine deploy fastest because we maintain those connectors. Anything else is scoped as a custom build on the same pattern.
Tell us your stack on the call.
[ ONE SETUP, EVERY ATTORNEY ]
30 minutes with a co-founder. We'll walk your attorney count, your practice management setup, and where the server should live — and send a fixed quote for your firm. If the free connector or a single guided setup serves you better, we'll say so.
