123CMS on your own servers, offline

Problem

Some customers cannot send content, player data or logins to a cloud: closed networks, security rules, data that must stay in the country. A cloud console is a refusal before the project starts, and a hand-built server is hard to upgrade and hard to hand over.

What we built

The same 123CMS application ships as one release bundle with every image, a checksum for each file and the default player template. The installer checks the signed licence file offline before starting anything, brings the stack up, creates the first administrator and accepts the customer's own certificate. Upgrade keeps the previous release so it can be rolled back; nightly encrypted backups, a restore drill and database password rotation come in the bundle. For installs behind office or mobile networks we hold an outbound-only support tunnel to a relay, so no inbound port is opened on the customer's side.

Result

Installable and upgradable from the bundle alone. Our own test install runs behind a support tunnel; no customer install yet.

Links

No public link. This one runs inside a customer perimeter.

Tags

Related work

• 123CMS One branded console for content, scheduling and fleet-wide emergency override.
• On-Premises Signage Deployment — Multi-Brand Retail Showcase On-premises 123CMS for a two-floor retail showcase, on the client's own server.
• Team Secure Network Access Two VPN exits, per-person keys, monitored.
• 123WF — Indoor Wayfinding Interactive indoor maps on signage screens: a 123CMS module, also sold standalone.