30 years at the application layer

Kunal AnandChief Product Officer | F5

In 1997, most people running web infrastructure were patching solutions together in real time. Traffic spikes took sites down. Servers got added manually when capacity ran out, which was usually too late. The question was never whether the web would grow. It was whether the infrastructure underneath it could keep up.

F5 started with a simple conviction: the answer was not more servers. It was smarter traffic. F5 BIG-IP put application-aware intelligence directly in the data path, making decisions based on real-time conditions rather than static rules. That choice, to treat application delivery as an intelligent system problem rather than a hardware scaling problem, became the throughline of everything that followed.

Thirty years is a long time in technology. Most companies that were relevant in 1996 are not. The ones that survived didn't just execute well. They stayed close to the right problem.

For F5, that problem has always been the same: keeping applications fast, available, and secure as the world around them changes. The world has changed several times over

1996 to 2005: When the Internet outgrew its own infrastructure

The early web was built for curiosity, not commerce. When it became both, the cracks appeared fast. Availability mattered now. Performance failures were business failures. The category F5 helped define, the application delivery controller, emerged from a straightforward observation: the network layer didn't understand applications, and that blind spot was costing people.

BIG-IP placed intelligence directly in the path of application traffic. Not just routing packets but understanding what those packets were for and making decisions accordingly. As applications grew more interconnected, delivery and security began to converge. Identity-aware access, application security, and full-proxy architectures followed. The foundation was laid for a model that treated performance, reliability, and protection as parts of the same system, rather than separate products running alongside each other.

2006 to 2015: When virtualization changed the rules

Cloud and mobile access changed how applications were built and consumed. Infrastructure became dynamic. Traditional network perimeters started to fade. The threat surface shifted with it.

F5 evolved hardware and software together during this period. VIPRION anticipated elastic, cloud-scale behavior inside the data center. BIG-IP Virtual Edition extended delivery and security into virtualized and cloud environments. Applications could move without losing consistency or control.

The clearer insight from this era was about security. Applications, not networks, had become the primary attack surface. Protecting the network perimeter was no longer enough. F5 deepened its focus on application-centric security, integrating protection directly into the traffic path. The two disciplines, performance and security, had to be engineered together. That thinking shapes the platform F5 runs today.

2016 to 2022: The hardest transition

This was the era that required the most change, and it's worth being honest about that.

Cloud and multicloud adoption accelerated. Flexibility increased. So did fragmentation. Teams deployed more tools, platforms, and policies, often without a unified way to manage them. And F5 faced a version of that same challenge internally: how do you serve a world that is moving toward developer-driven, software-defined infrastructure when your core business was built around appliances and network operations teams?

The answer came in two moves.

The acquisition of NGINX brought a modern, developer-first approach to application delivery into the portfolio. NGINX was already running inside more companies than most people realized, sitting in Kubernetes clusters and CI/CD pipelines, managed by the people writing the code rather than the people running the network. Bringing it into F5 meant F5 could meet developers where they were working, not just where the network team was.

F5 Distributed Cloud Services introduced SaaS-delivered networking and security for highly distributed environments. It was a bet that the future of infrastructure management would look more like software than hardware, and that customers would need a way to apply consistent policy across clouds, data centers, and the edge without building a different operational model for each.

Neither acquisition was simple to integrate. Neither fit cleanly into the existing motion. That's exactly why they mattered. The companies that stayed relevant through this era were the ones willing to absorb that kind of friction.

The lesson from this period was reinforced constantly: complexity, left unmanaged, becomes risk. Not just operational risk. Strategic risk. Customers needed to simplify without sacrificing performance, visibility, or control. F5 needed to build a way to offer that.

2023 to 2026: The F5 Application Delivery and Security Platform

By the early 2020s, the attack surface had fundamentally changed. APIs outnumbered traditional application interfaces. AI workloads demanded both extreme throughput and new categories of protection, including risks that didn't yet have established names. Software supply chains became vectors. Threats moved faster than teams could track them manually.

The response F5 developed was architectural rather than additive. Rather than continuing to extend the portfolio, F5 consolidated it. In 2025, F5 introduced the F5 Application Delivery and Security Platform (ADSP), bringing together high-performance traffic management and comprehensive application and API security into a single operational model.

The premise behind F5 ADSP is that delivery and security cannot be optimized independently when they share the same traffic path. The intelligence that optimizes performance should also enforce protection. A single platform means a single source of truth for policy, visibility, and control across hybrid multicloud environments. It reduces the operational surface area that complexity would otherwise exploit.

Thirty years of learning what breaks in application infrastructure, distilled into a platform built for what comes next.

What 30 years actually means

Three decades in, the pattern holds.

Every time the architecture of the Internet shifts, a new set of failure modes emerges. Scale breaks things. Perimeters dissolve. Complexity concentrates risk. F5 has navigated each of those transitions by staying close to the application layer, where traffic, security, and performance converge.

The gratitude here is real: to the customers who kept raising harder problems, to the partners who helped extend the reach of those solutions, and to the people inside F5 who did the actual work across every one of those eras.

What's ahead won't be simpler. AI is reshaping both what applications do and how they get attacked. The organizations that manage that transition well will be the ones with an infrastructure intelligent enough to keep up.

That's still the work. It's been the work since 1996.

To learn more, read our recent blog post, “30 years of F5 through the eyes of F5ers.

About the Author

Kunal AnandChief Product Officer | F5

Kunal Anand leads the F5 product organization as Chief Product Officer. Responsible for product vision, strategy, and execution, he ensures development of breakthrough solutions that solve critical challenges and create exceptional experiences for customers. In his previous role as Chief Technology and AI Officer, Kunal charted the company’s technology and AI strategy and vision. Prior to F5, Kunal held the dual role of Chief Technology Officer and Chief Information Security Officer at Imperva. His journey to Imperva began in 2018 with the acquisition of Prevoty, an application security startup he co-founded in 2013. Before joining Prevoty, he was the Director of Technology at BBC Worldwide. Kunal has a deep history of innovation and technical expertise, and has held roles leading security, data, technology, and engineering teams at Gravity, MySpace, and the NASA Jet Propulsion Lab. Kunal has over 15 years of experience in AI and machine learning, ranging from model training, employing AI-driven algorithms to enhance products, and designing and implementing AI architectures. Kunal holds a Bachelor of Science degree in computer science from Babson College.

More blogs by Kunal Anand