Rilin

Rilin for AI-native Companies

Rilin tracks the licensing restrictions, IP terms, and privacy obligations that decide what you can build.

How Rilin works for an AI-native company

What the licence lets you build with, on the record

Data-use restrictions, field-of-use limits and derivative rights across every sourcing and licensing agreement sit in the register, so what a dataset can be used for is answerable without reopening the paper.

Model licence v4
Allowed
Fine-tune the base modelAny downstream taskclause 4.1
Limited
Train on customer dataOpt-in tenants onlyclause 3.2
Barred
Redistribute weightsNo sublicensing, at allclause 4.4
Limited
Commercial use at scaleUnder 700M monthly usersclause 5.1
Allowed
Benchmark and publishWith attributionclause 6.3
Limited
Ship derivative modelsNamed in the licence onlyclause 4.6

Read the model and compute terms before you commit

Rilin reviews provider terms, and surfaces the IP ownership positions, output rights, indemnity scope and change-of-terms provisions inside them.

Model-and-Compute-Agreement-v3.docx

8.1IP OwnershipCritical
8.3Output RightsCritical
12.4Change of TermsCaution
8.1IP Ownership
Critical exposure

The compute commitment is take-or-pay: ₹18 Cr a year is payable whether or not the capacity is drawn down.

Usage below plan does not reduce the bill, and the term auto-extends for another year unless notice lands 90 days out.

Who owns what you ship

IP assignment across contractor and employment agreements, and IP and indemnity positions in customer paper, held together so ownership across the codebase and the model is traceable to a document.

AssetTraceable to
Fine-tuned model weights
Product codebase
Customer deliverables
Contractor-built tooling
Model licenceclause 8.1 · IP retained by you
Employment agreementsclause 4.2 · Assigned to the company
Customer MSAclause 11.4 · Licensed, indemnity capped
No assignment on fileContractor agreement is silent

Privacy commitments carry a clock

DPA obligations, data-handling commitments, breach-notification windows and customer SLAs land as assigned work, each traceable to the clause behind it.

Licence and spend commitments
Next payment window closes in 5h

Commitment

Due

Owner

Status

Clause 6.1 · Model provider agreementPay model and cloud provider invoices within agreed credit terms

08 AugRTRavi T.
Due

Clause 3.2 · Cloud compute agreementMeet committed cloud or compute spend

09 AugPMPriya M.
Due

Clause 5.2 · Data licence agreementSubmit usage statement to the model or data licensor

15 AugAKArjun K.
Upcoming

Clause 9.3 · Data licence agreementRemove licensed data or models when the licence expires

22 AugNSNeha S.
Upcoming

Clause 7.1 · Enterprise customer termsApply service credits for an SLA breach

04 AugMJMeera J.
Done

Every document diligence asks for, in one place

Data licences, provider terms, IP assignments and customer contracts sit together with obligations extracted, so a data room comes out of the register.

Matter recordDiligence ready
Customer terms38, all on current paper
Model licences9, with permitted use
IP assignments24 signed, 1 open
Privacy recordsDPAs and sub-processors
Audit trailUnbroken since 2025
Adv. Ajit BelliappaSpecialist CounselTechnology and IP
MatterIP assignment gap · tooling
ContractCTR-2026-019
Full matter history attachedConsult Counsel

The contracts you hold and the obligations inside them.

Data licensing and sourcing agreements
Model and compute vendor terms
Customer SaaS and order forms
Data processing agreements
IP assignment and contractor agreements
Data-use and licensing restrictions
IP ownership and indemnity
Privacy and DPA obligations
Usage caps and cost commitments to providers
Customer SLA and data-handling commitments

Built for the most sensitive documents you hold.

Rilin handles signed contracts with the controls enterprise security, finance and legal teams require.

End-to-end encryption

Your contracts are encrypted in transit and at rest.

Role-based access

Every action scoped to a person and logged. Least-privilege by default.

Data residency

Hosted in India or the region your policy requires.

Full audit trail

Every read, edit and escalation recorded, and exportable on demand.

Signing trail

Who signed, approved and amended each contract, with timestamps.

Tenant isolation

Your data is never co-mingled with another organisation's.

Your contracts are never used to train models.

Tenant-Isolated · No Model Training · Your Data Stays Yours

Frequently asked questions

Have a question that needs a human to answer? No problem.

Talk to us
What is Rilin?
Rilin is a contractual liability control platform. It turns signed contracts into operational objects that can be owned, tracked, and executed.
What happens after a contract is signed?
Rilin turns it into a Transaction. Every obligation is extracted, assigned to an owner, given a deadline, and tracked. Each action maps back to the clause it satisfies.
What does Rilin track?
Obligations, deadlines, ownership, and execution status across every material contract. Continuously.
Who uses Rilin?
Any enterprise with regular contractual transactions. Leadership, finance, and legal teams use Rilin to track obligations, assign ownership, and surface risk across their contract stack.
Does Rilin replace outside counsel?
No. Rilin does not replace counsel. If needed, empanelled specialist counsel can be engaged through the platform with full contract context already loaded.
Does Rilin replace our CLM?
No. A CLM manages the contract lifecycle. Rilin manages what the contract requires after it is signed. They solve different problems.

The contracts are already signed.

Do you know what they say?