The Endless OS Foundation, a social welfare nonprofit, has been working to bridge the digital divide by increasing access to affordable devices and building software that reduces the need for high-speed connectivity. However, the COVID-19 pandemic exacerbated the digital divide, causing a surge in demand for online educational content. As a result, the Foundation saw an increase in downloads and updates, leading to a spike in egress costs. Their existing content delivery network (CDN) was unable to provide efficient solutions, and they were experiencing CDN dead zones in regions like Southeast Asia, Central, and South America, where they have a significant number of users. The quality of their service was inconsistent, and costs were continually increasing.

Filestack, a low code content API platform, was facing challenges in scaling their rapidly growing file management service. They were in need of a Content Delivery Network (CDN) that could support their expanding services in a reliable, cost-effective, and fast manner. Their service involved image transformation, which resulted in multiple versions of the same file, and they needed a way to invalidate these versions quickly. They also required customization at the edge, a large number of powerful and strategically located Points of Presence (POPs), and the ability to handle large file sizes. Additionally, Filestack was struggling with the management of Transport Layer Security (TLS) certificates, a task that was distracting their team from product development. They were also considering dropping a premium feature, CNAME, due to the burden of managing a certificate and private key for each customer.

Trade Me, New Zealand’s largest auction and classifieds site, faced a significant challenge during its digital transformation. The company, which has been in eCommerce since 1999, initially relied on New Zealand-based data centres in Auckland and Wellington. However, these centres required manual processes for configuration and maintenance, which were cumbersome and inefficient. The company decided to transition to the public cloud for scalability and automation benefits. However, this move presented its own set of challenges. The majority of Trade Me's customers are based in New Zealand, but the nearest Google Cloud servers were in Sydney, Australia, over 2,000km away. This distance posed potential issues for content delivery speed and customer experience. Additionally, the cloud migration raised new security and reliability challenges. For instance, if international connectivity was impacted by network failure or cyberattacks, the company could still serve domestic customer traffic with their New Zealand servers. However, this would not be possible with the cloud servers located in Australia.

The Weather Company, a premier provider of accurate weather forecasts, insights, and alerts, serves over 400 million monthly active users worldwide. The company's primary challenge is managing the scale and volume of its user base, which peaks during severe weather events such as hurricanes or winter storms. The company needed a robust configuration, setup, and technology to support its users, particularly in delivering video technology and handling hundreds of millions of requests daily. These requests are crucial as users rely on them to make quick decisions during severe weather conditions.

A+E Networks, a global entertainment company, was facing challenges in managing its streaming media services. With a portfolio of seven popular video brands, the company reaches 335 million people worldwide. However, the increasing demand for more viewers, more bandwidth, and more content was putting pressure on developers to deliver frequently and fast. The company's configuration management was largely manual and became slow and cumbersome as their portfolio grew. A build across each site could take hours, and as they added programming and moved to microservices, the time only expanded. A+E Networks also lacked visibility with their legacy Content Delivery Network (CDN), having to rely on professional services with no view of what was happening behind the scenes. The company wanted to empower developers to implement services and upgrades quickly and manage traffic spikes with a multi-CDN model.

Slate Magazine, a digital media pioneer, faced significant challenges with their legacy Content Delivery Network (CDN). The CDN lacked the agility to purge content and complete updates at the speed required by the rapidly evolving digital media landscape. The process of waiting for a change to go live could take as much as 15 minutes, which was highly inefficient in the fast-paced digital media industry. Additionally, the legacy CDN charged on a per-service basis and required XML for updates, adding to the workload of Slate's already busy team of developers. These challenges prompted Slate to seek a more efficient and agile solution.

Finn AI, a provider of AI-powered virtual assistance for banks and credit unions, faced a significant challenge in securing their business-critical APIs. The company, which uses natural language processing technology (NLP) to enable conversational AI technology for financial institutions, needed a solution that would provide visibility into API discovery attempts by malicious threat actors and the ability to stop unusual activity against these APIs. Despite having a relatively small attack surface due to the absence of a client-side frontend, Finn AI's APIs still required effective protection. The company sought a solution that would install easily, scale effectively, be light on resources, and provide protection against OWASP Top 10 and zero-day exploit attempts.