Workspace for judicial operations, internal matters, and integration-ready APIs.
NEXULEX
Product

A Chile-first legal SaaS built around connected causes instead of disconnected spreadsheets.

Nexulex brings together OJV monitoring, internal matters, operational work, public lookup tools, billing, and developer tooling inside one workspace for legal and technical teams.

Sign upView pricing
Open API docsView OJV status

01

OJV monitoring

Search, validate, and monitor connected causes with activity, cuadernos, delays, permissions, and operational context.

02

Internal matters

Use the internal matter as the coordination layer for owners, metadata, documents, cost, time, and multiple connected causes.

03

Work and calendar

Tasks, calendar, and work queue stay attached to the real judicial record and to clear team ownership.

04

Lookup and context

Rutificador, jurisprudencia, public OJV health, and support all live inside the same operating narrative.

Operating architecture

Every module shares the same core unit: the connected cause.

Daily operations, billing, API allowance, and admin visibility all stay aligned around OJV or other scraper-backed causes connected to the organization.

OJV monitoring
Search, validate, and monitor connected causes with activity, cuadernos, delays, permissions, and operational context.
Internal matters
Use the internal matter as the coordination layer for owners, metadata, documents, cost, time, and multiple connected causes.
Work and calendar
Tasks, calendar, and work queue stay attached to the real judicial record and to clear team ownership.
Lookup and context
Rutificador, jurisprudencia, public OJV health, and support all live inside the same operating narrative.
Billing and governance
Connected-cause billing, API allowance, coupons, financial profile coverage, and organization controls without losing traceability.
Developer API
Organization-scoped keys, bilingual docs, and audience-aware routes so builders can integrate without hidden rules.
Real workflow

How a Chilean team actually uses Nexulex.

The product does not split judicial tracking from internal coordination. It keeps the role, the matter, the work, the lookup flow, and billing in one system.

1

Validate the role, tribunal, or filing in OJV before starting tracking.

2

Link the connected cause into an existing internal matter or create a new one inline.

3

Assign teams, owners, internal state, and metadata without losing the judicial origin.

4

Operate from activity, tables, work queue, and calendar using the same connected cause.

5

Consult jurisprudencia or rut lookup when the matter needs extra context.

6

Close the loop through billing, API usage visibility, and organizational governance.

Teams

Built for different legal operations that still need one source of truth.

Litigation firms
For teams living inside OJV that still need a cleaner internal matter layer around the real judicial file.
In-house legal
For teams that need ownership, documents, time, and cost control even when one matter links several connected causes.
Collections and high volume
For operations that think in capacity, bundles, caps, and organization-wide standardization.
Technical integrators
For builders who need API usage control, audience-scoped docs, and billing that matches real consumption.
Designed for Chile

The language, structure, and pricing model match local legal operations.

It speaks in OJV, PJUD, rol, caratulado, tribunal, sala, RUT, and razon social.

It separates connected causes from internal matters so billing follows the real judicial record.

It explains CLP, IVA, bundles, lump sums, and API allowance without hiding the rules.

It keeps public OJV status visible so support and operations start with real context before escalation.

OJV / PJUDRUT / razon socialCLP / IVA
Technical trust and governance

The same platform works for the lawyer reviewing a cause and the admin watching capacity and access.

Keys and audience
Organizations manage their own API keys and only see routes that belong to their audience.
Explainable billing
Every invoice can show billable connected causes, included API allowance, and metered overage when it exists.
Visible operations
Admin, billing, and support work with the same capacity posture, warnings, and invoice backlog.
Open API docsView OJV status

Run judicial operations, internal work, and technical consumption from one surface.

Create an account, review the pricing model, and start with a structure tailored to Chile from day one.

Sign upView pricing