Concepts
Concepts
Overview
This section defines the terminology and mental models you need to work with Oblax. Each concept represents a distinct layer in the platform’s architecture, from project structure and module identity to authentication, access control, and billing. The subsections below explain each concept in detail.
| Concept | Description |
|---|---|
| Projects | The basic unit of organization. Each project owns an /app filesystem, a manifest, and a set of modules. |
| Environments | Isolated configuration scopes (development, staging, production) that share a project’s data model. |
| Clients | Application identities that connect to a project’s API via a clientAppId. |
| Modules | Composable backend building blocks — Forms, Bookmarks, Flux Scripts, Templates, ACL — each with a defined identity strategy. |
| Authentication and Authorization | JWT-based identity verification across platform and application realms. |
| ACL and Permissions | HTTP-key-based route maps that control which tokens can access which endpoints. |
| Realms | Access scopes that partition a project into isolated security domains. |
| Roles | Three-tier role system spanning platform, organization, and project levels. |
| Service Extension | Custom backend logic and code generation via the obxfw CLI. |
| Storage | File and object storage for uploads, assets, and generated content. |
| Flux Events and Scripts | Event-driven JavaScript scripts that execute in response to platform events. |
| Billing and Pricing | Usage-based billing models, pricing tiers, and cost management. |