Business Study 005

Oohify.

A programmatic DOOH aggregator bridging the gap between small media owners and digital advertisers through unified API protocols.

VerticalAdTech / DOOH
Core StackJava / Spring Boot
DatabasePostgreSQL / Redis

Context 01: The Problem

The DOOH market is fragmented by legacy CMS silos.

— Physical ad space is difficult to book programmatically

— Medium-scale media owners lack digital visibility

— Real-time inventory sync is non-existent for legacy screens

Context 02: The Arbitrage

A unified software layer that manages traffic, not hardware.

● Zero physical overhead model

● Programmatic booking via unified API

● Attribution via mobile location data

Programmatic
Architecture

Syncing real-time inventory from 20+ legacy CMS providers into a single high-performance dashboard.

Market Note

"The value is in the software layer—aggregating fragmented nodes into a unified booking engine."

Unified Protocol

Acting as a translation layer for various legacy hardware communication protocols.

Real-time Sync

Programmatic booking engine managing ad-rotation slots across multiple owners.

Footfall Attribution

Pairing ad play timestamps with anonymized mobile location data for reach validation.

Technical Specs

BUILD_V.05

01

Backend Engine

Java Spring Boot for high-concurrency data processing.

02

Frontend

Next.js for the media owner and advertiser dashboards.

03

Data Store

PostgreSQL for inventory and Redis for high-speed slot caching.

04

API Sync

Custom adapters for syncing with legacy DOOH CMS endpoints.

Java Spring
Next.js
PostgreSQL
Redis
Programmatic API