Codility VS Veysign

Veysign's answer:

Three things.

• Screens are bundled, not metered. The digital signage products we compare against all price per screen. Veysign puts a number of screens inside a flat monthly price, so the cost of adding a second or third display to a cafe is zero until you cross a tier.
• The player is a native Android app, not a browser in kiosk mode. Each screen keeps its assigned playlist on the device, so playback carries on when the connection drops. When it reconnects, an update is applied only after the new content has fully downloaded and been verified, so an interrupted sync never replaces content that is already working.
• Nothing important is paywalled at the bottom. Locations are unmetered on every plan, and email alerting when a screen stops checking in is included on every plan, including the free tier.

Veysign's answer:

• The arithmetic at the small end. The five signage products we track published per-screen rates between $7 and $20 per screen per month when we last checked them on 1 September 2026. Veysign bundles 3 screens into $9/month and 8 into $19/month. That gap is widest exactly where per-screen pricing hurts most, in the two-to-eight-screen venues.
• It behaves on bad connections. Venue internet is not datacentre internet. The playlist lives on the device, and a failed sync leaves the working playlist running instead of blanking the screen.
• It runs on hardware you already own. Android 9 and newer, on Android TV devices, boxes, tablets and commercial displays. There is no proprietary media player to buy per screen.
• You can find out whether a screen died without paying for it. Offline screen alerting is on every plan, free tier included.

Veysign's answer:

Operators who run screens in physical venues and are not AV specialists: restaurants and cafes running menu boards, retail stores, clinics, gyms and hotels.

The practical sweet spot is somewhere between two and fifty screens, often spread across more than one site. Typically these are teams who update signage today by carrying a USB stick to each display, or by leaving a slideshow looping on a smart TV, and who want to stop doing that without hiring an integrator or committing to a per-screen contract.

The multi-location case matters more than the screen count: a small chain that wants one brand-wide campaign running everywhere while letting local staff manage their own site's information.

Veysign's answer:

Veysign is built by ZS Cloud Systems (SMC-Private) Limited, trading as ZsTechLabs.

It was built around two decisions that shaped everything else.

The first is Android-first. The screens these venues already have are Android: TV boxes, tablets, commercial displays. Building a native Android player rather than shipping a browser in kiosk mode meant the software could survive restarts, memory pressure and a dead network without leaving a blank screen in a customer's window.

The second is not billing per screen. Every product in this category meters screens, which is fine at fifty displays and punishing at three. Bundling screens into a flat price is the whole positioning: it makes the second and third screen in a small venue effectively free, and that is where most of the market actually lives.

The web dashboard and the Android player are developed together, so pairing a screen is a 6-digit code rather than a provisioning exercise.

Veysign's answer:

Web platform

• Laravel (PHP) on the server, with Inertia.js bridging to a Vue 3 front end written in TypeScript
• Tailwind CSS, built with Vite, server-side rendered
• Redis for cache and queues, with Laravel Horizon supervising the workers
• Laravel Cashier for Paddle billing, Sanctum for API tokens, Socialite for SSO sign-in
• S3-compatible object storage for media, so the storage provider is a configuration choice rather than a deploy-time constant
• Sentry for error monitoring

Veysign Player (Android)

• Written in Kotlin, targeting Android 9 and newer
• Jetpack Compose for the UI
• Media3 / ExoPlayer for image and video playback
• Room as the on-device database that holds the playlist and schedule, which is what makes offline playback work