Modular by construction.
Each module ships with its own libSQL database, its own ingest path, and its own RBAC scope. Turn them on independently. The dashboard is the only thing they share.
Where it sits.
Modules are one layer of a larger composition. Hover the rail to see what each layer is responsible for.
The portal UI is one entry point. llms.txt and a roadmapped MCP server are the others — every doc page and module lives behind a single addressable surface for humans, agents, and CLIs.
Ten production modules — each with its own libSQL database, its own schema, its own ingest path. Turn them on independently. Same auth, same RBAC, no monolith.
BetterAuth handles sessions, OAuth, magic links, and passkeys. SpiceDB handles relationship-based authorization. Every module reads the same identity; every API call hits the same policy plane.
Everything is a signed POST to /api/ingest. The SDK is a convenience, not a requirement. cURL works. Each event is verified at the edge before it lands in the owning module's database.
Each module owns a libSQL file — its own schema, migrations, and audit chain. Shared Postgres backs auth, RBAC, and cross-module workflow state. No single database is the bottleneck.
Bun on the server. Docker Compose on a laptop, a VPC, or our cloud. No Kubernetes required, no proprietary control plane — the whole stack starts with one command.
What's happening right now.
Logs
Log aggregation and analysis from multiple sources (SSH, Docker, Kubernetes, HTTP).
Traces
Distributed tracing viewer for OpenTelemetry spans, service maps, and request waterfalls.
Errors
Fingerprint, deduplicate, and triage exceptions with stack traces and release context.
Performance
Runtime process metrics — CPU, memory, event loop, and GC for instrumented services.
What it costs.
What you ship.
Configs
Configuration management and synchronization with versioning and a diff viewer.
Deploys
Deployment tracking and monitoring with health checks and rollback capabilities.
Repository
Code analysis and repository metadata tracking with feature extraction.
Who did what.
Audit
Comprehensive audit logging for all admin actions with before/after diffs.
Secrets
1Password-backed secrets management — integration in progress.
How teams operate the system.
Feature Flags
Manage rollout rules, targeting, and audit-backed flag changes from the same portal.
Webhooks
Outgoing webhook delivery with signed payloads, retries, and delivery history.
Tenants
Tenant and project administration for multi-tenant Cuitty installs, gated by admin RBAC.
Power tools that don't fit a category.
How modules compose
Modules ingest events through a shared /api/ingest endpoint.
Each event is signed at the client and verified at the edge before it lands in
that module's libSQL database. The dashboard reads from those databases and
renders the per-module UI.
Adding a module to the registry (modules/modules.json)
lights up a new card here automatically. Phase 3 builds the per-module detail
pages.