# Omnitron

> Build, connect, document and operate TypeScript systems.

## Documentation Index
- [ABAC Conditions](https://omnitron.dev/docs/auth/abac-conditions.md): ABAC conditions (time-of-day, IP, fresh-MFA gates) are part of the planned authorisation stack. Today's Omnitron does not evaluate request-attribute predicates; the policy shapes below are the target design.
- [Shared access policy](https://omnitron.dev/docs/auth/access-policy.md): Small, portable roles and permissions shared by issuers, servers and interfaces.
- [Audit Trail](https://omnitron.dev/docs/auth/audit-trail.md): The structured audit_logs + actor-from-JWT discipline described here is part of the planned auth stack. Today's Omnitron emits operator activity into the daemon log only; the typed audit table and the helpers below are reference designs.
- [Authentication & Authorisation](https://omnitron.dev/docs/auth.md): The shared access policy , Titan JWT/session adapters and Netron authorization gates are implemented. Pages explicitly marked Design RFC describe additional application architecture. The current Omnitron daemon ships JWT issuance, session lifecycle, and the admin , operator and viewer roles (see OmnitronAuth in services-reference ). These pages describe the broader application authorisation design. See operator authentication for the implemented daemon role checks.
- [Mental Model](https://omnitron.dev/docs/auth/mental-model.md): This page describes the target authorisation model. Omnitron today ships only the base auth surface; the role/permission/condition/RLS layering shown below is a design reference.
- [Per-User Overrides](https://omnitron.dev/docs/auth/overrides.md): Per-user permission overrides on top of role defaults are part of the planned authorisation stack. Today's Omnitron stores (user, role) only; the override table and merge rules below are the target design.
- [Permissions](https://omnitron.dev/docs/auth/permissions.md): Permission matching is implemented in the shared access core . Netron's @Auth({ permissions }) uses explicit matching. Application policies can choose hierarchical matching, the default of access/permissions . The examples on this page describe transport gates and application catalogs; the supervisor's operator roles remain a separate policy.
- [RLS Bridge](https://omnitron.dev/docs/auth/rls-bridge.md): The RLS-bridge stack documented here (wrapper, permVer enforcement, generic policy projection) is a planned architecture, not what Omnitron ships today. Treat the code excerpts as reference shapes you'd implement in your own auth-utils package.
- [Token issuance & transports](https://omnitron.dev/docs/auth/token-issuance.md): Where the tokens go after a successful sign-in is a transport decision, not a service one. The same signin handler works whether tokens travel in the response body for the client to store, or in HttpOnly cookies the client never sees.
- [Changelog](https://omnitron.dev/docs/community/changelog.md): Versioning policy + how to find release notes per package.
- [Contributing](https://omnitron.dev/docs/community/contributing.md): Set up the source or documentation repository and verify a focused change.
- [Security policy](https://omnitron.dev/docs/community/security.md): How to report vulnerabilities + supported versions + disclosure SLA.
- [vs alternatives](https://omnitron.dev/docs/comparison.md): How this stack differs from NestJS, tRPC, Fastify, Hono, and the typical TS app stack.
- [Bare-metal / systemd](https://omnitron.dev/docs/deployment/bare-metal.md): Run Omnitron as a systemd service on your own server.
- [Docker Compose](https://omnitron.dev/docs/deployment/docker.md): Deploy an Omnitron-supervised stack as a single docker-compose file.
- [Overview](https://omnitron.dev/docs/deployment.md): How to deploy Omnitron-supervised apps — Docker, k8s, PaaS, bare-metal.
- [Kubernetes](https://omnitron.dev/docs/deployment/kubernetes.md): Production-grade Kubernetes deployment patterns.
- [PaaS (Fly.io / Railway / Render)](https://omnitron.dev/docs/deployment/paas.md): Opinionated PaaS deploys for fast time-to-prod.
- [Production readiness](https://omnitron.dev/docs/deployment/production-readiness.md): A practical acceptance checklist for deployment, observability, access control, and recovery.
- [Architecture](https://omnitron.dev/docs/foundations/architecture.md): How an Omnitron-based system composes at runtime.
- [Composition and build boundaries](https://omnitron.dev/docs/foundations/composition.md): Select small primitives first, then add transports, user interfaces and infrastructure deliberately.
- [Monorepo Layout](https://omnitron.dev/docs/foundations/monorepo.md): The Omnitron source tree at https://github.com/omnitron-dev/omni .
- [Principles](https://omnitron.dev/docs/foundations/principles.md): Shared contracts, explicit composition, visible lifecycle, and operational accountability.
- [Titan vs Omnitron](https://omnitron.dev/docs/foundations/titan-vs-omnitron.md): Titan runs standalone. Omnitron is an opt-in higher-level platform built on top.
- [Auth client](https://omnitron.dev/docs/frontend/netron/auth.md): AuthenticationClient — token storage, auto-refresh, cross-tab sync, inactivity timeout.
- [netron-browser](https://omnitron.dev/docs/frontend/netron/browser.md): Browser-optimized Netron RPC client — HTTP / WebSocket / multi-backend.
- [Caching](https://omnitron.dev/docs/frontend/netron/caching.md): LRU cache, stale-while-revalidate, tag invalidation.
- [Error handling](https://omnitron.dev/docs/frontend/netron/errors.md): Typed errors across the wire, retry classification, recovery patterns.
- [Overview](https://omnitron.dev/docs/frontend/netron.md): Browser-side Netron RPC — netron-browser + netron-react.
- [Middleware](https://omnitron.dev/docs/frontend/netron/middleware.md): Three-stage middleware pipeline, built-ins, custom middleware.
- [Multi-backend](https://omnitron.dev/docs/frontend/netron/multi-backend.md): One frontend, many Netron servers — routing, hooks, components.
- [netron-react](https://omnitron.dev/docs/frontend/netron/react.md): Production-grade React bindings for Netron RPC — type-safe hooks, multi-backend, auth.
- [SSR](https://omnitron.dev/docs/frontend/netron/ssr.md): Server-side rendering — dehydrate / hydrate, hydration safety.
- [Testing](https://omnitron.dev/docs/frontend/netron/testing.md): TestNetronProvider, integration patterns, deterministic fixtures.
- [Transports](https://omnitron.dev/docs/frontend/netron/transports.md): Choose a Netron transport, bound the lifetime of a call, and observe connection recovery.
- [Frontend overview](https://omnitron.dev/docs/frontend/overview.md): Three packages that cover everything browser-side in a Titan app.
- [Accessibility](https://omnitron.dev/docs/frontend/prism/accessibility.md): Vision simulation, keyboard interaction and accessible composition with Prism.
- [Blocks](https://omnitron.dev/docs/frontend/prism/blocks.md): Full-page composites — drop one in, fill the slots, ship a screen.
- [Component CLI](https://omnitron.dev/docs/frontend/prism/cli.md): Initialise, inspect, copy and maintain Prism components with the shipped CLI.
- [Components catalog](https://omnitron.dev/docs/frontend/prism/components.md): Per-component reference for the widgets in Prism.
- [Forms](https://omnitron.dev/docs/frontend/prism/forms.md): Schema-aware forms with react-hook-form + zod + Prism Field.
- [Hooks catalog](https://omnitron.dev/docs/frontend/prism/hooks-catalog.md): The 48 React hooks exported from @omnitron-dev/prism/hooks.
- [HTTP client](https://omnitron.dev/docs/frontend/prism/http.md): Typed REST requests, cancellation, interceptors and explicit retries.
- [Overview](https://omnitron.dev/docs/frontend/prism.md): Design system for production React frontends — MUI v9 + Prism.
- [Layouts](https://omnitron.dev/docs/frontend/prism/layouts.md): DashboardLayout + the three auth layouts + the core layout primitives.
- [Maps](https://omnitron.dev/docs/frontend/prism/maps.md): Self-hosted MapLibre maps, markers, a point picker and a coverage layer.
- [Research workspaces](https://omnitron.dev/docs/frontend/prism/research.md): Scientific documents, block editing and typed knowledge graphs with a shared MUI theme.
- [State and persistence](https://omnitron.dev/docs/frontend/prism/state.md): Local UI stores, persisted preferences, migrations and the boundary with server state.
- [Theme](https://omnitron.dev/docs/frontend/prism/theme.md): Palette, typography, shadows, dark mode, presets.
- [Developer map](https://omnitron.dev/docs/getting-started/developer-map.md): Direct routes from a development task to the guide, API reference and verification step.
- [Installation](https://omnitron.dev/docs/getting-started/installation.md): Install only what you need. Server-side Netron ships inside Titan; the browser client is a separate package.
- [Project Structure](https://omnitron.dev/docs/getting-started/project-structure.md): A reference layout for a Titan-based project. The Omnitron monorepo itself follows this shape; consumer projects do not need to be a monorepo to use the same conventions.
- [Quickstart](https://omnitron.dev/docs/getting-started/quickstart.md): Compile a Titan service, bind an HTTP transport, and call it from a typed client.
- [Introduction](https://omnitron.dev/docs/intro.md): Choose the Omnitron layers you need, understand their boundaries, and build your first service.
- [Authoring with Lumen](https://omnitron.dev/docs/lumen/authoring.md): Keep the document useful as static HTML. Add an island where interaction helps the reader inspect a result.
- [Lumen](https://omnitron.dev/docs/lumen/overview.md): Lumen compiles a document corpus into static HTML, local search, Markdown mirrors and an agent index. The same parsed document graph supplies page rendering and link checks. This manual is a reference consumer of that build path.
- [How this manual is built](https://omnitron.dev/docs/lumen/this-site.md): This repository consumes Lumen's ordinary CLI. Its layout uses Lumen navigation components and the shared Prism identity used by Omnitron Console.
- [Console access](https://omnitron.dev/docs/omnitron/access.md): Human roles, effective RPC permissions, account administration and revocation shared by Console and CLI.
- [Agents and delegated operations](https://omnitron.dev/docs/omnitron/agents.md): Architecture and acceptance criteria for provider adapters, delegated RBAC, monitoring evidence and controlled automation.
- [Architecture](https://omnitron.dev/docs/omnitron/architecture.md): Components, planes, and data flows inside the Omnitron supervisor.
- [Auth & RBAC](https://omnitron.dev/docs/omnitron/auth-rbac.md): Authentication, sessions, JWT, RBAC roles, RLS context propagation.
- [Xec automation](https://omnitron.dev/docs/omnitron/automation.md): Author, review, execute and inspect bounded Xec pipelines through Console and CLI.
- [Backend replacement](https://omnitron.dev/docs/omnitron/backend-handoff.md): Replace a control plane while a resident owner retains application processes.
- [Production best practices](https://omnitron.dev/docs/omnitron/best-practices.md): Patterns proven in real multi-app Omnitron deployments.
- [CLI reference](https://omnitron.dev/docs/omnitron/cli.md): Every command, every flag, every command group.
- [Cluster + Fleet](https://omnitron.dev/docs/omnitron/cluster.md): Multi-node Omnitron — leader election, state replication, fleet operations.
- [Configuration](https://omnitron.dev/docs/omnitron/configuration.md): Every field of omnitron.config.ts, defineEcosystem(), defineSystem().
- [Web console](https://omnitron.dev/docs/omnitron/console.md): The Omnitron webapp — React + Vite + Prism, every page, every plane.
- [Daemon](https://omnitron.dev/docs/omnitron/daemon.md): The long-running supervisor — its lifecycle, state, and RPC surface.
- [Operational diagnostics](https://omnitron.dev/docs/omnitron/diagnostics.md): A diagnostic must say what failed, what was observed, and what can restore service. Omnitron uses the same finding contract in commands, runtime health and notification adapters. Capture does not mean recovery, and broker acceptance does not mean a person received a message.
- [File workspace](https://omnitron.dev/docs/omnitron/files.md): Navigate, edit and transfer files across Omnitron nodes through the same audited Console and CLI contract.
- [Infrastructure](https://omnitron.dev/docs/omnitron/infrastructure.md): Declarative provisioning of Postgres / Redis / S3 / custom containers.
- [MCP + Knowledge base](https://omnitron.dev/docs/omnitron/mcp.md): AI agent integration via Model Context Protocol — kb + management tools.
- [Database migrations](https://omnitron.dev/docs/omnitron/migrations.md): Use @omnitron-dev/omnitron/migration for migration definitions, execution and inspection. omnitron migrate uses that same API. Applications do not need a separate Kysera dependency or a second migration CLI.
- [Observability](https://omnitron.dev/docs/omnitron/observability.md): How logs, metrics, traces, and health flow through Omnitron.
- [Orchestrator](https://omnitron.dev/docs/omnitron/orchestrator.md): The per-app launch pipeline — bootstrap, fork, watch, hand-off.
- [Overview](https://omnitron.dev/docs/omnitron/overview.md): What Omnitron is, what it solves, and how the pieces fit together.
- [Projects and stacks](https://omnitron.dev/docs/omnitron/projects.md): One monorepo owns its applications and libraries; named stacks express deployment environments without duplicating projects.
- [Recipes](https://omnitron.dev/docs/omnitron/recipes.md): Step-by-step solutions for common multi-process patterns.
- [Release readiness](https://omnitron.dev/docs/omnitron/release-readiness.md): Ordered implementation and acceptance plan for the control plane, execution, security, Console and package integrations.
- [Releases and verification](https://omnitron.dev/docs/omnitron/releases.md): Build from pinned project and runtime commits, verify artifacts, attest on a stack, and retain a recovery path.
- [Resilient control plane](https://omnitron.dev/docs/omnitron/resilient-control-plane.md): Target architecture for environments, verified promotion, placement, recovery, scaling and delegated infrastructure operations.
- [Services reference](https://omnitron.dev/docs/omnitron/services-reference.md): Every RPC service exposed by the daemon — names, methods, roles.
- [SSH workspace](https://omnitron.dev/docs/omnitron/terminal.md): Multiple SSH tabs through Xec, with pinned host keys, live authorization and bounded sessions shared with CLI.
- [Topology workspace](https://omnitron.dev/docs/omnitron/topology.md): Inspect physical placements and configured connections, review target changes, and keep target intent separate from runtime execution.
- [API index](https://omnitron.dev/docs/reference/api-index.md): Search public exports by symbol, package or import path, then open the relevant guide or implementation.
- [Compatibility and status](https://omnitron.dev/docs/reference/compatibility.md): Runtime requirements, package boundaries, versioning, and the distinction between implemented APIs and design proposals.
- [Glossary](https://omnitron.dev/docs/reference/glossary.md): Every term used across the stack, with cross-references.
- [Package Index](https://omnitron.dev/docs/reference/packages.md): Every package shipped from the monorepo, grouped by role.
- [Protocol and HTTP primitives](https://omnitron.dev/docs/reference/protocol.md): Shared wire contracts and HTTP machinery used by the server and browser clients.
- [Cross-runtime testing](https://omnitron.dev/docs/testing/cross-runtime.md): One test source running unchanged on Node, Bun, and Deno.
- [Overview](https://omnitron.dev/docs/testing.md): How to test apps built on this stack — unit, integration, cross-runtime, E2E.
- [Integration patterns](https://omnitron.dev/docs/testing/integration.md): Real Application, fake boundaries — the recipes that scale.
- [React testing](https://omnitron.dev/docs/testing/react.md): Testing React components that call Netron — TestNetronProvider patterns.
- [@omnitron-dev/testing](https://omnitron.dev/docs/testing/testing-package.md): Cross-runtime testing utilities — async helpers, runtime adapters, mock types.
- [Bootstrap](https://omnitron.dev/docs/titan/application/bootstrap.md): How Application.create + start actually run.
- [Application Events](https://omnitron.dev/docs/titan/application/events.md): The framework event bus — what fires, what to subscribe to, and what to ignore.
- [Health](https://omnitron.dev/docs/titan/application/health.md): Liveness, readiness, indicator-based aggregation.
- [Application](https://omnitron.dev/docs/titan/application.md): The Titan application kernel — what it owns, what it exposes, how to use it.
- [Lifecycle](https://omnitron.dev/docs/titan/application/lifecycle.md): OnInit, OnStart, OnStop, OnDestroy — when each fires, in what order, what to put in each.
- [Graceful Shutdown](https://omnitron.dev/docs/titan/application/shutdown.md): Phased shutdown with hard-exit guarantees.
- [Error Handling](https://omnitron.dev/docs/titan/best-practices/error-handling.md): Throwing the right error, in the right place, for the right caller.
- [Observability](https://omnitron.dev/docs/titan/best-practices/observability.md): Logs, metrics, traces — the three pillars and how to use each.
- [Performance](https://omnitron.dev/docs/titan/best-practices/performance.md): Where Titan apps win or lose latency and throughput.
- [Structuring Services](https://omnitron.dev/docs/titan/best-practices/structuring-services.md): How to size, organise, and compose services as the codebase grows.
- [Architecture](https://omnitron.dev/docs/titan/concepts/architecture.md): Subsystems, boundaries, and what owns what at runtime.
- [Design Principles](https://omnitron.dev/docs/titan/concepts/design-principles.md): The seven engineering decisions that shape every API in Titan.
- [Mental Model](https://omnitron.dev/docs/titan/concepts/mental-model.md): How to think about a running Titan app.
- [Configuration Hot Reload](https://omnitron.dev/docs/titan/configuration/hot-reload.md): Change config without restarting — when, how, and the gotchas.
- [Configuration](https://omnitron.dev/docs/titan/configuration/overview.md): Layered, validated, hot-reloadable configuration for Titan apps.
- [Configuration Sources](https://omnitron.dev/docs/titan/configuration/sources.md): Files, env vars, argv, objects, remote — every way to get config in.
- [Configuration Validation](https://omnitron.dev/docs/titan/configuration/validation.md): Schema-checked config — crash at boot, not at 3 AM.
- [Decorators](https://omnitron.dev/docs/titan/decorators.md): Every decorator Titan ships — what it does, when to use it, what to import.
- [Lifecycle Decorators](https://omnitron.dev/docs/titan/decorators/lifecycle.md): PostConstruct, PreDestroy — and when to prefer interfaces.
- [Method Traits](https://omnitron.dev/docs/titan/decorators/method-traits.md): Composing decorators on a single method — order, semantics, common stacks.
- [Circular Dependencies](https://omnitron.dev/docs/titan/di/circular-dependencies.md): Detect, diagnose, and break cycles in the DI graph.
- [Contextual Injection](https://omnitron.dev/docs/titan/di/contextual-injection.md): Resolve different providers based on runtime context — current user, environment, feature flags, tenant.
- [DevTools](https://omnitron.dev/docs/titan/di/devtools.md): Inspect the container at runtime — dependency graph, performance, state snapshots.
- [DI Middleware](https://omnitron.dev/docs/titan/di/middleware.md): Wrap container resolution itself — retry, caching, rate-limit, circuit-breaker, logging, validation, transactions.
- [Multi-injection](https://omnitron.dev/docs/titan/di/multi-injection.md): One token, many providers — the canonical pattern for plugins, validators, middleware chains.
- [Dependency Injection](https://omnitron.dev/docs/titan/di/overview.md): Nexus — the IoC container that owns every Titan-managed object.
- [Providers](https://omnitron.dev/docs/titan/di/providers.md): The provider types Nexus understands and the helpers that build them.
- [Scopes](https://omnitron.dev/docs/titan/di/scopes.md): Transient, Singleton, Scoped, Request — how Nexus decides when to reuse an instance.
- [Tokens](https://omnitron.dev/docs/titan/di/tokens.md): Class, symbol, multi-, lazy, async, optional, config, stream — the token family.
- [Error Classification](https://omnitron.dev/docs/titan/errors/classification.md): Categorise errors for telemetry, retry, and alerting decisions.
- [Error Factories](https://omnitron.dev/docs/titan/errors/factories.md): The Errors / NetronErrors / HttpErrors / AuthErrors namespaces.
- [Error Hierarchy](https://omnitron.dev/docs/titan/errors/hierarchy.md): The classes the framework exports — and the codes that classify what they are.
- [Errors](https://omnitron.dev/docs/titan/errors/overview.md): A typed error system built on TitanError, HTTP status codes, and ErrorCode-driven factories.
- [Identifiers](https://omnitron.dev/docs/titan/identifiers.md): Which ID generator to reach for, and why the default is time-ordered.
- [Child Loggers](https://omnitron.dev/docs/titan/logging/child-loggers.md): Bind context to a logger instance — service, request, trace.
- [Logging](https://omnitron.dev/docs/titan/logging/overview.md): Structured pino-based logging with child loggers, transports, and processors.
- [Log Processors](https://omnitron.dev/docs/titan/logging/processors.md): The ILogProcessor pipeline (transform / drop, child-inherited) and how it relates to Pino's native redact.
- [Log Transports](https://omnitron.dev/docs/titan/logging/transports.md): Where log records go — async stdout, extra destination streams, and the async ITransport sink.
- [Auth v1 → v2 Migration](https://omnitron.dev/docs/titan/migrations/auth-1-to-2.md): This migration plan accompanies the planned authorisation stack documented under Authentication & Authorisation . The unified permission engine, the pv claim, and the RLS bridge are target shapes — not changes the current Omnitron build has actually rolled out. Treat the steps below as the upgrade contract you'd hand to a platform team adopting that stack.
- [From Express](https://omnitron.dev/docs/titan/migrations/from-express.md): Migrating a plain-Node Express service to Titan.
- [From NestJS](https://omnitron.dev/docs/titan/migrations/from-nestjs.md): Concept-by-concept mapping from NestJS to Titan.
- [From prom-client](https://omnitron.dev/docs/titan/migrations/from-prom-client.md): Replacing prom-client with titan-metrics.
- [Migration guides](https://omnitron.dev/docs/titan/migrations.md): Move an existing service onto Titan — one concern at a time.
- [titan-auth](https://omnitron.dev/docs/titan/modules/auth.md): official · @omnitron-dev/titan-auth · stable
- [titan-cache](https://omnitron.dev/docs/titan/modules/cache.md): official · @omnitron-dev/titan-cache · stable
- [Community Modules](https://omnitron.dev/docs/titan/modules/community.md): community · @your-scope/titan-yourmodule
- [ConfigModule](https://omnitron.dev/docs/titan/modules/config.md): built-in · @omnitron-dev/titan · /module/config · stable
- [titan-database](https://omnitron.dev/docs/titan/modules/database.md): official · @omnitron-dev/titan-database · stable
- [Decorators catalog](https://omnitron.dev/docs/titan/modules/decorators-catalog.md): Every decorator exported by every module — what it does, where it comes from.
- [titan-discovery](https://omnitron.dev/docs/titan/modules/discovery.md): official · @omnitron-dev/titan-discovery · stable
- [Errors catalog](https://omnitron.dev/docs/titan/modules/errors-catalog.md): What every module throws, error codes, and handling patterns.
- [titan-events](https://omnitron.dev/docs/titan/modules/events.md): official · @omnitron-dev/titan-events · stable
- [titan-health](https://omnitron.dev/docs/titan/modules/health.md): official · @omnitron-dev/titan-health · stable
- [Modules](https://omnitron.dev/docs/titan/modules.md): The Titan ecosystem has three module tiers, each rendered with a origin badge so you can tell at a glance where a module comes from and what its guarantees are.
- [Lifecycle reference](https://omnitron.dev/docs/titan/modules/lifecycle-reference.md): What every module does in onInit / onStart / onStop / onDestroy.
- [titan-lock](https://omnitron.dev/docs/titan/modules/lock.md): official · @omnitron-dev/titan-lock · stable
- [LoggerModule](https://omnitron.dev/docs/titan/modules/logger.md): built-in · @omnitron-dev/titan · /module/logger · stable
- [titan-mailer](https://omnitron.dev/docs/titan/modules/mailer.md): official · @omnitron-dev/titan-mailer · stable
- [titan-metrics](https://omnitron.dev/docs/titan/modules/metrics.md): official · @omnitron-dev/titan-metrics · stable
- [Module map](https://omnitron.dev/docs/titan/modules/module-map.md): How the 16 modules relate, depend on one another, and combine.
- [titan-notifications](https://omnitron.dev/docs/titan/modules/notifications.md): official · @omnitron-dev/titan-notifications · stable
- [Observability matrix](https://omnitron.dev/docs/titan/modules/observability-matrix.md): What every module logs, raises as events, and writes as metrics.
- [Options patterns](https://omnitron.dev/docs/titan/modules/options-patterns.md): forRoot / forRootAsync / forFeature / forWorker across every module.
- [titan-pm](https://omnitron.dev/docs/titan/modules/pm.md): official · @omnitron-dev/titan-pm · stable
- [titan-ratelimit](https://omnitron.dev/docs/titan/modules/ratelimit.md): official · @omnitron-dev/titan-ratelimit · stable
- [titan-redis](https://omnitron.dev/docs/titan/modules/redis.md): official · @omnitron-dev/titan-redis · stable
- [RLS context guards](https://omnitron.dev/docs/titan/modules/rls.md): The shipped context guard decorators, their bypass semantics and the boundary with database policies.
- [titan-scheduler](https://omnitron.dev/docs/titan/modules/scheduler.md): official · @omnitron-dev/titan-scheduler · stable
- [Security checklist](https://omnitron.dev/docs/titan/modules/security-checklist.md): Per-module hardening guidance for production deployments.
- [Shared-session authentication](https://omnitron.dev/docs/titan/modules/shared-session.md): Live session authority, revocation and consistent grants across backends.
- [titan-storage](https://omnitron.dev/docs/titan/modules/storage.md): Local and S3 object storage behind one streaming adapter contract.
- [titan-telemetry-relay](https://omnitron.dev/docs/titan/modules/telemetry-relay.md): official · @omnitron-dev/titan-telemetry-relay · stable
- [Tokens & RPC reference](https://omnitron.dev/docs/titan/modules/tokens-reference.md): All injection tokens and exposed RPC services across every module.
- [Authoring a module](https://omnitron.dev/docs/titan/modules-system/authoring-modules.md): How to build, package, and publish a Titan module to share with the community.
- [Defining Modules](https://omnitron.dev/docs/titan/modules-system/defining-modules.md): The unit of composition in Titan — what a module is, how it composes, and how to design well.
- [Dynamic Modules](https://omnitron.dev/docs/titan/modules-system/dynamic-modules.md): Modules that take configuration — forRoot, forFeature, async factories.
- [Module Discovery](https://omnitron.dev/docs/titan/modules-system/module-discovery.md): How modules are found, loaded, and ordered.
- [Authentication](https://omnitron.dev/docs/titan/netron/authentication.md): AuthenticationManager, AuthorizationManager, BuiltInPolicies, AuthConfig.
- [RPC Middleware](https://omnitron.dev/docs/titan/netron/middleware.md): Per-call wrapping for cross-cutting concerns.
- [Multi-Backend](https://omnitron.dev/docs/titan/netron/multi-backend.md): One client, many servers — pools, failover, method-level routing.
- [Serialization](https://omnitron.dev/docs/titan/netron/serialization.md): msgpack as the wire format — types, custom codecs, when to override.
- [Services](https://omnitron.dev/docs/titan/netron/services.md): @Service, @Public, service descriptors, and peers.
- [Streaming](https://omnitron.dev/docs/titan/netron/streaming.md): AsyncIterable methods, server-push, backpressure.
- [Transports](https://omnitron.dev/docs/titan/netron/transports.md): HTTP, WebSocket, TCP, Unix — how to choose and how to configure.
- [Netron RPC](https://omnitron.dev/docs/titan/netron.md): A transport-agnostic RPC plane — same service surface across HTTP, WebSocket, TCP, Unix.
- [Titan Framework](https://omnitron.dev/docs/titan/overview.md): A composable TypeScript backend framework — DI, lifecycle, validation, and a transport-agnostic RPC plane.
- [API service stack](https://omnitron.dev/docs/titan/recipes/api-service.md): Public HTTP/WS API — auth, database, cache, rate limiting, health, metrics.
- [Recipes](https://omnitron.dev/docs/titan/recipes.md): End-to-end multi-module compositions for common backends.
- [Multi-tenant SaaS](https://omnitron.dev/docs/titan/recipes/multi-tenant-saas.md): Tenant-isolated database (RLS), contextual injection per tenant, tenant-scoped rate limits.
- [Notifications pipeline](https://omnitron.dev/docs/titan/recipes/notifications-pipeline.md): Producer → queue → worker → channels, with rate limit and preferences.
- [OAuth callback](https://omnitron.dev/docs/titan/recipes/oauth-callback.md): PKCE-protected authorisation-code flow with state validation and signed-URL session bootstrap.
- [Observability stack](https://omnitron.dev/docs/titan/recipes/observability-stack.md): Logs, metrics, traces, health — collected and shipped via the telemetry relay.
- [Webhook receiver](https://omnitron.dev/docs/titan/recipes/webhook-receiver.md): Validate signatures, enforce idempotency, route to handlers, isolate flaky downstream work.
- [Worker fleet](https://omnitron.dev/docs/titan/recipes/worker-fleet.md): Background-job processing across pods — process manager, distributed lock, scheduler, metrics.
- [Circuit Breaker](https://omnitron.dev/docs/titan/resilience/circuit-breaker.md): Stop calling a failing dependency. Let it cool down. Resume gradually.
- [Resilience](https://omnitron.dev/docs/titan/resilience/overview.md): Defending against partial failure — retry, circuit breaker, timeout, backoff.
- [Retry](https://omnitron.dev/docs/titan/resilience/retry.md): The retry() function, the @Retry decorator, and the backoff helpers.
- [Timeout](https://omnitron.dev/docs/titan/resilience/timeout.md): Bounded calls — every external dependency needs a deadline.
- [DI Overrides](https://omnitron.dev/docs/titan/testing/di-overrides.md): Replacing providers for tests — fakes, stubs, in-memory implementations.
- [Integration Tests](https://omnitron.dev/docs/titan/testing/integration.md): Boot a real Application with fake infrastructure.
- [Testing modules](https://omnitron.dev/docs/titan/testing/modules.md): How to mock each ecosystem module in unit and integration tests.
- [Testing](https://omnitron.dev/docs/titan/testing/overview.md): Unit, integration, end-to-end — patterns that scale.
- [Tracing](https://omnitron.dev/docs/titan/tracing.md): W3C-compatible trace context propagation, zero dependencies.
- [Contracts](https://omnitron.dev/docs/titan/validation/contracts.md): Method contracts — bind input + output schemas as a single declaration.
- [Validation Error Handling](https://omnitron.dev/docs/titan/validation/error-handling.md): What clients see when validation fails — and how to shape it.
- [Validation](https://omnitron.dev/docs/titan/validation/overview.md): Schema-driven input validation at the service boundary.
- [FAQ + Troubleshooting](https://omnitron.dev/docs/troubleshooting.md): Common questions and stumbling blocks across the stack.
- [1. Scaffold](https://omnitron.dev/docs/tutorial/scaffold.md): Empty folder → working monorepo → "hello world" Titan app.
- [2. Service with a database](https://omnitron.dev/docs/tutorial/service.md): Replace the hello service with a real one backed by Postgres.
- [3. Auth](https://omnitron.dev/docs/tutorial/auth.md): JWT sign-in, sessions, role-gated methods.
- [4. Frontend](https://omnitron.dev/docs/tutorial/frontend.md): Vite + React + Prism + netron-react with end-to-end types.
- [5. Tests](https://omnitron.dev/docs/tutorial/tests.md): Unit / module / integration / E2E coverage for the stack you built.
- [6. Deploy](https://omnitron.dev/docs/tutorial/deploy.md): Package everything into Docker; ship to a server.
- [Overview](https://omnitron.dev/docs/tutorial.md): A 6-step tutorial — from empty folder to deployed app.
- [common](https://omnitron.dev/docs/utilities/common.md): Type predicates, promise helpers, object tools, data structures.
- [cuid](https://omnitron.dev/docs/utilities/cuid.md): Collision-resistant URL-safe unique IDs for distributed systems.
- [eventemitter](https://omnitron.dev/docs/utilities/eventemitter.md): Async event emitter with parallel/serial/reduce patterns.
- [Overview](https://omnitron.dev/docs/utilities.md): Five utility packages the rest of the stack is built on.
- [kb](https://omnitron.dev/docs/utilities/kb.md): Knowledge-base framework — code intelligence + semantic search.
- [msgpack](https://omnitron.dev/docs/utilities/msgpack.md): Extensible MessagePack with native JS types + custom extensions + streaming.
- [Page not found](https://omnitron.dev/404.md): The requested route is unavailable. Open the documentation , search , or return home .
- [Archive](https://omnitron.dev/blog/archive.md): All published engineering notes, ordered by publication date.
- [Omnitron team](https://omnitron.dev/blog/authors/omnitron-team.md): Maintainers of the Omnitron stack. GitHub profile .
- [Authors](https://omnitron.dev/blog/authors.md): Omnitron documentation is maintained by the project contributors.
- [Introduction](https://omnitron.dev/blog/tags/intro.md): Start with an overview of the stack and its documentation.
- [Releases](https://omnitron.dev/blog/tags/release.md): Announcements describe their publication-time scope. Use compatibility and the current changelog before installing.
- [Topics](https://omnitron.dev/blog/tags.md): Browse the project introduction and release announcements.
- [Welcome to Omnitron](https://omnitron.dev/blog/welcome.md): Published 15 May 2026 · Omnitron team
- [Engineering notes](https://omnitron.dev/blog.md): Release announcements and implementation notes from the Omnitron project.
- [Community](https://omnitron.dev/docs/category/community.md): Work from reproducible source, report security issues responsibly and follow changes across releases.
- [Foundations](https://omnitron.dev/docs/category/foundations.md): Understand the boundaries between runtime, transport, interface and operations before composing them.
- [Getting Started](https://omnitron.dev/docs/category/getting-started.md): Choose a path from installation to your first running service. The developer map connects each task to its implementation guide.
- [Best Practices](https://omnitron.dev/docs/titan/best-practices.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Concepts](https://omnitron.dev/docs/titan/concepts.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Configuration](https://omnitron.dev/docs/titan/configuration.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Dependency Injection](https://omnitron.dev/docs/titan/di.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Errors](https://omnitron.dev/docs/titan/errors.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Logging](https://omnitron.dev/docs/titan/logging.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Module System](https://omnitron.dev/docs/titan/modules-system.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Resilience](https://omnitron.dev/docs/titan/resilience.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Testing](https://omnitron.dev/docs/titan/testing.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Validation](https://omnitron.dev/docs/titan/validation.md): Follow these guides in order, or open the reference for the part of your application you are changing.
- [Own the whole system](https://omnitron.dev/.md): Own the whole system
- [Search the documentation](https://omnitron.dev/search.md): Search runs locally against this build. To look up an exported symbol, open the API index .