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.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
