Runtime
Runtime Resolution
Technology
A runtime-first architecture, designed to scale without fragmenting.
Northken products consume platform capabilities through API and managed content. Pages, navigation, schemas, themes, and forms resolve at runtime — not at build time.
API
Explicit technical contracts
Builder
Surface composition
Atlas
Service mapping
Technical foundations.
Central identity
Sessions, access, scopes and surface affinities are operated by Northken. Products inherit a consistent identity base without rebuilding it.
Runtime content
Pages, navigation, schemas, themes, and forms are resolved at runtime. Managed content remains versioned, approved and traceable until publication.
Builder
Composition of pages, diagrams, navigation, themes and forms in runtime. Product teams edit what changes, without touching what doesn't change.
Atlas
Mapping of services, their relationships and their trajectories. An operational view to align products and platforms.
Shared Services
Billing, communications, audit, common data. Transversal capacities are operated once and consumed by the products.
Targeted deployments
Each change uses the minimum build level appropriate to its impact. The content is deployed without application rebuild.
How does it fit together?
A product connects to the platform through explicit technical contracts: identity for sessions, runtime for surface resolution, shared services for transversal capabilities. Atlas maintains the map of these connections. The Builder maintains the composition of the surfaces. Deployments remain targeted: what changes changes, what does not change does not move.
Evaluate an integration.
To frame shared capabilities, product boundaries and migration path.
Contact us