Duplication
Shared mechanisms are not copied between products and do not diverge in behaviour.
Project 02 · Platform Engineering
Novus Core:
a shared platform for independent products.
A framework-agnostic core on native PHP 8.4: stable module contracts, secure product composition, licensing, updates, queues, and unified administrative infrastructure.
- Format
- Commercial core
- Environment
- Web · Backend · CLI
- Challenge
- Shared product platform
- Nexronik role
- Architecture and development
01 / Context
Not another product.
The foundation for an entire family.
When every commercial product reimplements users, licensing, updates, and modules, development becomes an exercise in synchronising copies.
Novus Core moves platform responsibilities into one core. The product becomes the composition point, while domain functionality is added through independent modules and a stable public API, without Core modifications or hidden cross-module dependencies.
Coupling
Modules own their data and integrate only through contracts, events, or APIs.
Updates
Versions, compatibility, and rollback are validated before a new release is activated.
02 / Architecture
Contracts separate the product
from the platform.
Core has no knowledge of product brands or business terminology. It publishes the Extension API, manages the lifecycle, and lets the product safely compose the required module set.
01API 1.7
API
Stable Contracts
The public boundary for modules, products, and infrastructure adapters.
- Additive API evolution
- Capability contracts
- Versioned compatibility
- Contract tests
02Native PHP
CORE
Kernel & Runtime
Container, HTTP, events, routing, authorisation, and extension lifecycle.
- Module registry
- Install / boot / uninstall
- Queue and scheduler
- Audit and safe errors
03Composition
PRODUCT
Products & Modules
The product selects modules, settings, and its shell without modifying Core source code.
- Isolated module data
- Explicit capabilities
- Product shell and navigation
- Independent releases
ProductComposition root
ModulesDomain functions
Extension APIStable contracts
CoreShared services
03 / Capabilities
From first launch
to a secure update.
The core handles recurring platform tasks so product teams can build domain value instead of maintaining their own infrastructure copy.
Web installer
Eight steps: environment, database, Cloud, licence, configuration, administrator, migrations, and repeat-run lockout.
Module manager
Manifest, dependency graph, conflicts, capabilities, migrations, and a controlled lifecycle.
Licensing
Signed responses, local validation, offline grace, and a separate server boundary.
Marketplace
Signed package verification and multi-step installation plans before code is loaded.
Atomic releases
Immutable versions, staging, validation, pointer activation, and rollback to the previous release on failure.
Queues and jobs
A PDO queue with idempotency, priorities, leases, heartbeat, retry, and a dead-letter queue.
Backups
Driver-based backup, verification, and restore for supported database engines.
Admin and UI API
Users, roles, settings, navigation, and secure interface extension points.
04 / Interface
A complex platform —
a clear first launch.
The installer checks the environment and external dependencies step by step, while system states remain readable on desktop and mobile.
The screenshots capture the early Core 1.0.0 interface. The figures below refer to the current source tree and documented controlled runs.
05 / Boundaries
Extensibility
without implicit trust.
A module receives only declared capabilities, and the package is validated before its code reaches the active runtime.
Contracts instead of internal classes
Products and modules depend only on the public Extension API, while Core does not import their namespaces.
Explicit capabilities
Required permissions are declared in the manifest and granted separately by the product.
Verified packages
Signature, SHA-256, manifest structure, and dependency graph are validated before installation.
Fail-closed compatibility
An unsupported API version, owner conflict, or duplicate stable ID stops composition.
06 / Validation
Scale verified
by project artefacts.
Only reproducible figures are shown here: documented E2E, test tree composition, public contracts, and the CI matrix. These are not business metrics or an SLA.
installation steps completed
1264 px desktop
390 × 844 mobile
public test methods in 103 PHPUnit files
PHP files containing public Core Contracts
variants: SQLite, MySQL, MariaDB, and PostgreSQL
The eight-step E2E was recorded on 20 July 2026 using PHP 8.4.16 and SQLite 3.49.2. The figures 421 and 157 describe the static composition of the current tree; they do not replace a complete release run across all database engines.
07 / Stack
Minimal magic.
Explicit boundaries.
- RuntimeNative PHP 8.4 · Composer
- StandardsPSR-3 · PSR-7 · PSR-11 · PSR-15
- DataPDO · MySQL · MariaDB · PostgreSQL
- SecuritySodium · Ed25519 · SHA-256
- InterfacePHP templates · CSS · JavaScript
- QualityPHPUnit 12 · PHPStan 2.1 · CI matrix
Need a platform for a family of products?
We will design a core
that does not limit growth.
We will separate the platform, product, and modules so new functions connect through clear contracts and updates remain manageable.