Never let a contract renew in silence
All your contracts in one list; the system warns you as end and notice dates approach, and who approved and who signed stays on record.
Aglima is contract management software that organisations run on their own servers. Contracts are kept in one inventory with their versions, parties, approval and signature status. End and notice dates are calculated automatically and announced by email as they approach. Text inside scanned contracts can be searched.
Before and after
- Contracts live in folders and email attachments
- The version in force is guessed from the file name
- A missed notice period silently extends the contract
- Who is holding up an approval is tracked through email
- There is no way to search inside a scanned contract
- Contracts sit in one inventory, visible by permission
- The version in force and its parties are flagged in the system
- An alert fires as the notice date approaches
- The approval chain shows who it is waiting on
- OCR makes the document text searchable
Contract inventory — upcoming deadlines
This screen is the product's real output: whose notice period has already passed, and what expires this month. A contract whose notice period lapses renews silently; stopping that row from going unseen is the whole reason the inventory exists. Colour never carries the information alone — every row is read with its label and count.
Data table
| Time remaining | Value |
|---|---|
| Notice period passed | 6 |
| Expires within 30 days | 14 |
| Expires within 90 days | 39 |
| Long term | 353 |
How it works
Three steps, no technical detail.
You enter the contract
Parties, term and notice day are entered; the document uploaded. End and notice dates are calculated automatically.
Approval and signature run their course
Who approved, who signed, on what date — every step on record.
You are warned as the date approaches
An email arrives before the notice period expires; nothing renews unnoticed.
What you get
No more missed notice periods
A contract you no longer want does not renew by itself.
Search inside the contract
Even in a scanned PDF you find the contract that mentions a penalty clause.
Data never leaves your organisation
The software runs on your server; contracts are not hosted elsewhere.
Frequently asked questions
Does it run in the cloud or on our server?
On your server. Aglima is installed on the customer's own server; contract data never leaves your network. Only a small control connection exists for licence validation.
Can we search our old scanned contracts too?
Yes, on the enterprise plan. Uploaded scanned documents are converted to text with OCR and become searchable.
Does it renew contracts automatically?
No, deliberately. The system reminds you of the approaching date; the renewal decision and record are yours. A contract that extends by itself is exactly the problem we set out to solve.
What does it cost?
An annual per-user licence starting from 10 users; modules are added as needed. Tell us your user count and we will send a quote.
Plans
Setup and support are included in every plan. Ask for a quote for pricing. Annual per-user license from a 10-user base, with modules unlocked by license flags.
Core
contract lifecycle · single company
- Contract, version and party management
- Signature and archive record
- Upcoming deadline reminders
Inventory
approval chain · reporting · multi-company
- Multi-level approval chain
- Contract inventory and reporting
- Multi-company structure
- Advanced audit trail
Enterprise
supplier portal · OCR search
- Everything in Inventory
- Supplier portal
- OCR search inside documents
- Priority support for licensing and activation
Technical detailsSystem map, process and architecture decisions — for technical teams
-
Ropilo
The license is issued and the installation activated
User and module scope → Signed license file
The license is bound to a machine fingerprint; a server change requires re-activation -
Contract owner
The contract and its version are created
Parties, term, notice day → Draft contract
-
Approver
The staged approval chain runs
Draft contract → Approved contract
-
Contract owner
The signature record is opened and registered
Signature date and archive number → Registered contract
-
Term resolver
Terms are derived into a single source
Effective date + term + notice day → Expiry, notice and destruction dates
The inventory, reminders and destruction calculation all read this one record -
Reminder worker
Upcoming deadlines are announced
Notice and expiry dates → Email alert
-
Term information is stored in one place
The same commercial fact was entered on three screens and the reminder mechanism did not know which to read. The contract term is now authoritative; the other screens are inputs it derives from. Every field has exactly one writer, so nothing overwrites anything.
-
The module gate is server-side
Hiding the screen of an unpurchased module is not enough — its endpoints must be closed too. The module flag is read from the license file and enforced at the endpoint; hiding it in the interface is decoration, not security.
-
The license is bound to the machine
The license file is signed and bound to the installation's machine fingerprint, so a copied license will not run on another server. Because hardware changes are legitimate, permission to accept a new fingerprint sits in the control plane.
Which tier fits you?
Tell us your user count and deployment preference, and we will work out the right tier and price together.
Request a demo