Own the system — a long-term strategic investment.
Business-layer source handed over with deploy-level docs. You self-extend in part; Apus keeps maintaining and updating the platform core.
Full source ownership — a core that keeps evolving.
Your team builds extensions on the handed-over source while Apus keeps shipping updates to the platform core.
Own the source
Receive the business-layer source, less vendor dependency.
Self-extend
Your engineering team customizes & extends in part.
Strategic investment
A long-term technology asset for your organization.
How it deploys.
Agree on scope
Define the source-code & documentation handover scope.
Deploy & hand over
Install, hand over business-layer source + documentation.
Train & partner
Train your engineers; Apus maintains the core & supports.
What's included and what's not.
Detailed scope is defined by the specific contract.
Choose source-code handover for full ownership.
A strategic investment for large organizations needing long-term tech autonomy.
Frequently asked questions.
Which source code do I receive?+
The business-layer source with deploy-level docs. The platform core is provided as a binary and maintained by Apus.
Is self-built work supported by Apus?+
Self-built parts are your team's responsibility; Apus supports within the agreed scope and maintains the core.
Is the platform core updated?+
Yes. Apus keeps maintaining & updating the platform core per contract.
Which organizations is it for?+
Large enterprises and public sector needing technology autonomy and treating the system as a long-term strategic asset.
Is this model right for you?
The Apus team advises on the deployment choice for your needs.