Platform, Not Framework
Core is a platform with extension points, not an application framework. The distinction matters for how you build and maintain client applications.| Framework (e.g. Filament) | Platform (Core) | |
|---|---|---|
| Ownership | Each project builds its own app | Core owns structure, rendering, and UX centrally |
| Update path | Per-project migration | Central updates, isolated extensions |
| Mental model | Laravel app | Shopify theme |
The Domain Layer
Core’s central idea is the domain layer: a semantic layer that sits between your underlying systems and the interfaces your users interact with. Rather than exposing complex ERP views and CRM workflows directly, Core unifies data and logic from multiple systems into a coherent set of objects (customers, orders, products, cases) and actions (create, approve, invoice, escalate). This structure models virtually any business process and serves as the foundation for both automation and user interfaces. The domain layer is the single source of truth that renders across all surfaces:- Web application — layouts, pages, data tables, forms
- API — typed endpoints for external consumers
- AI — tool discovery, autonomous agents, enrichment
What Core Enables
Simplification
Complex systems hidden behind a unified, business-adapted interface tailored to how the team actually works.
Process Optimization
Standardized workflows that reduce manual effort and human error across the organization.
Self-Service
End-customers interact directly with the domain layer via Core Portal, without access to underlying systems.
Automation
Well-defined processes enable both rule-based and AI-driven automation without additional engineering.
How We Work with Core
Core is deployed in a forward-deployed engineer model. Our delivery team builds the domain layer and optimized workflows for each client — not custom code beyond the platform’s extension points. The investment compounds: every client application contributes patterns back to the platform, and every platform improvement benefits all clients.Key Concepts
| Concept | What it is |
|---|---|
| Object | A domain entity (customer, order, product). Defines metadata, routing, and capabilities. |
| Action | A typed operation against one or more objects. Declares parameters, authorization, and side effects. |
| Property | A typed, schema-defined attribute on an object. Drives UI rendering, validation, and API exposure. |
| Capability | An opt-in trait that activates platform features on an object (search, activity log, media, soft delete). |
| Object Interface | A semantic contract that maps object properties to platform-level functions (e.g. CustomerObject, DocumentObject). |
| Workflow | A background job or multi-step process that operates on objects. |
| Connector | An integration bridge to an external system (ERP, CRM, email provider). |
| Layout | An application shell (navigation, sidebars, chrome). |
| Page | A page template that composes UI from the data layer (TablePage, ObjectPage, FormPage). |
Architecture
How the three layers relate and the design principles behind them.
Getting Started
Set up your development environment and create your first project.