Skip to main content

cockpitOS — Platform Overview

cockpitOS is the operating system for shopping centers** — not “another CMS”, but an integrated platform that unifies editorial work, center operations, visitor-facing channels, and partner integrations on one shared data core.

This page explains concept and architecture for anyone encountering the system for the first time: leadership, owners, partners, press — without requiring a technical background, but with enough depth to see why this combination is rare.


The problem: digital fragmentation​

Shopping centers typically run many disconnected worlds:

  • Website (often WordPress or an agency project)
  • Social media (separate tool + manual approval)
  • Displays and kiosks (dedicated signage software)
  • QR apps or visitor web apps
  • Tenant communication, issues, property data
  • Analytics in yet another tool

Each channel has its own logins, its own maintenance, its own truth. Shops, events, and opening hours are entered multiple times — errors, delay, and high effort follow. AI assistants fail on scattered, outdated sources.


Our approach: one core, all channels​

cockpitOS solves this with a clear principle:

Maintain once — use everywhere.

The dashboard is the central control room. All center data lives here: shops, events, news, offers, floor plans, social posts, approvals, issues, and more. Website, digital signage, NOW web app, WordPress plugin, and social publishing read from this core — they are channels, not second databases.

That is the key difference from a toolbox: not integration via export/import, but one platform with many outputs.


Why this depth is rarely combined​

The market mostly offers partial solutions:

Typical marketcockpitOS
CMS or website builderCMS plus operational cockpit
Signage without editorial workflowSignage from the same content pool
Social tool without center master dataSocial with approval, Outstand publish, engage & reporting in the cockpit
Chatbot without live dataAI assistant with shops, events, wayfinding from the core
Property/tenant tools separate from marketingIssues, dispatch, workflow alongside content in one UI
One hard-wired website per centerMulti-tenant: many centers, one platform, modular activation

cockpitOS connects editorial, approval, distribution, visitor experience, analytics, and partner APIs in one product. That end-to-end integration across properties, channels, and roles is what we consider unique — not a single feature, but the overall architecture.


What the platform includes​

Modular per organization and role — but conceptually one system:

AreaWhat it does
Mall CockpitShops, events, news, offers, services, jobs, categories, media
Editorial flowDispatch (email inbox), workflow approvals, content planner
Marketing CockpitControl room: campaign portfolio, content planning (planner), Events in Town — not a second CMS
Social CockpitCreate posts, approval (internal + external link), Outstand publish, engage, reporting
Digital ExperienceCenter website, templates, v0/Vercel hosting, signage, companion, QR, reserve & collect
WayfindingFloor plans, routing — on website, kiosk, and NOW web app
Community & operationsFeedback, issues, broadcast, chatbot analytics
AnalyticsContent performance, footfall (preparation), social KPIs
Center Manager appMobile submission, issues, social — for teams on site
IntegrationsWordPress plugin, AgencyOS (partner API), public API, MCP (Claude/Cursor)

Menu paths and module IDs: Navigation & modules.


Conceptual pillars​

1. Single source of truth​

All channels use the same master data. When opening hours change, they are immediately consistent on website, displays, and in the assistant — without manual sync jobs.

2. Operational cockpit, not just editorial​

The /dashboard home is a control room: open approvals, dispatch, social queue, planner, issues — depending on role and selected center. cockpitOS thinks operations and marketing together, not just “save article”.

3. AI with context — not generic​

The visitor assistant uses real center data (shops, events, hours, wayfinding). Editors work with Claude via MCP or v0 directly against APIs and approval workflows — AI is built into the process, not bolted on.

4. Multi-tenancy & scale​

One installation manages many centers and organizations. Modules are enabled per subscription and role. Websites can run on Render, Vercel/v0, or hybrid — the data core stays the same.

5. Open to partners​

AgencyOS lets agencies and integrators push content via API. The public center website API feeds modern frontends (v0, custom React apps). That is platform thinking: cockpitOS remains the core; frontends can change.


Technical architecture (short)​

LayerContents
InfrastructurePostgreSQL, Redis, Render (Frankfurt); media via Bunny CDN; email (Resend); analytics (Umami); AI (OpenAI, optional Pinecone)
CoreMonorepo (pnpm/Turborepo): dashboard as the only app with direct DB access and all REST APIs
Shared packagesdatabase, ui, ai-context, wayfinding, mcp-cockpit-os, …
Channelscenter-website, digital-signage, center-manager — API clients to the dashboard
ControlModules (ModuleConfig), roles, organizations, center assignments

Security principle: Secrets and DB access live server-side in the dashboard (and controlled in channel backends). Frontends never receive raw DB credentials.

Developer details: Developer guide · Public API · AgencyOS.


Typical data flow​

  1. Editorial creates or submits content (dashboard, Center Manager, dispatch, Claude/v0).
  2. Approval (website drafts, social posts) runs through workflow — including external approval links and notifications.
  3. After approval: automatic distribution to website (revalidate), signage, social (Outstand), optionally WordPress sync.
  4. Visitors use website, QR/NOW web app, or kiosk — always with the same data.
  5. Analytics & social reporting measure impact at platform level.

Who cockpitOS is for​

RoleValue
Center operator / ownerOne platform instead of tool silos; measurable digitalization of the asset
Editorial & marketingLess duplicate work; social, website, and signage from one place
Center managers on siteMobile app for issues, content submission, social insights
Tech & agenciesPublic API, AgencyOS, MCP — extensible without replacing the core

Further reading​

TopicDocument
Press & short copyPress release texts
Modules & appsCore features & modules
Dashboard navigationNavigation & modules
Social end-to-endSocial media approval
v0 / Vercel go-liveGo-live DNS, Vercel & UD
Internal architecture note (code snapshot)docs/COCKPITOS-SYSTEMARCHITEKTUR-VOLLSTAENDIG.md — if in doubt, this page and the code win

Maintained with the product. Technical questions: Saad Badr, Technical Lead · technik@schickma.de

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