new resources

new resources

Hariri Foundation

Summary

Hariri Foundation |Jun. 2, 2026

This Request for Proposals titled “Alarabyplus 2.0,” issued by Fadaat Media Group (date not specified), outlines the design, development, deployment, and operation of a comprehensive Over‑the‑Top (OTT) platform across Mobile, TV, and Web, addressing the core challenge of delivering a robust, scalable, secure, and multilingual streaming service with advanced monetization and analytics. The document’s purpose is to inform qualified vendors of detailed technical, business, and operational requirements and to invite complete technical and financial proposals; its main call to action is for vendors to submit bids that meet the stated specifications, SLAs, support commitments, and evaluation criteria.

Key Insights

The document requests proposals to build and operate Alarabyplus 2.0 as a multi‑device OTT platform spanning Mobile, TV, and Web with seamless content delivery and user experience.
The project objective is to enable streaming, downloading, and interactive consumption of multimedia content on a robust and scalable platform across different devices.
The Scope of Work covers application design and development, UI implementation, secure authentication and payments, analytics integration, CDN setup and optimization, comprehensive QA, cloud deployment, and ongoing maintenance and support.
The Mobile application must support iOS, Android, and HarmonyOS with live streaming, video‑on‑demand, offline downloads, and push notifications, while maintaining compatibility with the latest and two previous OS versions and enforcing encrypted communications and secure credential storage.
The TV application must support Apple TV, Android TV, Roku, and Amazon Fire TV with live streaming, VOD, user profiles, and parental controls, and ensure compatibility with major TV platforms through frequent updates.
The Web application must provide adaptive streaming, user profiles, search, a recommendation engine, cross‑browser support for Chrome, Firefox, Safari, and Edge, and SEO for Arabic and English.
The CMS must include content ingestion workflows, scheduling, detailed metadata management, user management with role assignments, secure access controls, audit logs, and regular security updates.
Video encoding and streaming must support HLS and DASH, multiple resolutions and bitrates, and DRM solutions including Widevine, PlayReady, and FairPlay.
The database must be highly scalable with regular backups and disaster recovery plans in place.
APIs must enable integrations with third‑party services such as payment gateways, ad servers, and recommendation engines, accompanied by comprehensive documentation.
CDN delivery must integrate with Akamai, AWS CloudFront, and Azure CDN, employ geographic redundancy for low latency and high availability, and undergo performance testing and optimization.
Security must include end‑to‑end encryption, OAuth, two‑factor authentication, single sign‑on (SSO), and compliance with GDPR and CCPA.
A proper SLA and a dedicated vendor‑side Project Manager are required.
Personalization must provide “For You” recommendations based on user interests and watch history, with personal lists and reminders.
Notifications must be implemented across all platforms, and SEO must cover Arabic and English for live channels and VOD.
In‑app purchases must enable exclusive content access and early access to selected VOD titles.
Integration with other OTT platforms must allow Alaraby Plus content to appear in their recommendations and search results.
In‑app ad banners must support both in‑house and commercial advertising.
Statistics insights must report user activities including platform usage, content watched, watch time, locations, and interests.
The platform must support in‑app FAST channels for special content or events, with FAST reporting for Al Araby Plus activities on third‑party platforms and FAST Ads reporting for third‑party ads.
Video advertising must include VAST tagging for AVOD and Live DAI for live TV and FAST channels.
Advanced analytics must provide audience and content insights, top titles, detailed viewing data export, and linked devices information.
Search must be advanced and recommendation‑driven, and MMP integration must support campaign performance management.
Payment gateway integration must enable a subscription module with auto‑renewal, and videos must support chapter markers.
A conversion funnel must be implemented to convert free users to paying users for exclusive content, with deep linking for registration, purchase, and content viewing.
iOS Custom Product Pages must enable campaign‑specific pages with different descriptions and videos, and app indexing with universal links must surface the app in search engines.
Offline viewing must be supported, and CDN delivery must specify providers, POPs, and countries of availability.
Social media login and integration must be enabled alongside in‑app messaging for targeted engagement based on segmentation.
A picture editor must manage thumbnails and artwork for proper display, and special videos such as trailers, promos, and behind‑the‑scenes must be linked to episodes and titles.
Multiple user profiles must be supported under a single account, with QR code login from mobile to TV, Skip Intro, Continue Watching, and full Arabic language support.
End‑user data management and ownership must be ensured for registered users.
Subscriptions must support SVOD, TVOD, and AVOD, with the ability to broadcast to all connected devices in one operation and deliver excellent viewing across devices.
Artificial Intelligence must enhance content cross‑linking, and localization must include a multilingual frontend and CMS interface with video quality at HD 720p and above.
Video types in the VOD CMS must include Episodes and Trailers, while Collections must organize SVOD, AVOD, and TVOD items for CMS moderation and user browsing, and Shows must comprise multiple episodes around a theme or format.
Images must include background images for interface customization, banners usually sized 1280x720, widescreen thumbnails typically 1280x720 for episodes, and posters displayed prominently with show logos and actors.
Taxonomy must provide detailed discovery using genres, tags, actors, directors, hosts, production‑company, guests, producers, and writers to support search, discovery, analytics, and insights.
The rating system must be fully admin‑managed and include G, PG, PG13, NC‑17, 18+, UR, and NR to guide appropriate viewing decisions.
CMS admin privileges must include full content and category CRUD, user account management with role assignments, configuration of navigation and themes, security enforcement including authentication and password policies, backups and restoration, performance monitoring, scheduled maintenance, test environment, drag‑and‑drop content management, content hiding or removal, organization into categories, collections, and playlists, pricing adjustments for rentals, purchases, and subscriptions, promotional campaign management, and management of languages, subtitles, and regional restrictions.
CMS quality features must include seamless content ingestion manually or via MRSS, accurate scheduling of content and notifications in the admin’s time zone (Qatar), adaptive bitrate streaming for smooth playback across networks and devices, and multiple language support.
Ad formats must include pre‑roll, mid‑roll, post‑roll, banner, and overlay, with integrations to ad servers such as Google Ad Manager, FreeWheel, and SpotX and compliance with VAST and VPAID.
Targeted advertising must provide advanced segmentation by demographics, behavior, viewing history, and preferences; personalized ads; server‑side and client‑side DAI; frequency capping; and geotargeting.
Ad tracking and reporting must include real‑time analytics for impressions, clicks, completion rates, and viewability; attribution of post‑ad actions; third‑party ad verification; and privacy compliance with GDPR and CCPA.
Real‑time analytics must include dashboards for KPIs such as active users, concurrent streams, video plays, and engagement, with customizable views and alerts for critical metrics and performance issues.
User engagement reporting must include retention and churn rates, total and average watch time, interactions such as likes, shares, comments, ratings, and video player heatmaps.
Content performance reporting must identify top content by views, engagement, and watch time, analyze discovery paths such as search and recommendations, and provide viewer demographics by content.
Technical performance reporting must monitor buffering rates, playback failures, bitrates, start times, and device and platform performance.
Ad performance reporting must include impressions, clicks, completion rates, and revenue metrics such as CPM.
Advanced analytics must include predictive analytics, A/B testing, cohort analysis, and data export for external tools.
Analytics and tracking must comply with GDPR and CCPA and implement user consent mechanisms for data tracking.
Additional analytics capabilities must include header bidding and audience signals, PAL AND IMA SDK, audience detailed data, player detailing, funnel visualization, audience segmentation, LTV, churn analysis, and external data and API integrations.
Performance benchmarks must target 99.9% or higher uptime, page loads under two seconds for most users, video playback start within three seconds, seamless peak load handling for live events and major releases, continuous monitoring, minimal latency especially for live, dynamic scaling, and regular load, stress, and endurance testing.
SLAs must guarantee 99.9% uptime or higher, define response time benchmarks, set resolution times of one hour for critical issues, four hours for major issues, and 24 hours for minor issues, provide escalation procedures, deliver regular performance and compliance reports, offer 24/7 support, schedule low‑impact maintenance windows, and include service credits for breaches.
Cloud infrastructure must be provisioned on AWS, Azure, Google Cloud, or Huawei with geographic redundancy, auto‑scaling, disaster recovery, Infrastructure as Code, and environmental sustainability considerations.
Solution architecture must be detailed, scalable, and interoperable, using high‑availability design with failover, microservices where appropriate, containerization such as Docker, and an API gateway.
The CDN solution must allow dedicated CDN selection, be optimized for video with edge servers and intelligent traffic management, provide DDoS protection, and consider a multi‑CDN strategy.
The storage service must allow dedicated storage selection with strong security and compliance, data replication across regions, intelligent traffic management, long‑term archiving, strict access control, and cost management with tiered storage.
A managed hosting service option must include 24/7 support, continuous monitoring, compliance such as GDPR and SOC 2, and clear SLAs for response and resolution times.
Security compliance must align with ISO 27001, SOC 2, and GDPR, include regular audits and vulnerability assessments, maintain an incident response plan, encrypt data at rest and in transit, and enforce strong access controls and identity management.
Backups and restore must implement a robust backup policy, ensure quick and reliable restores with a clear disaster recovery plan, conduct regular testing, maintain version control, define RTO and RPO, and use immutable backups against ransomware.
Integration and compatibility must ensure seamless integration with existing systems and third‑party services, device compatibility across smart TVs, mobile devices, and web browsers, API versioning with backward compatibility, and rigorous integration testing.
User experience must focus on superior UX with regular updates, personalization features, accessibility per WCAG, and multi‑language support.
Sustainability and future‑proofing must prioritize sustainable, adaptable design, regular updates and scalability planning, environmental considerations in data centers and cloud, and continuous innovation.
Legal and compliance must ensure adherence to laws and regulations including copyright and intellectual property, data protection under GDPR and CCPA, clear terms of service and user agreements, and regular legal audits.
Project management must include a clear timeline with milestones and deliverables, regular progress reports, a risk management plan, stakeholder communication, and consideration of agile methodologies.
Training and documentation must include comprehensive staff training, detailed user guides, technical manuals, API documentation, ongoing support, training updates, and a knowledge base.
Proposal requirements must include company background and OTT experience with case studies, a detailed project plan with timelines and milestones, technology stack and tools, QA and testing approach, a financial breakdown with payment schedule and terms, a post‑launch support plan, and SLA details.
Evaluation will consider technical expertise and experience, proposal quality and completeness, proposed technology and approach, cost‑effectiveness, and post‑launch support and maintenance plans.
Distribution must support global reach in compliance with regional regulations and licensing, provide comprehensive analytics across channels, support monetization via subscription, pay‑per‑view, advertising, and in‑app purchases, and ensure scalable and reliable infrastructure for growth and peak traffic.
The Contents on page 2 lists 18 sections from Introduction to Distribution, indicating the report’s comprehensive coverage of technical, business, operational, and compliance requirements.