Package Map
This page maps the main Lombok packages to their responsibilities.
Core runtime packages
Section titled “Core runtime packages”packages/api
Section titled “packages/api”The main NestJS backend and control plane.
Responsibilities include:
- auth
- users
- folders
- storage
- events
- tasks
- app platform services
- Docker integration
- comments
- search
- notifications
- sockets
- MCP
- ORM integration
packages/ui
Section titled “packages/ui”The main React + Vite frontend.
Responsibilities include:
- authenticated and unauthenticated app shells
- page routing with React Router
- sidebar and app UI rendering
- API- and socket-backed user interactions
packages/core-worker
Section titled “packages/core-worker”The worker runtime.
Responsibilities include:
- core worker execution
- app worker execution
- sandboxed worker-task execution paths
- background processing and analysis flows
Shared platform packages
Section titled “Shared platform packages”packages/types
Section titled “packages/types”Shared contracts and types used across the platform.
This package includes important app-platform schema and contract definitions.
packages/utils
Section titled “packages/utils”Shared utility functions used by multiple packages.
packages/auth-utils
Section titled “packages/auth-utils”Shared auth-related helpers, especially for frontend and SDK usage.
packages/sdk
Section titled “packages/sdk”Typed client SDK surface used by platform consumers.
The SDK is built around the platform API contract and OpenAPI-derived typing.
App-platform packages
Section titled “App-platform packages”packages/app-worker-sdk
Section titled “packages/app-worker-sdk”SDK for app backend and worker code.
packages/app-browser-sdk
Section titled “packages/app-browser-sdk”SDK for embedded app frontends.
packages/demo-apps
Section titled “packages/demo-apps”Reference/demo apps that demonstrate the real app-platform model.
UI system packages
Section titled “UI system packages”packages/ui-toolkit
Section titled “packages/ui-toolkit”Reusable UI component and design-system package built around Radix, Tailwind, and Storybook.
Worker support packages
Section titled “Worker support packages”packages/worker-utils
Section titled “packages/worker-utils”Utilities used in worker and processing contexts, especially media/file processing concerns such as image and video handling.
Why this matters
Section titled “Why this matters”The package map helps answer a simple question:
where does a given kind of behavior live in Lombok?
Examples:
- backend logic →
packages/api - frontend logic →
packages/ui - worker execution →
packages/core-worker - shared contracts →
packages/types - app extension surfaces → app SDK packages
Next steps
Section titled “Next steps”Continue with: