What is Open Law?
One framework for every participant
Open Law is the vendor-neutral layer for legal practice data portability — Directory trust, Dynamic Client Registration, and standardised Access APIs.
Inspired by Open Banking's separation of standards from commercial connectivity, Open Law defines how legal practice data is discovered, trusted, and exchanged — so clients can authorise apps of their choice without firms gating access.
Why it exists
Law firms run on fragmented practice management stacks. Clients increasingly expect to choose their own software without waiting for firm IT procurement. Open Law separates open rails (standards anyone can implement) from commercial connectivity (optional hosted products).
Stack at a glance
| Layer | Role |
|---|---|
| Directory | Participants, JWKS, Software Statement Assertions |
| DCR | Register at a firm TSP with an SSA |
| Read/Write API | FAPI 2.0 access to matters, documents, financials, and more |
| Open Data API | Public discovery and price transparency without OAuth |
| Conformance | Prove Directory, auth, and client data boundary behaviour |
Firms (LSPs)
Legal service providers host practice data behind Open Law APIs. Clients authorise access to their own data — firms do not gate which apps clients use.
Find out moredevicesApps (TPPs)
Third-party providers build client-facing or firm-facing software on a common trust and data model — without rebuilding per practice system.
Find out morednsProviders (TSPs)
Technical service providers implement Directory-backed DCR, consent, and Read/Write APIs for one or many firms.
Find out moregavelRegulatory
Open standards, client-visible data boundaries, and self-attested conformance support transparency and marketplace safety.
Find out more