Pay for value used — not per seat.
Full features in every model; they differ in deployment and ownership. Adding users costs nothing.
Choose how you own and pay for the platform.
SaaS (Cloud)
Subscription · fast start · Apus operates it.
On-premise
License · installed on your infrastructure.
Source-code handover
Source license · strategic investment.
Then choose how it gets into operation.
An ERP project always needs specialists alongside you — surveying how you work, standardising processes, configuring the system around them, migrating data and running in parallel. Apus does not leave a company to self-onboard, because the hard part is not the software.
Essentials — Packaged implementation
Industry template · fixed scope & timeline · go-live in 90-120 days
Custom implementation
Built around your real processes · scope and roadmap agreed
Every edition runs on the same fully featured platform. Essentials differs only in fixing the implementation scope to an industry template. License and handover scope are detailed by contract; SaaS is priced by storage and resources — unlimited, never per-user.
One platform — you choose the level of ownership.
Fully operated by Apus — you use it, no infrastructure to run.
Runs on your infrastructure — data stays in your business.
Own the business layer — extend on your own terms.
An ERP project has three cost lines — we name all three.
No hidden fees, but no single number that fits every company either: each line depends on scope and is agreed before you sign.
Implementation
This line buys consulting, not extra features: we survey how you work today, standardise the processes and configure the system around them.
- Current-state survey & process analysis
- Standardisation advice against industry practice
- System configuration for the agreed processes
- Role-based training & go-live acceptance
Usage
Priced on storage and infrastructure resources — never per user, so adding people costs nothing.
- Follows the capacity tiers published below
- Unlimited users on every tier
- Updates & backups for the contract term
- Over the limit: move up a tier or pay per GB
Data migration
The effort depends on the quality of the data you already hold, so this is its own line — never folded into the implementation price.
- Level 0 — self-import with our templates (included)
- Level 1 — Apus maps, cleans and imports for you
- Level 2 — multi-year historical data conversion
- Input data quality remains the customer's responsibility
Implementation and license amounts are quoted after the survey, based on module count and process complexity. On-premise and source-code handover cost more than SaaS because the consulting, customisation and handover effort is larger.
What makes an ERP project big — and what doesn’t.
We quote after the survey, so this page carries no figure. What decides that figure is public though: the six drivers below — plus one that the rest of the market bills by and we do not.
| Driver | Small when… | Large when… | Impact on effort & schedule |
|---|---|---|---|
| Modules going live | One or two modules on the standard configuration | More than eight modules running several business flows at once | Large |
| Legal entities & ledgers | One entity, one set of books | Several entities with consolidation and intercompany transactions | Large |
| Divergence from industry practice | You adopt the industry template as it is | Distinctive processes you must keep, which have to be designed | Large |
| Existing systems to connect | Nothing outside Apus | Several running systems must stay, some without an API | Large |
| History to bring across | Opening balances only, loaded from the templates | Years of transactions from the old system, of uneven quality | Moderate |
| Operating locations | One office or one plant | Multiple warehouses, plants or branches, each with its own way of working | Moderate |
| Number of users | A few dozen people | A few thousand people | Negligible |
What does NOT become an extra charge
These are the line items that usually get charged separately elsewhere. Here they don’t — and this is why.
- Adding users. Every tier carries unlimited users — more people does not change the invoice.
- Unlocking features. Every feature exists in every edition and every deployment model; no package is cut down to be sold back.
- The everyday work tools. Apus Office is in every edition, never a separate purchase.
- Initial data entry. Tier 0 of data migration — loading it yourself from the standard templates — is included.
- Year one of an on-premise or source-code delivery. 12 months of warranty; the 20%/year maintenance fee starts in year two.
Beyond this list, everything sits inside one of the three cost lines above — including capacity above your tier, which is billed by tier or by GB.
You pay for capacity — not for headcount.
Text-based business records are tiny; what actually consumes capacity is document attachments and collaboration files. That is why the two quotas are separate — Drive files can never eat into your operational data.
| Tier | Business records & documents | Apus Office Drive | Legal entities | Environments | Backup |
|---|---|---|---|---|---|
| Starter | 100 GB | 500 GB | 1 | Production | 30 days |
| Growth | 500 GB | 2 TB | 3 | Production · Test | 90 days |
| Scale | 2 TB | 5 TB | Unlimited | Production · Test · Staging | 1 year |
| Enterprise | By request | By request | Unlimited | Production · Test · Staging · Dedicated data region | Per policy |
Exceeding a limit means moving up a tier or paying per GB — always flagged in advance, never a surprise invoice. Transaction-data retention and API call limits are set per tier in the contract.
On-premise: a licence scoped by modules and entities, with storage you provide. Source-code handover: a one-off source licence, then a maintenance-and-updates contract once warranty ends.
Support levels stated in response times, not adjectives.
Three levels for SaaS. On-premise and source-code deliveries carry a 12-month warranty, then move to a maintenance contract.
| Level | Channels | Hours | P1 response | Also includes |
|---|---|---|---|---|
| StandardIncluded with every plan | Support portal · email · help centre | Business hours | ≤ 4 business hours | — |
| BusinessAdd-on | Adds hotline · live chat | 12×5 | ≤ 2 hours | Regular system health reports |
| PremierAdd-on | Adds a named assigned engineer | 24×7 for P1 incidents | ≤ 1 hour | Regular process reviews & training, roadmap priority |
Incident severity levels
- P1
- Operations stopped — a core business process cannot run and there is no workaround.
- P2
- A core business process is affected but a temporary workaround exists.
- P3
- Localised defect affecting a limited group of users or a single function.
- P4
- Question, improvement request or guidance on how to use the system.
Warranty & maintenance — On-premise and source-code handover
A 12-month warranty from acceptance. From year two, the maintenance contract is 20% per year of the license value.
- Bug fixes and version updates
- Technical support at the chosen SLA level
- Access to technical documentation & the support portal
- Custom development of new features
- Consulting on newly standardised processes
- Data migration, infrastructure and third-party licenses
Support level, hours and response times apply as agreed in each customer's contract.
Fully featured platform — no hidden fees, no feature locks.
Pricing questions
You pay for value used (storage, infrastructure resources), not per employee. Adding users does not raise cost — ideal for organizations with large headcounts.
SaaS runs on Apus cloud with fast setup, low upfront cost and Apus operations. On-premise installs on your own infrastructure with data residency — ideal for compliance. The on-premise build does not include source code.
Business-layer source code plus deploy-level operations documentation. Apus maintains and updates the platform core. Exact scope is detailed by contract.
No. A project has three lines and all three are stated up front: implementation (one-off), capacity-based usage (recurring) and data migration (separate). Every feature ships in every model — we never gate features behind a package tier.
The implementation fee pays for people: surveying how you work today, advising on standardised processes, configuring the system around them, training and acceptance. Because the effort depends on module count, legal entities and process complexity, Apus quotes after a survey rather than posting a number that is wrong for everyone. Scope and price are agreed before signature and do not change mid-project.
SaaS includes updates and support in the subscription. On-premise and source-code handover carry a 12-month warranty; from year two the maintenance contract is 20% per year of the license value, covering bug fixes, version updates and support at your SLA level.
Yes — you can run a pilot with milestone acceptance before committing. Contact the Apus team to design a pilot for your scale.
Get a quote for your scale.
The Apus team will recommend the right model and quote by scope.