01 · CREATE
Layouts, playlists, media.
A browser-based editor combines text, images, video, clocks, feeds, data widgets, and reusable playlists.
We didn't just build a SaaS. We run one.
DigiSign is the complete loop from idea to screen: create layouts and playlists, schedule them across a fleet, pair a Windows or Android player in seconds, and keep playback moving when the network drops. Its Gemini-backed AI Content Studio turns a one-line brief into finished, editable designs. We engineered it, ship it, and operate it in production.
01 — THE BRIEF
Instead of pitching SaaS, we built one.
For years we gave clients the same advice: productize, automate, run in the cloud. DigiSign is us taking that advice ourselves — a product built to prove the argument, not to decorate a pitch deck.
The brief we set was plain: a team should get useful content onto one screen or an entire fleet in minutes. That meant a real layout editor, playlists, scheduling, screen groups, fast six-digit pairing, reliable playback, and then an AI studio that can do the first design pass from one line.
Running it changed how we quote client work. We now price what software costs to run, not just what it costs to build — because we pay DigiSign's bills ourselves.
- Product
- Platforms
- AI
- Templates
- Status
02 — THE PRODUCT
A one-line brief becomes a finished screen.
Type a brief — "weekend offer, 20% off desserts" — and the AI Content Studio returns a deep grid of editable designs. Gemini supplies the language and taste signals; a deterministic remix engine retrieves, refits, recolors, and quality-checks 336 templates in the browser. Beside it, live data apps keep screens current without a daily content chore.
336
templates in the remix engine
2
native player platforms — Windows and Android
24/7
offline-aware playback and live fleet control
03 — HOW IT'S ENGINEERED
The same stack we sell.
The current product runs on ASP.NET Core and .NET 10, a React 19 control plane, MySQL 8, SignalR, Docker, and native Windows and Android players. The architecture is intentionally practical: durable data, real-time commands, local media caches, and graceful offline playback.
02 · CONTROL
Schedules and screen groups.
Publish by time, screen, or group; send live commands and see command progress from the dashboard.
03 · PLAY
Windows and Android.
Players pair with a six-digit code, cache media locally, reconnect automatically, and continue offline.
04 · OPERATE
Fleet health and licensing.
Telemetry, previews, playback logs, remote commands, signed device identity, and per-screen offline leases.
| Layer | In DigiSign |
|---|---|
| Control plane | ASP.NET Core · .NET 10 · MySQL 8 · SignalR |
| Web console | React 19 · TypeScript · Vite |
| Players | Windows WPF · .NET for Android · shared playback core |
| Runtime | Docker Compose · CI/CD · local media caches · offline recovery |
| AI | Gemini · deterministic template remix · Pexels-first image retrieval |
| Live data | Weather · AQI · flights · travel time · feeds · calendars · stocks · social |
04 — WHAT RUNNING IT TEACHES US
Operating software is the real education.
Running DigiSign is a daily audit of our own advice: networks fail, devices drift, screens stay on after the office closes, and every release has to preserve playback.
OPS
Offline is a product state.
Players cache media locally, verify signed leases, reconnect with backoff, and resume without asking someone to reboot the screen.
REALTIME
A command needs a receipt.
SignalR carries live commands, while progress, telemetry, previews, and playback logs tell the operator what actually happened.
SECURITY
A screen is a device identity.
Pairing, hardware-bound keys, signed licence tokens, encrypted secrets, and account-scoped updates are part of the playback path.
05 — SEE IT LIVE
Judge the product, not the case study.
Plans, features, and the AI studio itself are on the product site — the canonical home for everything DigiSign.
06 — FOR YOUR PROJECT
What this proves for your project.
DigiSign is the receipt behind three of our practices: AI work that ships, product engineering that survives real users, and transformation advice we've applied to ourselves first.
Pillar 01
AI & automation that reaches production
The Gemini pipelines behind the Content Studio, pointed at the workflows that eat your team's hours.
Pillar 02
Product engineering, from idea to operated SaaS
MVPs, platforms, and rebuilds engineered by a team that carries its own product end to end.
Pillar 06
Digital transformation, one measurable step at a time
The same productize-and-automate path we took ourselves, mapped onto your spreadsheets and legacy systems.
Tell us what's slow.
We'll tell you what we'd build — and what it costs to run.