Aakd
Open navigation menu

Open-source contract lifecycle management

Turn agreements into reviewed, owned action.

One contract workspace for solo operators, small teams, and larger organizations. Review cited terms, assign the work they create, and keep every consequential step accountable.

Create workspaceView on GitHub

Self-hostable AGPL core. AI is optional, cited, and reviewed by people.

Static contract operations exampleNorthwind Services Agreement · PDFSource verified

Cited extraction

Ready for review

Quarterly service report

Page 8 · Section 4.2

Owner assigned · review recorded

Obligation

Send quarterly service report

Open
Owner
Operations
Due
Due in 10 days

Scoped API/MCP context

  • Cited source
  • Human review
  • Activity trail

  1. 01

    Upload agreement

    Keep the original document, versions, and contract record together.

  2. 02

    Review source

    Check every consequential suggestion against its exact excerpt and page.

  3. 03

    Assign action

    Confirm the owner, deadline, and required evidence before work moves.

  4. 04

    Prove completion

    Record evidence and preserve a clear, attributable activity history.

Reviewable by design

Review the source before the work moves.

Aakd keeps consequential suggestions connected to their exact source and puts authorized people in control of what becomes trusted state.

01

Source before answer

Review the excerpt and page that support a suggestion instead of accepting a detached summary.

02

Humans keep authority

AI can suggest. Authorized reviewers accept or reject supported extraction fields and obligation suggestions before they are used.

03

Review status stays visible

Supported extraction fields keep their source citation and review status visible to the reviewer.

Operational proof

Give every obligation an owner and an ending.

Move from a reviewed term to accountable follow-up without losing the agreement, source, deadline, or completion evidence.

ObligationOpen

Send quarterly service report

Owner
Operations
Due
Due in 10 days

Give scoped API and MCP clients contract context without handing them decision authority.

Governed contract context

Useful to agents. Governed by people.

Aakd exposes scoped contract context through existing API and MCP interfaces. Cited source, organization access, and human review remain part of the workflow.

Aakd does not claim autonomous legal decisions, unrestricted agent execution, or delegated approval authority. Granular delegated controls are later-phase work.

Agent Gateway

Read-first access model

API / MCP
  1. 01

    Permission-scoped

    Access follows the authenticated organization, role and API-key scope.

  2. 02

    Minimized results

    Return the fields needed for the job instead of defaulting to whole-contract disclosure.

  3. 03

    Cited extraction context

    Supported extraction fields retain source text, source page and review status.

  4. 04

    Current write boundary

    Current MCP mutations enforce member roles and API-key write scope.

Professional CLM breadth

Professional CLM, without the theatre.

Start with one cited action. Reach the broader lifecycle tools when the work calls for them.

  • Repository and search

    Available

    Store PDF and DOCX agreements, organize versions and find contract content.

  • Cited agreement intelligence

    AI optional

    Review extracted metadata, risks, obligation suggestions and cited Q&A when an AI provider is configured.

  • Obligations and renewals

    Available

    Track owners, due dates, reminders, subtasks and completion status.

  • Approvals and signing

    Available

    Coordinate reviews, comments, approval history and optional DocuSeal signing.

  • Authoring and templates

    Later-phase

    The codebase includes editing, templates and redlining, but these are not part of the Phase 0 first-run promise.

  • API, MCP and integrations

    Available

    Use scoped interfaces, webhooks, notifications, imports and supported business-system connections.

Capability status reflects the current repository. Hosted Cloud, SSO/SCIM and formal compliance certifications are not currently offered.

AGPL core

Run the contract stack you can inspect.

Deploy Aakd on infrastructure you control. Keep the open core useful, portable and independent of a hosted service.

  • Documented deployment

    Docker-based guides cover the web app, worker, PostgreSQL, Redis and S3-compatible storage.

  • Provider choice

    Use manual workflows without AI, run Ollama locally or bring supported provider keys.

  • Portable core data

    The community product includes API access and exports without requiring a managed edition.

Read the self-hosting guide
Quick startAGPL-3.0
$ git clone https://github.com/aaked-app/aakd.git
$ cd aakd
$ cp .env.example .env
$ docker compose up

Production deployment requires secure configuration, backups and operational review. The development defaults are not for public exposure.

Straight answers

What is available — and what is not.

Aakd is in Phase 0. Public claims should stay as inspectable as the product.

Is Aakd open source and self-hostable?

Yes. The core is licensed under AGPL-3.0 and can be deployed on your own infrastructure using the documented stack.

Does Aakd make autonomous legal decisions?

No. AI features produce reviewable suggestions and cited answers. Humans retain authority over canonical facts, legal decisions and consequential actions.

Do I need an AI provider to use Aakd?

No. Repository, manual metadata, approvals, obligations and signing flows can work without an AI key. AI-assisted features require a configured supported provider.

Start with one agreement and one cited result to review.

Create a workspace or inspect the source before deciding whether Aakd fits your contract operations.

Create workspaceView on GitHub