The workspace should meet
legal teams where they work.
Legal work already lives somewhere — in Word, in a document management system, in a research subscription. An integration page is only useful if it distinguishes what is connected from what is merely intended.
Integration status should be as clear as the legal work it supports.
The product keeps a registry of every intended connection and the state it is actually in. Nothing in the workspace is labelled connected before it is, and nothing on this page should be read as a commercial relationship with the companies named.
How status is handled
Most legal AI integration pages are a wall of logos. This one is a register, because a logo is not a statement of fact.
An honest registry
The authenticated product carries an integration registry that names each intended connection and its real state.
Protected settings
Integration settings are behind authentication and owner-scoped, so the register reflects your account rather than a marketing page.
No connection is implied
A third-party name on this site describes a design target. It does not indicate a partnership, a licence or an available connection.
Boundaries exist in code
Provider binding boundaries are defined in the codebase, so a connection can be added without redesigning the product around it.
What works today: files
The connection that exists now is the oldest and most reliable one in legal practice — a document that moves.
Upload in
Bring in plain text, Markdown, DOCX and PDF, extracted and made available to the requests you choose. Scanned pages go through OCR where that service is configured.
Real DOCX out
Export a genuine Word file with legal page setup, which opens in the tools the rest of the matter already uses.
Private storage
Files are stored privately with signed access and integrity checks rather than in a shared public location.
No round trip yet
A document exported to Word and edited there does not flow back. That sync is planned, not built.
What is intended, and honestly not here
Naming what is missing is more useful to a firm evaluating the product than another row of logos would be.
Microsoft 365 and a Word add-in
Requires app registration, scopes and tenant consent before any claim can be made. None of that is in place.
Document management systems
iManage, NetDocuments, SharePoint, OneDrive and Google Drive are design targets with no live connection.
Legal research providers
No commercial case-law provider is connected, and no agreement with one is claimed.
Enterprise identity
SSO, SAML and SCIM are planned for an enterprise release and are not available.
IN PRACTICE
The work lawyers bring to it.
Bring the executed agreement in
Upload the DOCX or PDF the matter turns on and put it directly into the request's context.
Take the draft to Word
Export a finished memorandum as a real Word file and continue in the firm's existing review chain.
Load the firm's precedent
Add internal precedent and guidance as private firm knowledge, separate from matter evidence.
Check what is actually connected
Open integration settings in the authenticated product and read the current state rather than inferring it from a website.
HOW THE WORK MOVES
A visible record from input to review.
01Authorize source
02Select matter scope
03Retrieve permitted context
04Use in research
05Trace contribution
06Return work product
IN THE WORKSPACE TODAY
What you can use now.
Not yet available: Microsoft Word add-in and Microsoft 365; iManage, NetDocuments, SharePoint, OneDrive, Google Drive; Commercial legal research providers; SSO, SAML and SCIM.
Document upload and extraction
TXT, Markdown, DOCX and PDF, with OCR fallback where configured.
Live
DOCX export
Real Word output with legal paper and layout.
Live
Integration registry and protected settings
Authenticated, owner-scoped and honest about state.
Live
Astra for Law
Legal model integration coming soon
◆
PRIVATE BETA
Keep the research visible. Keep the document yours.