Getting Started
Last updated September 21, 2026
Run Matruno locally, create the first legal workspace, and exercise one legal matter workflow before expanding configuration.
Start with the Local Stack#
Matruno is easiest to evaluate through the root Docker Compose stack. The stack starts PostgreSQL, PgBouncer, Redis, the OpenTelemetry collector, Temporal, the backend, the Temporal worker, the frontend, and the admin panel.
cp .env.example .env
cp .env.example backend/.env
docker compose up --build -d
docker compose ps
Then open http://localhost:3456 for the product UI and http://localhost:5678/docs for Swagger. See Local Development for hybrid commands, health checks, and worker startup.
Suggested rollout order#
- Run the local stack and confirm
/healthand/health/aggregaterespond from the backend. - Complete workspace setup at
http://localhost:3456/setup. - Create or import one legal workflow definition.
- Create the first matter, attach source documents or evidence if the workflow expects them, and start workflow execution.
- Review tasks, documents, agent execution logs, and audit history from the matter detail view.
What success looks like#
The first successful path is small: one legal workspace, one admin user, one active legal workflow definition, one matter, one workflow run, one attorney review or task completion, and visible execution history. Avoid trying to prove every connector or automation path before the basic matter / evidence / legal workflow / review loop is clear.
Keep the first legal workflow narrow
Start with one practice area and one matter type, such as contract review or a general legal request. A legal-compliance sample lives under examples/workflows/. Treat any remaining non-legal example JSON as workflow-shape samples only, not as Matruno product domains.
Was this helpful?