There are excruciatingly high stakes for software today. Trillions of dollars of market cap, billions of consumers, hundreds of billions of revenue, and limitless hours of usage are dependent on software working in real time, all the time, without downtime.
As the sophistication of software delivery has increased, every layer of the tech stack has been rewritten — an accelerated evolution has led to a bevy of multibillion-dollar, up-and-coming unicorns and multiple massive public market debuts.
However, today we’re talking about one of the most integral pillars holding up the internet. The Domain Name System, otherwise known as DNS, is the key addressing system that connects browsers, users, devices and servers together. Type in “www.techcrunch.com” in your browser, and DNS finds the address linked to that name and tells routers and switches across the world which server to connect to and how to send data back to you.
Unlike physical postal addresses, innovation around DNS addressing has flourished in recent years. Traffic management, performance scaling, and cost shaping have turned DNS from a basic directory into a vital layer for guaranteeing the reliability of all software in use on the internet today while protecting the bottom line.
Few companies have parlayed internet infrastructure experience into a world-class engineering company quite like NS1. The New York City-based startup has raised more than $100 million as it builds a strategic node at the core of the modern web delivery tech stack. Customers are flocking: 760 at latest count (up from 600 a year ago), with year-over-year bookings growth well into the triple digits.
How did the company take a slumbering and dreary yet reliable aspect of the internet and turn it into a strategic moat and an enterprise win? And what lessons can we learn about the future of the enterprise infrastructure layer from one of its leading lights? That’s what we’re here to find out.
The lead writer of this EC-1 is Sean Michael Kerner. Kerner has been covering the IT and enterprise infrastructure market for more than a decade as a tech journalist (or, @TechJournalist as he is known on Twitter). Perhaps most importantly, he’s also partially fluent in Klingon, which has no bearing on this EC-1, but is one of those cool facts we wanted to include anyway. The lead editor for this package was Danny Crichton, the assistant editor was Ram Iyer, the copy editor was Richard Dal Porto, and illustrations were drawn by Nigel Sussman.