Skip to main content

For Decision Makers — Owners, Operators & Partners

This page is not the editorial guide. It is aimed at the management level and strategic partners:

Term (Industry)What it means
Asset Owner / Property OwnerOwner of the property, portfolio managers
Center OperatorManagement & administration of the center (main client)
Asset ManagerInstitutional managers of the space
Investors (VC/PE)Only if the platform company cockpitOS is being financed — not the shop tenant
Strategic PartnersAgencies, technology partners, integrators

It answers the question:

Is this a hodgepodge of tools — or a platform worth using for the operation and digitization of the center?

Short answer: cockpitOS is built as a multi-tenant operating system for shopping centers: a data core, many channels, modular architecture, public APIs, and a transparent technical foundation. Not "WordPress plus a few plugins."


In 60 Seconds​

WhatPlatform for center operation: content, approvals, website, signage, social, apps, analytics — one maintenance, many outputs.
For whomOperators, owners, marketing organizations, agencies (via APIs).
TechnologyMonorepo, PostgreSQL, dashboard as API and data core; channels as clients.
DifferenceEnd-to-end integration (Editorial → Approval → Website/Signage/Social) instead of silo solutions.

Deep dive: Platform Overview · Module Map: Core Features & Modules.


Why this does not seem like a “hodgepodge” software​

1. Intentional Architecture — One Core, Many Channels​

  • Only the dashboard speaks directly with the database (Prisma, central business logic).
  • Website, signage, and manager app are API clients — no parallel “shadow CMS”.
  • Social publishing, workflow, dispatch, and planner are integrated in the same product, not retrofitted via Zapier.

2. Product Maturity Visible in Daily Operations​

SignalMeaning for Decision Makers
Modular SystemTenants unlock mall cockpit, social, signage, analytics … per contract — scaling in the product model, not just in code.
Roles & OrganizationsMulti-center, multi-mall, rights per role — enterprise-capable structure.
Approval WorkflowsWebsite drafts and social posts with audit trail, notifications, external approval link.
Public API + AgencyOS + MCPPartners and modern frontends (v0) without replacing the core — platform thinking.
Template SystemMany center websites (ILG, MEC, Goldbeck, …) on a common architecture, not 20 individual projects.
This DocumentationHundreds of pages, role-based navigation, changelog — investment in traceability, not just code.

Details: Platform Maturity & Operations.

3. Market Position — Depth Instead of Single Features​

The market is dominated by partial solutions (CMS, signage, social tool, property software). cockpitOS addresses the gap in between: the same shops and events on website, display, app, and in the AI assistant — including an operational cockpit (dispatch, issues, planner).

Comparison table: Platform Overview → Section “Why this depth is rarely combined”.


What can scale financially​

LeverDescription
More Centers per InstallationMulti-tenancy already in the data model and navigation.
Modules / UpsellSocial cockpit, analytics, digital experience, property … as building blocks.
Agency EcosystemAgencyOS API, public API, documented contracts — revenue through integration instead of just licenses.
Modernization of Existing Solutionsv0/Vercel frontends on stable data core — modernizing the center without data migration per channel.
AI as ProcessMCP, v0 instructions, assistant with live data — differentiation, not chatbot decoration.
What we do not promise

No revenue, customer, or market share figures in the public documentation — those belong in the pitch and contract. This page substantiates product and architectural maturity.


Technology — Serious, Not Experimental​

AreaStatus
StackTypeScript, Next.js (App Router), PostgreSQL, Prisma, Turborepo Monorepo
OperationProductive on Render (including Frankfurt), media CDN, documented cron/webhooks
DatabaseAdditive migrations, documented security rules — no “changing the schema on the fly”
SecuritySecrets server-side; public APIs with clearly defined fields (templatePublicContent without keys)
ObservabilityStatus setup (Better Stack), analytics (Umami) — see Operations

Technical depth for due diligence: Developer Guide · Public API · Architectural note in the repo (link below).


Delivery Speed — Verifiable​

SourceWhat you see
Change LogMajor deliveries with date, what/why, links
GitHubMonorepo, commits, CI
Live Productsdashboard.cockpit-os.de · signage.cockpit-os.de · docs.cockpit-os.de

This is not a PowerPoint product: Dashboard, signage, documentation, and APIs are publicly accessible and described in the documentation.


Who This Page Is For​

RoleRecommended Path
Investor (VC/PE)This page → Maturity & Operations → Due Diligence (Short)
Asset Owner / Center Operator (Exec)Platform Overview
Press / CommunicationsPress Release — Texts
Technical PartnerDue Diligence (Short) → Developer Guide

Editorial onboarding: Navbar Editorial → Start here.


Next Step & Contact​

Nutzungsstatistik: Seitenaufrufe werden anonymisiert erfasst. Im Umami-Dashboard nach diesem Pfad filtern: /en/plattform/investoren-und-partner