Lima is a subscription sized by the tier your estate needs. The whole platform is included at every tier. The price does not change with the rows you move, the connections you add, the jobs you run or the questions you ask. Each entry offer has a fixed scope, a fixed duration and a fixed price, and a scoped quote takes one call.
These rules are the price structure. Ranges follow when the packaging decision is final; the rules do not change.
The subscription is set by the tier: 32C, 64C, 96C, 128C or the cloud equivalent. The tier is chosen from your table count, your row volumes and your run windows in one call, and it is the only thing that sets the price.
Catalog, lineage, quality rules, access policy, the Data Fabric, the Backbone, MDM, ChatLima and governed agents are all included. There is no module matrix and no add-on list.
Each offer names what is delivered, how long it takes and what it costs before work starts. The report at the end is the acceptance test.
When a migration or a first load needs a larger tier for a period, the tier is the only thing that changes, and the price returns with the tier afterwards.
Compute is attributed per team and per data product inside Lima, and cache savings are shown. On the showcase estate the cache saved £1,840 of compute in one month.
Software is the subscription. Delivery is quoted as services, by your systems integrator or by Lima's team, and the software price is the same whoever delivers.
An offer is the first engagement. The subscription starts when the offer's report is accepted.
A scan of your SAP extraction jobs by method, an exposure list against the December 2026 date, a replacement per job and a date plan.
One planning dataset from SAP or Oracle into Kinaxis, o9, Blue Yonder, SAP IBP, OMP or Anaplan, on your planning calendar.
The first ten to twenty mappings, jobs or packages from a legacy integration tool or scheduler converted, run side by side, reconciled and cut over.
Retire a legacy system and keep its history. Inventory in week one; full extraction with control totals; retention tiers; audit access through the Fabric; switch-off criteria signed by finance and audit.
Your largest tables moved and reconciled: terabytes moved, rows per minute, reconciliation variance and cost per terabyte against your current tool.
Exceptions, KPIs and two governed agents on your live SAP, Oracle, WMS and 3PL data, with the baseline measured from day one.
Fifty of your own questions on your own schema: accuracy, latency and access-control correctness measured against your incumbent tool.
Sized by the tier, with the whole platform included. The offers above are credited against it where the plan says so. Delivery by your systems integrator or by Lima's team is quoted separately.
The tier is chosen from your estate in one call. Each tier is one node; 128C also heads a multi-node cluster for terabyte runs.
| Tier | Configuration | What it suits | What is included |
|---|---|---|---|
| 32C | 32 vCPU · 256 GB memory (or the cloud equivalent) | One ERP's nightly delta; a first planning dataset; a department's reporting copies | The whole platform · all connectors · support |
| 64C | 64 vCPU · 512 GB | The reference tier: 600+ tables and 200M+ rows; the 220M-row estimate runs here in about 30 minutes | The whole platform · all connectors · support |
| 96C | 96 vCPU · 512–768 GB | Scripted transforms at volume; archive extracts; several ERPs into one model | The whole platform · all connectors · support |
| 128C | 128 vCPU · 1 TB | Terabyte migrations and decommissioning; the head of a multi-node cluster | The whole platform · all connectors · support |
| Changes the price | How |
|---|---|
| The tier | A larger estate or a heavier run window moves you up a tier; the price moves with it and back again. |
| Deployment form | Lima's cloud, your private cloud or on-premise are quoted separately because the infrastructure differs. |
| Delivery services | Quoted as services by whoever delivers; the software price is unchanged. |
| Never changes the price | Why |
|---|---|
| Rows moved | The engine is licensed by capacity; a migration month costs the same as a quiet month. |
| Connections and connectors | All connectors are included; the twentieth source costs what the first did. |
| Jobs, agents, conversations, questions | None of them is metered. |
| Modules | There is no module matrix. |
Many estates run four tools around their data: an integration tool metered by rows or credits, an orchestrator, a catalog and a quality or observability tool, each with its own contract, renewal and integration work. Lima replaces the four with one subscription. The arithmetic is yours to do; the table is the shape of it.
| Line | Today | With Lima |
|---|---|---|
| Integration tool | Metered by rows, credits or processing units; renewal with a true-up | Included in the tier |
| Orchestrator | Per deployment or per hour; self-hosted operations time | Included (on Airflow) |
| Catalog and lineage | Per asset or per user; a scanning project to keep current | Included; lineage captured as pipelines run |
| Quality and observability | Per monitor or per table; alerts without owners | Included; exception records with owners |
| Integrating the four | Engineering hours every quarter | None: one platform |
| Total | Four invoices plus the hours | One tier |
The tiers and the offers are the price structure; the ranges are published when the packaging decision is final. Until then a scoped quote takes one call, and it is written down before any work starts.
No. The whole platform is included at every tier.
The tier is the only variable. A renewal at the same tier is quoted before the term ends, with any change explained.
Yes. The offers are software with a fixed scope. Delivery is quoted as services by whoever delivers, and the software price is the same either way.
Nothing beyond the tier. The Backbone is included; if its workloads need a larger tier, that is the only change.
Thirty minutes on your estate. You leave with the tier, the reasoning and a fixed-price first engagement in writing.
