Priced on the change you actually release
A fixed annual fee you can budget before the programme starts. One line per landscape per year, sized on one question: how many transports did your legacy development system release in the last twelve months? Never a charge per transport.
One question sizes the line
Count the transports your legacy development system released in the previous twelve months. That count picks the size.
Count by release date, not by creation date: a transport counts when it was released from the ECC development system. Your Basis team can read this from the transport header table (E070) or from your change-request ledger.
Each size is a cap, and a count over the cap rounds up to the next size: 600 released transports is size S, 601 is size M.
The programme year is usually close to the last twelve months. If it is not, size on the last twelve months anyway. If volume later crosses a cap, the landscape moves up from that month, pro rata, with no retrospective charge.
Four sizes, one licence line each
The size is the only variable. The licence fee for each size is quoted per landscape, in the pilot conversation.
| Size | Fits | Released BAU transports a year | Licence |
|---|---|---|---|
| S | One small legacy system, light BAU, short conversion | Up to 600 | Quoted per landscape |
| M | A typical single-instance ECC with an active BAU team | Up to 1,500 | Quoted per landscape |
| L | A large or multi-company instance, or a long conversion | Up to 3,000 | Quoted per landscape |
| XL | Global template, several business units releasing into one development system | Up to 6,000 | Quoted per landscape |
Above 6,000 released transports a year, talk to us.
Every size includes
- The self-hosted box, on one Linux VM in your network
- Up to five repositories for the landscape
- The full S/4 rule pack
- AI conflict resolution with your own model key, or no AI at all
- The review queue, side-by-side review, approve and reject, and the audit export
- Support for defects in the box software and help with install and licence questions
Not included
- Model usage. Your provider bills you directly, under your own key.
- Customising objects. Version 1 covers programs, classes, interfaces, function groups and dictionary objects.
- A hosted tenant Roadmap
The terms, in plain words
Sizes and terms are public. The licence fee is quoted per landscape. The commercial term sheet sets out the full terms for your programme.
- Unit
- One line in the programme budget: per landscape, per year.
- Landscape
- One BAU system and the project system it converts to, both reaching one box, with up to five repositories.
- Crossing a cap mid-year
- The landscape moves to the next size from that month, pro rata. No retrospective charge.
- Later landscapes
- A second and later landscape on the same programme is discounted.
- Term and end
- Runs for the programme. Ends when the legacy system is decommissioned.
- The licence file
- An offline signed file, checked on the box. A lapsed licence stops new changes being processed. It never stops you taking your code out.
- Model spend
- Billed by your own provider, outside the licence. No model-usage fee from us.
- Currency
- Quoted in AUD or USD.
Estimate the dual-maintenance effort you carry today
Set your own numbers. The estimate counts only the transports that go straight through as saved. The rest are counted at full manual effort.
This is an estimate from your inputs. It excludes model spend and the licence fee. The straight-through share is what the pilot measures. The public benchmark gave 21 of 33 objects with no person and no AI, on 25 transports from an open-source project. The default of 50 percent is a starting point, not a forecast.
Start with a four-week pilot
The pilot is a fixed fee, credited against the first year's licence if you adopt.
- Four weeks, one package
- Runs on your first 20 released BAU transports
- Installed by your Basis team from the runbook, target under one working day
- A final report, measured against the pilot acceptance plan
- A fixed fee, credited against the first year's licence on adoption
- You keep your code and every record at exit
The independent security review and penetration test have not been carried out yet. They are scheduled before production use.