Technical Information Request List (TIRL)

Table of Contents

  1. Current Development Status
  2. Technology Architecture
  3. Development Ownership & Contracts
  4. Development Roadmap & Costing
  5. Product Features
  6. Platform–Content Integration
  7. Security & Data Protection
  8. Performance & Scalability
  9. Analytics & Measurement
  10. Maintenance & Team
  11. Known Technology Risks

1. Current Development Status

Stage of product development (concept / wireframes / prototype / MVP / beta)

The SelebZ platform is currently at an MVP stage. Core user flows such as authentication, content browsing, vertical scroll playback, adaptive video streaming, like & share videos, payment gateway are designed and partially implemented.

The architecture is production-ready and designed to scale to beta and public launch.

As SelebZ is a micro-OTT app, there isn't a public demo link available. The demo is provided as an APK file, which needs to be manually downloaded and installed on a mobile device. We will be happy to present and demonstrate the app in person during our meeting, showcasing its features, user interface, and functionality in detail.

Product requirement document (PRD)

To be documented.

Functional specification documents

To be documented.

2. Technology Architecture

High-level system architecture diagram

(Diagram Link)

The platform uses a cloud-native, microservices-based setup for scalable video delivery, secure content protection, and high user access. It divides its architecture into the Client Layer, API Gateway, Core Backend Services, Application Layer, Data Layer, Media Ingestion and Processing, and Content Delivery Network.

This structured approach ensures scalability, fault separation, performance improvement, and easier future growth.

Client Layer

The Client Layer includes mobile applications that run on Android and iOS platforms.

Users watch short-form and segmented video content through a vertical scrolling experience.

The client handles:

All client requests go through the API Gateway to ensure security and control.

DRM License Server

A separate DRM License Server enforces content protection. It issues DRM licenses only after:

The server supports encrypted HLS/DASH playback and prevents unauthorized access, screen recording, and content theft. This meets the security needs of content owners and studios.

API Gateway

The API Gateway is the single entry point for all client and admin requests.

Its responsibilities include:

This layer improves system security, observability, and scalability.

Core Backend Services

The Core Backend Services layer contains independent microservices, each responsible for a specific business task:

These services are loosely connected and can scale independently.

Application Layer (Read / Write APIs)

The Application Layer breaks down business logic into Read APIs and Write APIs.

This separation helps improve performance and read scalability.

Data Layer

The Data Layer uses a polyglot persistence strategy. It selects databases based on access patterns and data characteristics.

This layered storage model ensures low latency and horizontal scalability.

Media Ingestion & Processing

The Media Ingestion and Processing pipeline manages secure onboarding of content:

Encrypted Video Storage

All processed and encrypted video assets are stored in secure object storage.

Content Delivery Network (CDN)

A global Content Delivery Network (CDN) is used to deliver video content efficiently.

This ensures smooth playback and high availability across regions.

The proposed architecture is designed to support secure, scalable, and high-performance video streaming with DRM protection, personalized feeds, and modular backend services. The system is cloud-ready and can scale seamlessly from MVP to large-scale production deployments.

Front-end framework stack

Mobile Application

Admin Dashboard & Analytics

Back-end framework stack

Backend Architecture

Technology Stack

Asynchronous Processing

Database design overview

The SelebZ platform uses a polyglot persistence architecture that incorporates various database technologies based on how data is accessed, scalability needs, and consistency requirements. We use different databases because no single database works best for all tasks.

The database layer is logically divided into:

Database Strategy Principles

The database architecture is designed around the following principles:

Logical Database Segmentation

Data Ownership & Isolation

This ensures: Fault isolation; Independent scaling; Safe schema evolution.

DB Category Purpose
User & Identity Data Authentication, profiles, subscriptions
Content Metadata Movies, parts, feeds, ordering
Engagement Data Watch history, likes, views
Caching Layer Performance optimization
Analytics Store Business intelligence and insights

Hosting / cloud infrastructure plan

Hosting & Cloud Infrastructure Plan (GCP)

The SelebZ platform is hosted on Google Cloud Platform (GCP). It uses a containerized, microservices-based architecture that offers high availability. This architecture is designed for:

Infrastructure Compute Model

High-Level Hosting & Infrastructure

(Diagram_link)

The platform uses a container-first cloud setup with Google Kubernetes Engine for application workloads. It offers fully managed data services for storage and global edge services for content delivery. This design ensures scalability, reliability, and operational efficiency.

Content delivery network (CDN) strategy

SelebZ uses a global Content Delivery Network (CDN) first video delivery strategy to ensure low latency and high-quality playback for short-form vertical video content across different network conditions.

The CDN strategy is designed to:

CDN Provider & Integration

CDN Platform

CDN Role in Architecture

Video Delivery Model

Streaming Protocols

Video Segmentation

Adaptive Bitrate Streaming (ABR)

Supported Renditions

How Adaptation Works

Player continuously monitors: Network bandwidth; Buffer health; Device capability. It automatically switches between renditions without interrupting playback.

This ensures: Smooth playback on unstable networks; Optimal quality on high-speed connections.

DRM & Secure Delivery

Content Protection

License Flow

Security Benefits

Origin Protection Strategy

Origin Setup

CDN Access Control

Cache Strategy

Cacheable Content

Cache Policy

Geographic Delivery Strategy

Initial Focus

Performance Optimization Techniques

SelebZ uses a CDN-first, adaptive streaming approach that employs encrypted multi-bitrate delivery. This strategy ensures steady, secure, and high-quality video playback, even with different network conditions. It also reduces infrastructure load and allows for easy scalability.

3. Development Ownership & Contracts

In-house vs outsourced development model

The Selebz platform is developed using a primarily in-house engineering model, supplemented by AI-assisted development tools to accelerate delivery and improve developer productivity. The company maintains full ownership and control over all intellectual property, source code, and system architecture.

In-House Development

AI-Assisted Development

Development contracts with vendors or agencies

Not required, as no external vendors or agencies are currently engaged for core platform development. All development activities are performed by internal teams governed by employment agreements.

IP ownership clauses in vendor contracts

Not applicable, as development is performed internally. All intellectual property, including source code and related artifacts, is owned by SelebZ as per internal employment and appointment terms.

Source code repository access structure

Source code repositories are owned and controlled by Selebz. Access is role-based and limited to internal developers only. All code changes follow internal review and approval processes.

4. Development Roadmap & Costing

Remaining development milestones

Covered in Financial Projections, as appended.

Timeline for MVP (Minimum Viable Product) launch

Covered in Financial Projections, as appended.

Timeline to full public launch

Covered in Financial Projections, as appended.

Estimated cost to reach MVP

Covered in Financial Projections, as appended.

Estimated cost to reach scale

Covered in Financial Projections, as appended.

5. Product Features

Core user features list

The SelebZ application is designed as a vertical micro-frame OTT experience, optimized for short attention spans and continuous content consumption, similar to Instagram Reels but with structured episodic content.

Authentication & User Access

Content Discovery & Consumption

Video Playback Experience

User Engagement

Creator / content management tools

Content Upload & Processing

Content Structuring

Content Quality Control

Admin and analytics dashboard features

Platform Administration

Content Performance Analytics

User Analytics

Operational Monitoring

The product roadmap is designed to evolve toward advanced personalization, creator-led content publishing, and AI-driven recommendations as the platform scales.

Monetization feature readiness

The platform is built with multiple monetization paths, allowing flexibility as the business evolves.

Subscription-Based Monetization

Advertisement-Based Monetization

Hybrid Monetization Model

Monetization Analytics

6. Platform–Content Integration

SelebZ follows a structured, automated, and secure content integration pipeline that manages the full lifecycle of content — from ingestion and processing to secure delivery and scheduled release.

The platform is designed to handle episodic micro-frame content while maintaining OTT-grade quality, rights enforcement, and scalability.

Content ingestion workflow

Ingestion Sources

Workflow Steps

Key Characteristics

(Diagram_link)

Encoding / transcoding pipeline

To convert uploaded content into multi-bitrate, device-compatible formats optimized for adaptive streaming.

Pipeline Architecture

Output Formats

Streaming Standards

Additional Processing

Rights management and DRM plan

Content Rights Management

DRM Strategy

Security Measures

Metadata tagging system

Metadata Categories

Usage

Content release scheduling tools

Scheduling Capabilities

Release Models Supported

The SelebZ content integration platform combines automated ingestion, adaptive transcoding, DRM-based rights enforcement, rich metadata tagging, and flexible release scheduling to support scalable, secure, and high-quality content delivery.

7. Security & Data Protection

The SelebZ platform is designed with a security-by-design and privacy-by-default approach.

User data, content assets, and payment information are protected through layered security controls, strict access policies, and compliance-ready data governance frameworks aligned with Indian regulatory requirements.

User data collection plan

The platform collects only necessary data required for service delivery and monetization.

Identity & Account Data

Usage & Engagement Data

Subscription & Transaction Data

Data privacy compliance plan (India DPDP Act readiness)

The platform is designed to be compliant with the Digital Personal Data Protection (DPDP) Act (India).

Consent Management

User Rights Enablement

Data Localization

Data Retention Policy

Security protocols

Application Security

Infrastructure Security

Data Security

Content Security

Monitoring & Incident Response

Payment gateway integration plan

Supported Payment Methods

Integration Flow

Security Controls

The SelebZ platform implements robust security and data protection practices aligned with India's DPDP Act, using encryption, access controls, consent-driven data governance, and secure third-party payment processing to ensure user trust and regulatory readiness.

8. Performance & Scalability

Load assumptions for first 12 months

The platform is designed to support ~500,000 to 900,000 active users within the first 12 months.

Stress test plan (if any)

Formal large-scale production stress testing is planned prior to major public releases.

Video hosting and streaming bandwidth cost model

Video hosting and streaming costs are modeled based on actual DAU consumption, CDN bandwidth usage, and average viewing behavior.

Key assumptions:

Projected costs (Year 1):

Costs scale linearly with DAU and are optimized via adaptive bitrate streaming and CDN caching.

9. Analytics & Measurement

User behavior tracking design

The platform implements a comprehensive user behavior tracking system to monitor engagement, retention, and conversion across the user lifecycle.

Tracked user events include:

Architecture approach:

Content performance metrics planned

The platform tracks detailed content-level performance metrics to evaluate audience engagement and optimize content strategy.

Key content metrics include:

Dashboard mockups

To be documented.

10. Maintenance & Team

Technical team structure

The platform is developed and maintained by an in-house cross-functional team with clearly defined ownership across engineering, product, and data.

Current team composition:

CTO or tech lead profile

The technology function is led by Varun Agrawal (CTO), who oversees platform architecture, scalability, security, and long-term technical roadmap.

CTO responsibilities include:

Post-launch maintenance plan

Post-launch maintenance is handled by the in-house technical team with structured monitoring and operational workflows.

Maintenance scope includes:

Operational readiness:

Bug-fix and update cycle plan

The platform follows a structured release and bug-fix cycle to ensure stability while enabling rapid iteration.

Bug-fix approach:

Update cycles:

11. Known Technology Risks

Key technical dependencies

The platform relies on a set of core technical components and infrastructure services that are critical to overall system operation.

Key dependencies include:

All critical components are designed with horizontal scalability, monitoring, and failover strategies to reduce operational risk.

Third-party APIs or services relied upon

The platform integrates with the following third-party services to support non-core but essential functionalities:

Third-party integrations are abstracted behind service layers to allow replacement or migration with minimal impact if required.

Single points of failure identified

Potential single points of failure have been identified and addressed during system design.

Identified areas and mitigations: