JURO is a multilingual LegalTech workspace built for Uzbekistan with international product and engineering standards. It connects legal questions, source evidence, documents, cases and practical next steps in one protected product environment—not a disconnected AI chat.
Product boundary: the visuals below are original JURO product illustrations and contain no customer data. They explain implemented and developing workflows; they are not presented as live screenshots or a substitute for individual legal advice. AI Avatar is explicitly IN DEVELOPMENT.
Product demo
The 12.6-second loop shows the intended connected flow: question → analysis → source → legal context → next step → document → lawyer. The demo uses only repository-local assets; a static poster is served when reduced motion is preferred.
What JURO can do
JURO brings multiple legal-work surfaces into one system. Availability still depends on account permissions and deployment state; the evidence-led status matrix below remains the source of truth for LIVE, WORKING, PARTIAL and IN DEVELOPMENT boundaries.
How it works
The product is designed around progression, not chat volume: collect the right context, make source evidence visible, keep work protected and turn the result into a practical action. Human assistance remains an explicit step when the current workflow and availability permit it.
AI that shows its sources
JURO’s legal-information path keeps the evidence boundary visible. Query-scoped retrieval, citation eligibility and persisted direct citations are implemented in direct-retrieval.ts and direct-citation-store.ts. The public-source path retrieves relevant Lex.uz and Advice.uz pages; JURO does not claim an official provider API, complete legal coverage or that a source page turns AI output into individual legal advice.
Document intelligence
Document review, comparison, versioning and action-plan surfaces exist in the protected platform. The illustration communicates the workflow, not a claim that every analysis path has completed fresh authenticated end-to-end verification; the status remains PARTIAL where the matrix says so.
AI Avatar — In Development
JURO is developing a visual AI legal assistant for more natural and accessible interaction. The repository does not claim a production avatar, approved rigged character, live lip-sync or a completed voice path. Research, interface prototyping and asset approval remain development work.
Human lawyer hand-off
The hand-off model is simple: preserve the question, sources, documents and action history so a user can request human assistance without rebuilding the case from zero. It is a controlled product workflow—not a guarantee of representation, availability or legal outcome.
Built for production
The self-hosted architecture and operating procedures are described in Self-hosted operations.
The monorepo separates public, protected and administrative surfaces while keeping credentials and data access behind server boundaries. React, Next.js and TypeScript power the frontend; Node.js, PostgreSQL, pgvector and local content-addressed files support the runtime and data layer; OpenAI configuration remains server-side; CI/CD and artifact checks support release discipline.
Product experience
These are repository-maintained product captures without customer data. They complement the explanatory compositions above with real product surfaces.
| Public product | Protected workspace |
|---|
| |
| Public website · multilingual entry and product explanation | Workspace · cases, documents, actions and account-scoped navigation |
| AI legal information | Document builder |
|---|
| |
| AI + sources · structured response and evidence surfaces | Documents · library, guided builder and generated-file paths |
| Document review | Mobile product entry |
|---|
| |
| Review · analysis and comparison entry (PARTIAL) | Responsive experience · narrow public-product preview |
Architecture and product boundaries
flowchart LR
Website[Public website] --> Platform[Platform Node.js server]
Admin[Admin Node.js server] --> Platform
Platform --> PG[PostgreSQL and pgvector]
Platform --> Files[Private local files]
Jobs[Background jobs] --> PG
Jobs --> Files
Platform --> AI[Direct AI providers]
Jobs --> AI
JURO is a monorepo with independently deployable surfaces:
- apps/website powers the public website through React, Next.js and a native Node.js server.
- apps/platform provides protected route handlers, AI evidence, document workflows, cases, authorization boundaries and generated-file flows.
- apps/admin is a separate Node.js administrative surface and remains PARTIAL.
- PostgreSQL, pgvector and private local files back persisted platform data and files; AI and email configuration remain server-side.
- The platform includes DOCX, PDF and ZIP generation paths; email/OTP delivery is captured locally in this private environment.
Solid connections denote implemented or working repository paths; dashed connections preserve PARTIAL or PLANNED boundaries. For the engineering rationale and code map, read Product foundations.
Trust, privacy and legal safety
The repository keeps several operating boundaries inspectable: server-side credentials, backend-mediated database and file access, ownership and workspace checks, source display, and explicit limitations around AI output. No GDPR, ISO, SOC 2, data-residency or legal-outcome claim is made here.
Report a vulnerability privately through SECURITY.md. Do not put secrets, personal data, user documents or production logs in an issue or pull request.
Current status
| Area | Status | Notes |
|---|
| Public website | LIVE | juro.uz returned HTTP 200 on 2026-09-10. |
| Protected platform entry | LIVE | app.juro.uz returned HTTP 200 and redirected to the localized protected login on 2026-09-10. |
| AI legal-information flow | WORKING | Source-aware response and citation surfaces are implemented; broader legal evaluation is a separate release gate. |
| Document builder | WORKING | Persisted document workflows, private storage and generated-file paths are implemented. |
| Document analysis and comparison | PARTIAL | Review and comparison surfaces exist; fresh authenticated end-to-end evidence is not complete. |
| Cases and action plans | WORKING | Case, task and action-plan workflows are implemented. |
| Lawyer directory and consultations | PARTIAL | Controlled profiles, directory and hand-off lifecycle work is incomplete. |
| AI Avatar | IN DEVELOPMENT | The visual assistant is a declared development track; no production avatar, approved rigged character or completed live voice path is claimed. |
| Administration | PARTIAL | A separate admin server and protected administrative flows exist. |
| Production payments | PLANNED | No live payment provider is claimed in this repository. |
Repository map
juro/
├── apps/
│ ├── website/ # juro.uz public website
│ ├── platform/ # app.juro.uz and legal workflows
│ └── admin/ # separate administrative server
├── docs/ # architecture, migrations and operations
├── .github/ # CI, contribution and issue templates
├── .env.self-hosted.example # configuration names only; no secrets
├── SECURITY.md
├── package.json
└── README.md
Quick start
For local development, run npm run local from the repository root. The platform, website, admin service and background jobs run on your PC; only PostgreSQL runs in Docker Desktop. See local development for host document-tool prerequisites, verification emails and stop/start commands.
This branch runs privately on a Linux server with Node.js 22.13+, PostgreSQL 17 with pgvector, Poppler, Tesseract and ClamAV. See Self-hosted operations for installation, configuration, migrations, service startup and backup verification.
npm run install:all
# Configure the ignored .env.self-hosted using .env.self-hosted.example.
docker compose --env-file .env.self-hosted up -d
npm --prefix apps/platform run db:migrate
npm run dev:platform
Start npm run dev:website and npm run dev:admin in separate terminals. All three services bind to loopback. The application uses local storage and direct AI provider APIs; imported legal collections remain unavailable until their integrity checks pass. Email is captured locally, and payments, automatic legal ingestion and production probes are disabled.
Never commit environment files, keys, database exports, user documents or logs.
Quality and testing
From the repository root, with PostgreSQL and document tools available:
npm run type-check
npm run build
npm test
CI checks locked installs, migrations, TypeScript, production builds, native application tests and dependency licences. The rendered application tests require production builds.
Deployment
This branch is an isolated server migration. It does not authorize production cutover, DNS changes or changes to existing Cloudflare resources. The operations guide covers private systemd services and verified backups. Historical deployment documents describe the prior architecture and are not startup instructions for this branch.
Roadmap
| Now | Next | Later |
|---|
| Maintain source-aware information, document workflows, permissions and release evidence. | Complete authenticated verification of document analysis and lawyer hand-off. | Consider payments and wider ecosystem integrations only after their product, security and operational gates are approved. |
Contributing and license
JURO is a product-managed repository. Focused, safe contributions are welcome; see .github/CONTRIBUTING.md and use the supplied issue and pull-request templates. A pull request does not authorize a production deployment, DNS change or access to production data.
No license file is currently included. Reuse rights have not been granted here; contact the repository owner before using code or presentation assets.
Presentation-asset provenance and update rules: docs/github/README_ASSETS.md.
