About FireUX

Industry SaaS framework

FireUX is an industry SaaS framework for industry founders and the teams building their software. Shared SaaS foundations and industry libraries compose connected Apps and Workspaces.

Industry libraries own domain records, capabilities and workflows. Apps and Ecosystems compose them into products. Nuxt and Nuxt UI provide the technical and interface foundation.

Open Project WorkspaceBrowse modules

What this page covers

  • How Projects connect Apps and Ecosystems
  • What the Project Workspace operates
  • How Modules add reusable capability
  • Where public platform records are published

How FireUX is organised

  1. 1. Project
    A Project is the control-plane record that connects its Apps and Ecosystem.
  2. 2. App
    An App is a branded product surface connected to a Project and Ecosystem.
  3. 3. Ecosystem
    An Ecosystem groups Apps around one product or domain and owns their shared configuration.
  4. 4. Module
    A Module is reusable, source-controlled capability explicitly composed into an App.
  5. 5. User
    A User has an identity and App-specific membership.
  6. 6. Workspace
    A Workspace is a working surface with capabilities and Tools for the work an App supports.
  7. 7. Capability
    A Capability is an area of responsibility in a Workspace. Its Tools perform supported actions.
  8. 8. Solution
    A Solution explains a proven FireUX capability in the language someone searches for.
  9. 9. Public directory
    Public Apps and Ecosystems are safe projections of their canonical records.

Modules

What FireUX is built from

FireUX Core supplies shared SaaS and interaction foundations. Industry libraries add domain models, capabilities and workflows.

Entities

The records FireUX connects

Project

Control-plane record for a FireUX Project.

Key fields: id, name, description, image

Links to: App, Ecosystem

App

Canonical App identity connected to a Project and Ecosystem.

Key fields: id, name, project_id, ecosystem_id, role, status

Links to: Project, Ecosystem, User

Ecosystem

Canonical Ecosystem identity grouping related Apps.

Key fields: id, name, project_id, slug, status

Links to: Project, App

User

User identity with App-specific membership.

Key fields: id, display_name, handle, profiles

Links to: App

Ignition request

A request to configure and launch an App.

Key fields: status, business, app_job, access, delivery

Links to: Project

Module package manifest

Source-controlled package metadata used to compose App capability.

Key fields: type, id, name, team

Links to: App

Structure

Relationship map

Project
  <- Ecosystem.project_id
  <- App.project_id

Ecosystem
  <- App.ecosystem_id

User
  -> App membership

Ignition request
  -> Project launch pipeline

Module package manifest
  -> App build and runtime composition

Key routes

Home · /Get Started · /get-startedOperations · /operationsSolutions · /solutionsApps · /appsModules · /modulesEcosystems · /ecosystemsWorkspace Entry · /workspaceProject Workspace · /workspace/projectProject Ignition · /workspace/project/ignitionsProject Ecosystem · /workspace/project/ecosystemProject Apps · /workspace/project/apps