App directory entry
Safe directory projection of canonical owning App identity.
Key fields: id, app_name, ecosystem_id, slug, status
Links to: User, Ecosystem directory entry
About FireUX
Platform Operating System for Ecosystem Apps
FireUX is the operating system for builders and operators. We run app discovery, module composition, and ecosystem operations from one structured platform.
We run ecosystem apps from one platform surface, so teams can ship faster, keep architecture aligned, and scale modules without fragmenting the system.
What this page covers
- How platform modules fit together across apps
- The key platform records and their relationships
- Small realistic sample objects for context
- Direct links to public and console surfaces
FireUX - Key Concepts (Priority Order)
- 1. Ecosystem
FireUX is the platform ecosystem that hosts domain apps and shared contracts. - 2. Apps
Apps are product surfaces built from shared modules and runtime contracts. - 3. Modules
Modules package domain capability so apps can compose features without rewrites. - 4. Users
One user identity can move across multiple apps inside the ecosystem. - 5. Runtime Modes
Live, test, and demo modes keep operations predictable across environments. - 6. Console Pattern
Console entry follows one consistent runtime-driven pattern across apps. - 7. Directory + Package Metadata
Public entity projections and tracked package manifests have separate authority. - 8. Public Surfaces
Public routes describe what is available today without exposing private operations. - 9. Service Surfaces
Service apps like Stitch run on the same platform contracts and identity model. - 10. Extensibility
New ecosystems can launch quickly without rebuilding platform fundamentals.
Modules
How we organize the app
Each module owns a clear platform responsibility and together they run one operating core.
Entities
The records we work with every day
User
Public root identity with app and profile relationship indexes.
Key fields: id, display_name, handle, app_ids, profiles
Links to: App, StitchProvider, StitchRequest
Ecosystem directory entry
Safe public projection of an owning Ecosystem record.
Key fields: id, name, slug, status, app_count
Links to: App directory entry
Module package manifest
Source-controlled package metadata; not an entity or public directory row.
Key fields: type, id, name, team
Links to:
StitchProvider
Service provider profile record for capabilities and availability.
Key fields: id, display_name, type, availability, tags
Links to: User, StitchRequest
StitchRequest
Service request record posted for matching and delivery planning.
Key fields: id, title, status, budget_type, tags
Links to: User, StitchProvider
Structure
Relationship map
Project (FireUX control plane) <- Ecosystem.project_id <- App.project_id Ecosystem <- App.ecosystem_id Module package manifest -> package/runtime wiring only User -> App (membership/admin) -> StitchRequest StitchRequest <-> StitchProvider