APPNETOS Core
One Core. Unlimited Business Software.
The APPNETOS Core provides the shared runtime and fundamental services for APPNETOS applications. Applications build on the same core while defining their own configuration, functionality and execution contexts. The CMS and other business applications are separate applications, not part of the Core itself.
Architecture & Runtime
Start here to understand how APPNETOS initializes and runs applications.
Architecture
Explore the shared core, application boundaries and modular runtime.
Explore architectureContexts
Understand app, admin, rest,
admin-rest,
worker and cmd. The api and
admin-api
contexts are planned.
Bootstrap
Learn how the runtime initializes its environment, services and error handling.
Explore bootstrapClass Extensions
Discover how APPNETOS resolves configured class overrides.
Explore class extensionsCore Components
The Core includes services for request processing, rendering, persistence, security and background execution. Detailed component guides will be published progressively as their implementations are reviewed.
HTTP & Rendering
Routing, URI resolution, requests, responses, Twig rendering and error handling.
Documentation in preparationData & Caching
MongoDB, documents, collections, annotations, Redis and document caching.
Documentation in preparationSecurity & Users
Authentication, permissions, user management and security services.
Documentation in preparationBackground & Utility Services
Workers, scheduling, mail, commands, logging and debugging.
Documentation in preparationBusiness Core
The Business Core provides reusable business-domain documents and collections, including addresses, organizations, people, companies, suppliers, warehouses and other business entities. Individual domain guides will be added as the existing implementations are documented.
Business Domain Reference
Explore the shared data models and their integration with APPNETOS documents and collections.
Documentation in preparationLiving Documentation
APPNETOS is under active development. These pages describe the current implementation and grow as components are added or refined. Planned functionality is identified separately from implemented features.