Platform Maturity & Operation
Target Group: Decision-makers (owners, operators), investors (VC/PE), IT management, strategic partners — who want to assess if CockpitOS is operable and extendable, not just demo-ready.
Software Engineering — like a product, not a side project
| Feature | Implementation |
|---|---|
| Monorepo | apps/ (Dashboard, Center Website, Signage, Manager) + packages/ (database, ui, MCP, wayfinding, ...) — shared types and UI. |
| A Single API Truth | Business logic and database access in the Dashboard; channels consume REST APIs. |
| Type Safety | TypeScript throughout; Prisma schema as the contract basis (packages/database). |
| CI & Checks | Including Next.js Dynamic Route Checks in the Dashboard build — prevents outages due to routing conflicts. |
| Documentation as Deliverable | cockpit-docs/ with changelog, developer contract, editorial onboarding — maintained in parallel with code. |
Data & Migrations — no "YOLO Schema"
CockpitOS works with live center data. Fixed rules apply in the project:
- Additive migrations (new columns with default/nullable).
- Expand-Contract on structural changes — no blind
DROPactions. - Documented SAFE migrations and reference
db_structure.mdin the repository.
This is a maturity signal for operators and investors: data sets are treated like in enterprise software.
Multi-Tenancy & Modules
| Concept | Benefit |
|---|---|
| Organizations & Centers | Multiple tenants in one installation. |
ModuleConfig | Features per organization/role — Mall Cockpit, Social, Signage, Analytics … |
| Role Model | Super Admin, Center Admin, Content Editor, Center Manager, … — documented in Navigation & Modules. |
Scaling in the business model is inherent to the product, not interpreted retroactively.
Integrations — open, but controlled
| Integration | Maturity |
|---|---|
| Public Center Website API | Contractually documented, CORS for modern frontends, templatePublicContent for v0 without secrets. |
| AgencyOS | Partner API including audit, content push, team access — Documentation. |
| MCP (Claude/Cursor) | Same tools as internal editorial — Remote MCP for teams. |
| Outstand (Social) | Publish, webhooks, metric sync, cron — operation documented. |
| WordPress | Plugin path for existing centers — parallel to the CockpitOS website, not a replacement for the core. |
| v0 / Vercel | Frontend channels, deploy register, go-live DNS — Documentation. |
Operation & Availability
| Topic | Note |
|---|---|
| Hosting | Productive, among others, on Render (render.yaml in Repo). |
| Media | Bunny CDN — central media logic in the cockpit. |
| Cron / Webhooks | Documented under docs/CRON-SETUP.md (Repo) and in specialist documentation (Social, Revalidate). |
| Status | Setup of Better Stack — Setup Documentation. |
No secrets in this documentation — operating partners receive credentials separately.
Product Scope — modular, but cohesive
The Feature Matrix shows which app covers which core function:
The Module Registry in the code (apps/dashboard/src/lib/modules.ts) corresponds to the Navigation — documentation and product are aligned (maintenance rule in the team).
Back
Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/plattform/plattform-reife-und-betrieb