Version chain
Inspect the document order, relationship, scope note, page count, and extraction status.
Centralize executed agreements, preserve immutable version lineage, and connect every source document to the obligations and outcomes it governs.
“Provider shall deliver the agreed work and preserve evidence of completion.”
DataForSEO reports 140 monthly US searches for “contract repository software,” with commercial intent. The verified results consistently emphasize centralized storage, search, permissions, version control, and lifecycle visibility. Reloren provides those repository foundations for executed client agreements and extends them into post-signature execution.
The repository is built for MSAs, SOWs, order forms, amendments, and email agreements used by seller-side service teams. It is not a drafting room or e-signature platform. Its purpose is to preserve the signed source and make the obligations inside that source operational.
Reloren accepts PDF, DOCX, TXT, Markdown, and EML sources up to 25 MB. Retained originals are encrypted, and each document receives a version number, checksum, type, extraction status, and audit context.
Amendments are added as new versions with an amends, supersedes, or incorporates relationship. That prevents a revised file from silently replacing the source that reviewers relied on earlier.
Inspect the document order, relationship, scope note, page count, and extraction status.
Queries and stored records remain scoped to the organization workspace.
Workspace settings govern operational retention while referenced contract versions remain available until workspace deletion.
Finding an agreement is only the first repository job. The next question is what the agreement requires. Reloren proposes source-linked obligation candidates and lets a person turn approved candidates into owned delivery, reporting, acceptance, billing, renewal, service-level, or governance records.
Cross-contract views summarize open, overdue, disputed, and evidence-backed work. The repository therefore answers both “where is the contract?” and “what still needs to happen?”
Contract repositories often end at metadata and reminders. Reloren stores fulfillment proof, client-decision state, and immutable obligation events next to the cited source. A reviewer can trace an outcome back through the evidence to the signed excerpt.
This structure supports audits, client conversations, milestone billing review, and renewal preparation without claiming that the software determines legal compliance.
Workspace roles, invitations, sessions, Google authentication, OIDC, SCIM, scoped API keys, webhooks, and audit exports support shared use. Encrypted backups and restore verification cover the stateful deployment path.
Optional Composio connections can support evidence intake or downstream workflows. CSV exports remain available when a team wants a simple, reviewable handoff instead of an integration.
The sequence stays visible even when the surrounding systems and team responsibilities differ.
Add the signed MSA, SOW, order form, amendment, or email agreement. Reloren accepts PDF, DOCX, TXT, Markdown, and EML files up to 25 MB and retains the original as an encrypted contract version.
Local text extraction proposes obligation candidates with the document, estimated page, clause label, exact excerpt, and confidence. A person approves or rejects every candidate before it becomes active work.
Assign an owner, due date or triggering condition, evidence requirement, acceptance requirement, and billable value. The operating record stays linked to the language that created it.
Attach project artifacts, email, URLs, files, notes, or client confirmation. Record whether the client decision is pending, accepted, disputed, rejected, or waived without rewriting earlier events.
Record billable, milestone, rate-change, renewal, credit, penalty, or recovered-value events. Export obligations, audit history, and commercial records for the systems that remain responsible for invoicing and accounting.
A serious evaluation should test the operating record, not stop at a polished extraction demo.
Ask how files are encrypted, versioned, checksummed, retained, and restored.
Confirm amendments and superseding sources remain visible as separate immutable records.
Decide whether the repository must only find documents or also manage their obligations.
Review tenant boundaries, roles, SSO, provisioning, API scopes, and audit export.
Verify that contract, obligation, evidence, and audit data can be exported.
Reloren is seller-side, post-signature contract execution software. It does not draft, redline, negotiate, sign, or provide legal advice. It does not score legal risk, manage buyer-side procurement, replace CRM, project management, PSA, ERP, or accounting systems, or issue invoices autonomously. Candidate extraction requires human review. Optional integrations are brokered through Composio; the core workflow works without them.
Contract repository software centralizes agreements and related metadata so authorized teams can find, control, and monitor them. Reloren adds immutable versions and post-signature execution records.
Yes. Documents can be typed as an MSA, SOW, order form, amendment, email, or other source and related through version lineage.
Yes. Retained contract sources use encryption, and the application also supports encrypted durable backups.
Contracts can store expiration dates, notice days, renewal types, owners, and due obligations. Reloren expresses these as operating records rather than only email reminders.
Yes. The product includes contract reports, obligation and value views, CSV output, and tenant-scoped audit export.
No. Reloren begins with executed agreements and does not draft, negotiate, redline, or sign them.
Open the synthetic workspace to inspect versions, clauses, obligations, evidence, and value before importing an agreement.