Skip to main content
Login
Apus Platform
Book a demo
DEPLOYMENT & OWNERSHIP

Every business gets its own instance — you choose where it runs.

No system is shared between customers. The models differ in where it runs, who operates it and how much you own — not in features.

Talk to an expert
DEPLOYMENT ARCHITECTURE

One platform — three destinations.

Choose where the system runs; the module set stays identical, and you can switch models as the business enters a new stage.

One platform
Dedicated CloudPopularAnnual subscription (monthly option) · your own instance · Apus operates it.
Data: your own instance, run by Apus
Annual licence · by module + storage tier · updates + Standard support included.
Data: your infrastructure
Source-code handoverSource license · strategic investment.
Data: your infrastructure
Popular

Dedicated Cloud

Annual subscription (monthly option) · your own instance · Apus operates it.

Your own instance, never shared with another company
Servers, updates & backups included in the subscription
By module + storage tier · unlimited users
Source-code escrow option
Best for: your own system, without running it

Self-hosted

Annual licence · by module + storage tier · updates + Standard support included.

Installed on your servers or cloud/VPC
Data stays in your business
Run it yourself — or have Apus manage it
Source code NOT included
Best for: customers needing data control

Source-code handover

Source license · strategic investment.

Business-layer source handed over
Deploy-level operations docs
Apus maintains & updates the platform core
Partial self-extend
Best for: large enterprise / public sector
DETAILED COMPARISON

Differs in deployment & ownership — not in features.

Criteria
Dedicated Cloud
Self-hosted
Source-code
Source code
—
— (binary core)
✓ business layer · binary core
Tech docs
User guides & public API
Basic
Deploy-level (deploy, schema, API)
Data
Own instance, run by Apus
Customer infra
Customer infra
Updates
by Apus
Customer-paced · or Apus (managed)
Core: Apus releases · customer applies at their own pace
Customization
Config
On request
Extend the handed-over business layer yourself
Cost from year 2
Included in the subscription
Annual licence renewal (updates & Standard support included)
12-month warranty, then 20%/year
Best for
Own system, no ops team
Data residency
Large enterprise & public sector

Every model is a dedicated instance — nothing is shared between customers. Dedicated Cloud: an annual subscription (monthly option), by module + storage tier, unlimited users. Self-hosted: an annual licence by module + storage tier, and it does NOT include source code; with Self-hosted, managed by Apus, Apus operates it on your infrastructure for a management fee on top of the licence. The self-hosted annual licence includes updates and Standard support. License and handover scope are detailed by contract. Source-code escrow option for Dedicated Cloud.

IMPLEMENTATION ROADMAP

Four steps to go live.

12–3 weeks

Discover

Business analysis · requirements · solution design.

24–6 weeks

Set up

Core config · data migration · integrations.

32–3 weeks

Train

User training · process testing · UAT support.

41–2 weeks

Go-live

Launch · go-live support · stabilization.

Dedicated project managementQuality & security assuranceSupport at the chosen SLA tierFull training & documentation
CHOOSE A MODEL

What do you prioritize?

IF YOU PRIORITIZE

Your own system, without buying servers or running operations.

PICKDedicated Cloud
IF YOU PRIORITIZE

Data stays in your business, control of infrastructure & security.

PICKSelf-hosted
IF YOU PRIORITIZE

Full ownership, a long-term strategic investment, self-extend.

PICKSource-code
MIGRATION & INTEGRATION

A safe, well-planned transition.

Apus migrates data from legacy systems and connects to your existing systems — with reconciliation and a parallel run before cut-over, and limited downtime.

Migrate from legacy ERP/CRM/Excel, cleansed & reconciled
Integrate existing systems via API & webhooks
Parallel run before cut-over
1
Data assessment
Map data & source systems.
2
Extract & cleanse
Standardize, de-duplicate, reconcile.
3
Load & test
Load into Apus, verify integrity.
4
Parallel run & cutover
Reconcile results, then cut over in the agreed window.
SLA & SUPPORT

Clear service commitments, long-term partnership.

100%
Data on your own instance
24×7
P1 support (Premier tier)
24h
Request response (business hours)
Dedicated PM
Dedicated project manager
FAQ

Deployment questions.

How long until go-live?+

Depending on scope, typically 9–14 weeks across the 4-step roadmap. More complex projects are estimated during discovery.

Will we lose data migrating from a legacy system?+

The migration process includes cleansing, reconciliation and a parallel run to surface discrepancies before cut-over. Source-data quality is reviewed together with you at the assessment step.

Who owns the source code?+

The platform core belongs to Apus. With source-code handover you receive the business-layer source; Dedicated Cloud offers an escrow option.

Can we switch models later (Dedicated Cloud → Self-hosted)?+

Yes. You can move between models; scope & cost are defined by the specific contract.

How much downtime at go-live?+

Minimal. Thanks to parallel run and planned cut-over, operational disruption is kept to a minimum.

Choose the model that fits you.

The Apus team advises on the deployment & ownership model for your needs.

Talk to an expertSee pricing