Compare / Legora
Sandstone vs Legora: A Collaborative AI Workspace, or an Operating System for Legal?
Legora is a collaborative AI workspace — shared sessions, research, document review, tabular review, and drafting, layered over Microsoft 365, with a customer base weighted toward European law firms and a growing in-house presence. Sandstone is built around the in-house function: capturing requests as they arrive, routing them with context, and holding the record of how they were resolved.
Sandstone vs Legora
| Capability | Sandstone |  Legora |
|---|---|---|
| Primary focus | AI-native operating system for in-house legal work | Collaborative AI workspace for legal research, review, and drafting |
| Who it was built for | In-house legal departments serving a business | Law firms first, expanding toward in-house |
| Intake | Structured intake from Slack, email, and business systems | Work begins with a document or a question in the workspace |
| Collaboration model | Legal works a request together, with comments and drafts staying behind the scenes until you choose to involve the business or a counterparty | Shared AI workspace where team members work in the same session |
| Business context | Counterparty history, prior decisions, and relationships attached to each request | Firm data combined with public legal sources |
| Playbooks | Built from your existing contracts and precedent, applied across workflows | Configured positions with fallbacks, applied contextually during review |
| Workflows and approvals | Built step by step, with approval gates at each one | Agentic execution across connected sources |
| Permissions across systems | Permissions mapped across every connected integration | Platform and Microsoft 365 controls |
| Repository and system of record | Serves as system of record for legal work and contracts | Document and matter workspaces |
| Acting back in source systems | Replies and actions go back to Slack, procurement, and contract systems under a shared team identity, with permissions mapped across those integrations centrally | Workspace and Microsoft 365 |
| Language and jurisdiction coverage | Multi-language | Multi-language, with European data residency options |
| Best fit for | In-house teams whose bottleneck is the volume and variety of inbound legal work | Firms and large teams doing multi-jurisdictional research and document review |
Based on publicly available information as of September 2026. Names and trademarks belong to their respective owners. If anything here is inaccurate or out of date, contact us and we'll update it.
Frequently asked questions
Yes, and the difference is what's being collaborated on. In Sandstone the unit is the request: legal works it together, with internal comments and drafts separable from what the requester sees, then brings in a business stakeholder or outside counsel deliberately. A shared AI workspace collaborates on the document or session in front of you. Both are useful; only one of them starts when the business asks a question.
Sandstone works across languages, so multi-jurisdictional teams aren't limited to English. If data residency is a hard requirement for you, raise it early and we'll be specific about what we can commit to rather than answer it in the abstract.
Sandstone does basic research, grounded in your own playbooks, precedent, and prior decisions. It isn't built to replace Westlaw or Lexis, and teams with heavy case law and statutory research needs generally run a dedicated research platform alongside it.
Requests, context, and history live in Sandstone whether the work is done internally or sent out, so instructing outside counsel starts from the full record rather than a reconstruction. Replies come back into your systems under a shared team identity.
