# Legora

Commercial AI platform for legal work with an agent, workflows and connections to document repositories.

Canonical profile: https://ki-agentenkompass.de/en/agents/legora/
Editor: [Michael Meierhoff](https://ki-agentenkompass.de/en/about/)
Sources reviewed: 2026-11-05
Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests.

## Overview

Legora is a proprietary, sales-led product from a Swedish provider. The agent uses the other Legora tools.

- Provider: Legora
- Product family: Legora
- Profile type: Legal AI platform with an agent
- Environment: Web app; according to the home page also Word and Outlook add-ins and a mobile app
- Connections: Document repositories such as iManage, NetDocuments, SharePoint, Box and Google Drive, data rooms, eDiscovery, contract management and office applications
- Setup: Access goes through sales: the home page offers a demo booking. Administrators set up sign-in (SSO) and integrations.
- Pricing model: No public prices on the reviewed pages; the entry point is a demo booking.

## Key features

### Agent for legal work

The agent analyses the task, selects tools, proposes a plan and carries out multi-step work across documents and data sources. Results sit in the project for review and approval.

Source: https://legora.com/product/agent

### Workflows without code

Lawyers build workflows from Legora tools, reference documents, precedents and style guides. Firm workflows live in a library.

Source: https://legora.com/product/workflows

### Parallel sub-agents

According to the blog post the agent dispatches sub-agents that work in parallel across practice areas, and pauses when judgment is needed.

Source: https://legora.com/blog/introducing-the-agent

### Skills for your own standards

Skills encode processes and standards as reusable instructions so the agent works the way the team does.

Source: https://legora.com/product/agent

### Integrations

Named integrations include iManage, NetDocuments, SharePoint, Box, Google Drive, data rooms, Everlaw, Docusign and Outlook. According to the announcement the connected system remains the source of truth for permissions.

Source: https://legora.com/newsroom/legora-launches-integration-ecosystem-spanning-the-enterprise-legal-stack

### Monitors for regulation

Monitors scan global regulation for relevant updates.

Source: https://www.legora.com

### Security and data region

According to the security page, AES-256 at rest, TLS 1.2 or higher, SSO, a bring-your-own-key option (BYOK) and retention settings apply. According to the page Legora does not use customer data to train or fine-tune AI models.

Source: https://legora.com/security

## Example workflows

### Review a contract draft with the agent

- Your input: A contract draft and your team's standards as a skill.
- Possible result: The agent proposes a plan, revises the document and places the result in the project.
- What to check: Check the plan and changes yourself before approving.

### Build your own workflow for recurring tasks

- Your input: Reference documents, precedents and style guides from your firm.
- Possible result: A workflow in the firm library that colleagues start with their own documents.
- What to check: Improve the workflow with test cases and team feedback.

## Requirements and limits

### Access through sales

Requirement: The home page offers a demo booking and names neither prices nor a trial.

Source: https://www.legora.com

### Workflows run on input

Limitation: The workflows page describes no triggers or schedules; a workflow runs when you supply documents or context.

Source: https://legora.com/product/workflows

### Word Assistant history in the add-in

Limitation: Word Assistant chats are stored in the regional Word add-in and are not moved during the authentication migration. You can export them there, also after the migration, and import them into the Global Word add-in.

Source: https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol

### Memory feature

Not yet confirmed: The agent page and the introduction post describe no memory feature; only Skills capture standards.

Source: https://legora.com/product/agent

### Hosting locations and subprocessors

Not yet confirmed: The security page names no hosting locations and no subprocessors; the region is set by the contract.

Source: https://legora.com/security

## A good fit if …

- your firm wants a legal agent with workflows and connections to document repositories
- you want to review and approve the agent's work product in the project
- you want to set the data region by contract and use SSO via SAML or OIDC

## Less suitable if …

- you want to compare prices or try it yourself without talking to sales
- you need a documented memory feature across sessions
- you need a self-run or open-source solution

Editorial assessment based on provider documentation. Not a product test.

## Usable AI models

Models not stated

According to the vendor, Legora's agent harness handles model selection and the platform is not tied to one model. The benchmark tests models from Anthropic, OpenAI and SpaceXAI but says explicitly that only some of them are live. The pages checked do not name which models actually run in Legora.

- Model families named: None named
- Model choice: The product chooses
- Your own API key: Not stated
- Router or custom endpoint: Not stated
- Local models: Not stated

Partly documented · Sources accessed on: 2026-11-05

- [Legora: Benchmark for Agentic Reasoning](https://legora.com/bar)

- [Legora: aOS](https://legora.com/product/aos)

- [Legora: Security](https://legora.com/legal/security)

## Europe & regional availability

Security page, security policy and privacy policy reviewed. The Trust Center page delivered no content when fetched.

Reviewed scope: Hosted platform; region per contract
Reviewed on: 2026-11-05

### Data region per customer agreement

With requirements

According to the security policy, customer data is hosted in data centres in the region set by the customer agreement. Vendors that process it must be in the EU or GDPR-compliant. The cloud runs on Azure. The privacy policy says the subscriber selects the region for its content.

Region covered: EU/EEA

Documented reason: Which region applies depends on the contract; the pages name no specific locations.

Official source: https://legora.com/legal/security
Official source: https://legora.com/legal/privacy-policy

### EU-based provider and storage control

With requirements

According to the security page the technical team is based in Sweden and operates under GDPR; there are EU-based and US-based technical staff. Where data is stored can be controlled through enterprise security packages.

Region covered: EU/EEA

Documented reason: The page names storage control only for enterprise security packages.

Official source: https://legora.com/security

### Role and transfers outside the EEA

Availability still unclear

Legora acts as a data processor for customer content. The privacy policy applies to that content only in part, mentions transfers outside the EU/EEA and Standard Contractual Clauses. The training platform may process data in the US.

Region covered: EU/EEA, United Kingdom and Switzerland

Documented reason: For customer content the policy refers to the subscriber agreement; it lists no subprocessors.

Official source: https://legora.com/legal/privacy-policy

## Accounts & permissions

Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.

Configuration covered: Hosted platform with administration features
Sources reviewed: 2026-11-05

### Account used

Documented: Legora supports SSO via SAML and OIDC. Administrators run the migration to the new sign-in themselves; according to the help page it cannot be undone. Email-and-password sign-in remains possible depending on the setting.

Evidence: https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol
Evidence: https://legora.com/security

### Admin approval

Documented with conditions: According to the workflows page firms can manage team access with roles and permissions. According to the announcement, ethical-wall and governance tools such as Intapp Walls for AI determine what content Legora can retrieve.

Evidence: https://legora.com/product/workflows
Evidence: https://legora.com/newsroom/legora-launches-integration-ecosystem-spanning-the-enterprise-legal-stack

### Data access & team sharing

Documented: Every tool in Legora is available to the agent. Through integrations it searches and edits documents in connected repositories and saves them back; permissions follow the connected system.

Evidence: https://legora.com/product/agent
Evidence: https://legora.com/newsroom/legora-launches-integration-ecosystem-spanning-the-enterprise-legal-stack

## Prices and included usage

Pricing checked: 2026-11-05

The home page names no prices and no free trial; the offered entry point is a demo booking.

### Legora

No public price; demo booking only

Platform by arrangement with sales.

Price source: https://www.legora.com

Pricing details: https://www.legora.com

## Operation & oversight

Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.

Deployment covered: Hosted operation by the provider
Sources reviewed: 2026-11-05

### Files and working state

Documented with conditions: Agent and Outlook chats are stored in Legora, Word Assistant chats in the regional add-in. According to the security page customers can set retention periods; it names no specific periods.

Evidence: https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol
Evidence: https://legora.com/security

### Sign-ins

Documented: SSO via SAML and OIDC with a custom sign-in address per organisation. Members who keep email and password need a new password of at least 15 characters; MFA settings may need to be set up again.

Evidence: https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol
Evidence: https://legora.com/security

### Starting further runs

Documented with conditions: According to the page the agent monitors email, documents and projects and acts when something needs attention; the page describes no triggers or schedules. Workflows run when you supply documents or context.

Evidence: https://legora.com/product/agent
Evidence: https://legora.com/product/workflows

### Human intervention

Documented: The agent places work product in the project for review and approval and, according to the introduction post, pauses when judgment is needed.

Evidence: https://legora.com/product/agent
Evidence: https://legora.com/blog/introducing-the-agent

### Detecting errors

Documented with conditions: According to the page the agent checks whether it achieved the goal and then adjusts or repeats steps. The page does not describe how errors become visible.

Evidence: https://legora.com/product/agent

### Resuming after failures

Open in reviewed sources: The reviewed agent pages do not describe how interrupted runs are resumed.

Evidence: https://legora.com/product/agent
Evidence: https://legora.com/blog/introducing-the-agent

### Editorial assessment

Legora is a managed product with approval in the project and SSO. For memory, error handling, resumption and concrete locations, the contract, Trust Center or sales need to answer.

## Memory and conversation continuity

Scope: Chat history of the agent and assistants; the pages describe no dedicated memory feature
Sources accessed: 2026-11-05

Chats are stored in Legora or in the Word add-in; the reviewed pages describe no feature that remembers preferences across sessions.

### Storage and scope

Documented: Agent chats and Outlook Assistant chats are stored in Legora. Word Assistant chats, including playbook results, are stored in the regional Word add-in.

- [Legora Support: Authentication migration](https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol)

### Selection and timing

Partly documented: Skills capture processes and standards as reusable instructions. The page does not describe how memories are selected automatically.

- [Legora: Agent](https://legora.com/product/agent)

### Inspect, edit and delete

Partly documented: Word chats can be exported from the regional add-in before the authentication migration. According to the security page customers can set retention periods; data is deleted after the contract ends. The reviewed pages do not describe how users delete individual chats.

- [Legora Support: Authentication migration](https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol)
- [Legora: Security](https://legora.com/security)

### Agent and channel boundaries

Partly documented: According to the announcement the connected system remains the source of truth for permissions. The reviewed pages describe no boundaries between agents or channels for chat history.

- [Legora: Integration ecosystem](https://legora.com/newsroom/legora-launches-integration-ecosystem-spanning-the-enterprise-legal-stack)

### Retrieval

Not publicly established: The reviewed pages do not describe how earlier chats or memories are retrieved.

- [Legora: Agent](https://legora.com/product/agent)
- [Legora: Introducing the Agent](https://legora.com/blog/introducing-the-agent)

### Session reset and compaction

Not publicly established: The reviewed pages say nothing about resetting or compacting context.

- [Legora: Agent](https://legora.com/product/agent)
- [Legora: Introducing the Agent](https://legora.com/blog/introducing-the-agent)

## Context

A contract with Legora and legal documents. The reviewed pages do not detail prices, memory features or locations; the Trust Center showed no content when fetched.

Official website, security, privacy and help pages reviewed. The Trust Center delivered no content when fetched. Feature descriptions come from the provider; example tasks are editorial. Hands-on tests are still pending.

## Open points

Europe, availability still unclear:
- Role and transfers outside the EEA

Requirements and limits, not yet confirmed:
- Memory feature
- Hosting locations and subprocessors

## Sources

- https://www.legora.com

- https://legora.com/security

- https://legora.com/legal/security

- https://legora.com/legal/privacy-policy

- https://legora.com/product/agent

- https://legora.com/product/workflows

- https://legora.com/newsroom/legora-launches-integration-ecosystem-spanning-the-enterprise-legal-stack

- https://legora.com/blog/introducing-the-agent

- https://legora.com/blog/legora-workflows-the-orchestration-layer-for-legal-work

- https://support.legora.com/it-admin-guide-legora-s-new-authentication-protocol

## Provider

Legora offers an AI platform for legal work. According to the security page its technical team is based in Sweden and operates under GDPR.

- Operator: Legora
- Organization: Provider
- Website: https://www.legora.com
- Reviewed: 2026-11-05

- Provider source: https://www.legora.com

- Provider source: https://legora.com/security

[Sources and method](https://ki-agentenkompass.de/en/sources/)
