This conference call transcript was computer generated and almost certianly contains errors. This transcript is provided for information purposes only.EarningsCall, LLC makes no representation about the accuracy of the aforementioned transcript, and you are cautioned not to place undue reliance on the information provided by the transcript.
spk23: And as a reminder, this conference is being recorded and will be available for replay from the Investor Relations section at the Arista website following this call. Ms. Liz Stein, Arista's Director of Investor Relations, you may begin.
spk02: Thank you, operator. Good afternoon, everyone, and thank you for joining us. With me on today's call are J. Sri Ullal, Arista Network's Chairperson and Chief Executive Officer, and Chantel Brightups, Arista's Chief Financial Officer. This afternoon, Arista Networks issued a press release announcing the results for its fiscal first quarter ending March 31, 2024. If you would like a copy of this release, you can access it online at our website. During the course of this conference call, Arista Networks Management will make forward-looking statements, including those relating to our financial outlook for the second quarter of fiscal year, longer-term financial outlooks for 2024 and beyond, our total addressable market and strategy for addressing these market opportunities, including AI, customer demand trends, supply chain constraints, component costs, manufacturing output, inventory management, and inflationary pressures on our business, lead time, product innovation, working capital optimization, and the benefits of acquisitions, which are subject to the risks and uncertainties that we discuss in detail in our documents filed with the SEC, specifically in our most recent Form 10Q and Form 10K, and which could cause actual results to differ materially from those anticipated by these statements. These forward-looking statements apply as of today, and you should not rely on them as representing our views in the future. We undertake no obligation to update these statements after this call. Also, please note that certain financial measures we use on this call are expressed on a non-GAP basis and have been adjusted to exclude certain charges. We have provided reconciliations of these non-GAP financial measures to GAP financial measures in our earnings press release. With that, I will turn the call over to Jay Shwik. Thank you, Liz.
spk04: Thank you, everyone, for joining us this afternoon for our first quarter 2024 earnings call. Amidst all the network consolidation, Arista is looking to establish ourselves as the pure-play for the next era, addressing at least a $60 billion TAM in data-driven -to-cloud AI networking. In terms of Q1 specifics, we delivered revenue of $1.57 billion for the quarter with a non-GAP earnings per share of $1.99. Services and software support renewals contributed strongly at approximately .9% of revenue. Our non-GAP gross margins of .2% was influenced by improved supply chain and inventory management as well as a favorable mix of the enterprise. International contributions for the quarter registered at 20% with the Americas strong at 80%. As we kick off 2024, I'm so proud of the Arista teamwork and our consistent execution. We have been fortunate to build a seasoned management team for the past 10 to 15 years. Our co-founders are very engaged in the company for the past 20 years. Ken is still actively programming and writing code, while Andy is our full-time chief architect for next-generation AI, silicon, and optics initiatives. Hugh Holbrook, our recently promoted chief development officer, is driving our major platform initiatives in tandem with John McCool and Alex on the hardware side. This engineering team is one of the best in tech and networking that I have ever had the pleasure of working with. On behalf of Arista, though, I would like to express our sincere gratitude for Anshul Sadanar's 16-plus wonderful years of instrumental service to the company in a diverse set of roles. I know he will always remain a well-wisher and supporter of the company, but Anshul, I'd like to invite you to say a few words.
spk06: Thank you, Jayashree. The Arista journey has been a very special one. We've come a long way from our startup days to over an $80 billion company today. Every milestone, every event, the ups and downs are all etched in my mind. I've had a multitude of roles and learned and grown more than what I could have ever imagined. I have decided to take a break and spend more time with family, especially when the kids are young. I'm also looking at exploring different areas in the future. I want to thank all of you on the call today, our customers, our investors, our partners, and all the well-wishers over these years. Arista isn't just a workplace, it's family to me. It's the people around you that make life fun. Special thanks to Arista leadership, Chris, Ashwin, John McCool, Mark Ford, Eta and Chantel, Mark Taxey, Hugh Holbrook, Ken Duda, and many more. Above all, there are two very special people I want to thank. Andy Becter-Shine, for years of vision, passion, guidance, and listening to me. And of course, Jeshwari. She hasn't been just my manager, but also my mentor and coach for over 15 years. Thank you for believing in me. I will always continue to be an Arista well-wisher. Back to you, Jeshwari.
spk04: Thank you for that very genuine and heartfelt expression of your huge contributions to Arista. It gives me goosebumps hearing your nostalgic memories. We will miss you and hope someday you will return back home. At this time, Arista will not be replacing the COO role and instead flattening the organization. We will be leveraging our deep bench strength of our executives who stepped up to drive our new Arista 2.0 initiatives. In particular, John McCool, our Chief Platform Officer, and Ken Kaiser, our Group Vice President, have taken expanded responsibility for our cloud, AI, Titan initiatives, operations, and sales. On the non-cloud side, two seasoned executives are being promoted. Ashwin Kohli, Chief Customer Officer, and Krish Nath, Chief Sales Officer, will together address the global enterprise and provide our opportunities. Our leaders have grown up in Arista for a long time with long tenures of a decade or more. We are quite pleased with the momentum across all our three sectors, cloud and AI titans, enterprise, and providers. Customer activity is high as Arista continues to impress our customers and prospects with our undeniable focus on quality and innovation. As we build our programmable network underlays based on our universal least-fine topology, we are also constructing network as a service suite of overlays such as zero-touch automation, security, telemetry, and observability. I would like to invite Ken Duda, our founder, CTO, and recently elected to the Arista board to describe our Enterprise NAS strategy as we drive to our enterprise campus goal of $750 million in 2025. Over to you,
spk08: Ken. Thank you, Jai Shree, and thanks everyone for being here. I'm Ken Duda, CTO of Arista Networks, excited to talk to you today about NetDL, the Arista Network Data Lake, and how it supports our network as a service strategy. From the inception of networking decades ago, networking has involved rapidly changing data, data about how the network is operating, which paths through the network are best, and how the network is being used. But historically, most of this data was simply discarded as the network changed its state, and that which was collected can be difficult to interpret because it lacks context. Network addresses and port numbers by themselves provide little insight into what users are doing or experiencing. Recent developments in AI have proved the value of data. But to take advantage of these breakthroughs, you need to gather and store large data sets labeled suitably for machine learning. Arista is solving this problem with NetDL. We continually monitor every device, not simply taking snapshots, but rather streaming every network event, every counter, every piece of data in real time, archiving a full history in NetDL. Alongside this device data, we also collect flow data and in-band network telemetry data gathered by our switches. Then we enrich this performance data further with user service and application layer data from external sources outside the network, enabling us to understand not just how each part of the network is performing, but also which users are using the network for what purposes and how the network behavior is influencing their experience. NetDL is a foundational part of the EOS stack, enabling advanced functionality across all of our use cases. For example, in AI fabrics, NetDL enables fabric-wide visibility, integrating network data and NIC data to enable operators to identify misconfigurations or misbehaving hosts and pinpoint performance bottlenecks. But for this call, I want to focus on how NetDL enables network as a service. Network as a service, or NAS, is Arista's strategy for up-leveling our relationship with our customers, taking us beyond simply providing network hardware and software by also providing customers or service provider partners with tools for building and operating services. The customer selects a service model, configures service instances, and Arista's CV-NAS handles the rest. Equipment selection, deployment, provisioning, building, monitoring, and troubleshooting. In addition, CV-NAS provides end-user self-service, enabling customers to manage their service instance, provision new endpoints, provision new virtual topologies, set traffic prioritization policies, set access rules, and get visibility into their use of the service and its performance. One can think of NAS as applying cloud computing principles to the physical network, reusable design patterns, scale autonomous operations, multi-tenant from top to bottom with cost-effective automated end-user self-service. And we couldn't get to the starting line without NetDL, as NetDL provides the database foundation of NAS service deployment and monitoring. Now, NAS is not a separate SKU, but really refers to a collection of functions in cloud vision. For example, Arista Validated Designs, or APD, is a provisioning system. It's an early version of our NAS service instance configuration tool. Our Agni services provide global location-independent identity management needed to identify customers within NAS. Our UNO product, or Universal Network Observability, will ultimately become the service monitoring element of NAS. And finally, our NAS solution has security integrated through our ZTN, or Zero Trust Networking, product that we showcased at RSA this week. Thus, our NAS vision simultaneously represents a strategic business opportunity for us, while also serving as a guiding principle for our immediate cloud vision development efforts. While we are really excited about the future here, our core promise to our investors and customers is unchanging and uncompromised. We will always put quality first. We are incredibly proud of the amount of success customers have had deploying our products, because they really work. And as we push hard, building sophisticated new functions in the NetDL and NAS areas, we will never put our customers' networks at risk by cutting quarters on quality. Thank you.
spk04: Thank you, Ken, for your tireless execution in the typical Arista way. In an era characterized by stringent cybersecurity, observability is an essential perimeter and imperative. We cannot secure what we cannot see. We launched Cloud Vision Uno in February 2024 based on the EOS Network Data Lake Foundation that Ken just described for universal network observability. Cloud Vision Uno delivers fault detection, correction, and recovery. It also brings deep analysis to provide a composite picture of the entire network with improved discovery of applications, hosts, workloads, and IT systems of record.
spk22: Okay,
spk04: switching to AI, of course, no call is complete without that. As generative AI training tasks evolve, they are made up of many thousands of individual iterations. Any slowdown due to network can critically impact the application performance, creating inefficient wait states, and idling away processor performance by 30% or more. The time taken to reach coherence, known as job completion time, is an important benchmark achieved by building proper scale-out AI networking to improve the utilization of these precious and expensive GPUs. Arista continues to have customer success across our innovative AI for networking platforms. In a recent blog from one of our large Cloud and AI Titan customers, Arista was highlighted for building a ,000-node GPU cluster based on our flagship 7800 AI spine. This cluster tackles complex AI training tasks that involve a mix of model and data parallelization across thousands of processors, and Ethernet is proving to offer at least 10% improvement of job completion performance across all packet sizes versus InfiniBand. We are witnessing an inflection of AI networking and expect this to continue throughout the year and decades. Ethernet is emerging as a critical infrastructure across both front-end and back-end AI data centers. AI applications simply cannot work in isolation and demand seamless communication among the compute nodes consisting of back-end GPUs and AI accelerators, as well as the front-end nodes, like the CPUs, alongside storage and IPWAN systems as well. If you recall, in February, I shared with you that we are progressing well in four major AI Ethernet clusters that we won versus InfiniBand recently. In all four cases, we are now migrating from trials to pilots, connecting thousands of GPUs this year, and we expect production in the range of 10K to 100K GPUs in 2025. Ethernet at scale is becoming the de facto network and premier choice for scale-out AI training workloads. A good AI network needs a good data strategy delivered by a highly differentiated EOS and network data lake architecture. We are therefore becoming increasingly constructive about achieving our AI target of 750 million in 2025. In summary, as we continue to set the direction of Arista 2.0 networking, our visibility to new AI and cloud projects is improving, and our enterprise and provider activity continues to progress well. We are now projecting above our analyst day range of 10 to 12% annual growth in 2024. And with that, I'd like to turn it over to Chantel for the very first time as Arista CFO to review financial specifics and tell us more. Well, welcome to you,
spk22: Chantel. Thank you, Jashree, and good afternoon. The analysis of our Q1 results and our guidance for Q2 2024 is based on non-GAAP and excludes all non-cash stock-based compensation impacts, certain acquisition-related charges, and other non-recurring items. A full reconciliation of our selected GAAP to non-GAAP results is provided in our earnings release. Total revenues in Q1 were $1.571 billion, up .3% -over-year, and above the upper end of our guidance of $1.52 to $1.56 billion. This -over-year growth was led by strength in the enterprise vertical, with cloud doing well as expected. Services and subscription software contributed approximately .9% of revenue in the first quarter, down slightly from 17% in Q4. International revenues for the quarter came in at $316 million, or .1% of total revenue, down from .3% in the last quarter. This -over-quarter reduction reflects the quarterly volatility and includes the impact of an unusually high contribution from our EMEA in-region customers in the prior quarter. In addition, we continue to see strong revenue growth in the U.S. with solid contributions from our cloud-tightened and enterprise customers. Growth margin in Q1 was .2% above our guidance of approximately 62%. This is down from .4% last quarter and up from .3% in Q1 FY23. The -over-year margin accretion was driven by three key factors. Supply chain productivity gains, led by the efforts of John McCool, Mike Capus, and his operational team, a stronger mix of enterprise business, and a favorable revenue mix between product, services, and software. Operating expenses for the quarter were $265 million, or .9% of revenue, up from last quarter at $262.7 million. R&D spending came in at $164.6 million, or .5% of revenue, down slightly from $165 million last quarter. This reflected increased headcount offset by lower new product introduction costs in the period due to timing of prototypes and other costs associated with our next-generation products. Sales and marketing expense was $83.7 million, or .3% of revenue, compared to $83.4 million last quarter, with increased headcount costs offset by discretionary spending that is delayed until later this year. Our G&A cost came in at $16.7 million, or .1% of revenue, up from .9% of revenue in the prior quarter. Income for operations for the quarter was $744 million, or .4% of revenue. Other income for the quarter was $62.6 million, and our effective tax rate was 20.9%. This resulted in net income for the quarter of $637.7 million, or .6% of revenue. Our diluted share number was 319.9 million shares, resulting in a diluted earnings per share number for the quarter of $1.99, up 39% from the prior year. Now turning to the balance sheet. Cash, cash equivalents, and investments ended the quarter at approximately $5.45 billion. During the quarter, we repurchased $62.7 million of our common stock, and in April we repurchased an additional $82 million for a total of $144.7 million, at an average price of $269.80 per share. We have now completed share repurchases under our existing $1 billion board authorization, whereby we repurchased 8.5 million shares, at an average price of $117.20 per share. In May 2024, our Board of Directors authorized a new $1.2 billion stock repurchase program, which commences in May 2024 and expires in May 2027. The actual timing and amount of future repurchases will be dependent upon market and business conditions, stock price, and other factors. Now turning to operating cash performance for the first quarter. We generated approximately $513.8 million of cash from operations in the period, reflecting strong earnings performance, partially offset by ongoing investments in working capital. DSOs came in at 62 days, up from 61 days in Q4, driven by significant -of-quarter service renewals. Inventory turns were one, flat to last quarter. Inventory increased slightly to $2 billion in the quarter, up from $1.9 billion in the prior period, reflecting the receipt of components from our purchase commitments, and an increase in switch-related finished goods. Our purchase commitments at the end of the quarter were $1.5 billion, down from $1.6 billion at the end of Q4. We expect this number to level off as lead times continue to improve, but will remain somewhat volatile as we ramp up new product introductions. Our total deferred revenue balance was $1.663 billion, up from $1.506 billion in Q4 fiscal year 2023. The majority of the deferred revenue balance is services-related and directly linked to the timing and term of service contracts, which can vary on a -by-quarter basis. Our product deferred revenue balance decreased by approximately $25 million versus last quarter. We expect 2024 to be a year of significant new product introductions, new customers, and expanded use cases. These trends may result in increased customer-specific acceptance clauses and increase the volatility of our product deferred revenue balances. As mentioned in prior quarters, the deferred balance can move significantly on a quarterly basis, independent of underlying business drivers. Accounts payable days were 36 days, down from an unusually high 75 days in Q4, reflecting the timing of inventory receipts and payments. Capital expenditures for the quarter were $9.4 million. Now, turning to our outlook for the second quarter and beyond. I have now had a quarter of working with Jay Sri, the leadership team, and the broader Arista ecosystem, and I am excited about both our current and long-term opportunities in the markets that we serve. The passion for innovation, our agile business operating model, and employee commitment to our customer success are foundational. We are pleased with the momentum being demonstrated across the segments of enterprise, cloud, and providers. With this, we are raising our revenue guidance to an outlook of 12 to 14% growth for fiscal year 2024. On the gross margin front, given the expected end customer mix combined with continued operational improvements, we remain with a fiscal year 2024 outlook of 62 to 64%. Now, turning to spending and investments, we continue to monitor both the overall macro environment and overall market opportunities, which will inform our investment prioritization as we move through the year. This will include a focus on targeted hires and leadership roles, R&D, and the -to-market team as we see opportunities to acquire strong talent. On the cash front, while we continue to focus on supply chain and working capital optimization, we expect some continued growth in inventory on a -by-quarter basis as we receive components from our purchase commitments. With these sets of conditions and expectations, our guidance for the second quarter, which is based on non-GAAP results and excludes any non-cash stock-based compensation impacts and other non-recurring items, is as follows. Revenues of approximately $1.62 to $1.65 billion, gross margin of approximately 64%, and operating margin at approximately 44%. Our effective tax rate is expected to be approximately 21.5%, with diluted shares of approximately 320.5 million shares. I will now turn the call back to Liz for Q&A. Liz?
spk02: Thank you, Chantelle. We will now move to the Q&A portion of the Arista earnings call. To allow for greater participation, I'd like to request that everyone please limit themselves to a single question. Thank you for your understanding. Operator,
spk23: take it away. Thank you. And we will now begin the Q&A portion of the Arista earnings call. In order to ask a question during this time, simply press star and then the number one on your telephone keypad. If you would like to withdraw your question, press the star and the number one again. We ask that you please pick up your handset before asking questions in order to ensure optimal sound quality. And your first question comes from the line of Atif Malik with Citi. Your line is open.
spk21: Hi, it's Adrienne for Atif. Thanks for taking the question. I was hoping you could comment on your raised expectations for the full year with regards to customer mix. It sounds like from your gross margin guidance, you're seeing a higher contribution from enterprise. But I was hoping you could comment on the dynamics you're seeing with your cloud titans. Thank you.
spk04: Yeah, so as Chantelle and I described, you know, when we gave our guidance in November, we didn't have much visibility beyond three to six months. And so we had to go with that. The activity in Q1 alone, and I believe it will continue in the first half, has been much beyond what we expected. And this is true across all three sectors, cloud and AI titans, providers and enterprise. So we're feeling good about all three and therefore have raised our guidance earlier than we probably would have done in May. I think we would have ideally like to look at two quarters. Chantelle, what do you think? But I think we felt good enough. Yeah, no, I think
spk22: we saw because of the diversified momentum and the mix of the momentum that gave us confidence.
spk05: Great. Thanks, Adrienne.
spk23: And your next question comes from the line of Somic Chatterjee with JP Morgan. Your line is open.
spk12: Hi, thanks for taking my question. I guess, Jeshwia and Chantelle, I appreciate the sort of raise and the guidance for the full year here. But when I look at it on a half over half basis in terms of what you're implying, if I am doing the math correct, you're implying about a sort of five, six percent half over half growth, which when I go back and look at previous years, you're probably there's only one year out of the last five or six that you've been in that sort of range or below that every other year. It's been better than that. I'm just wondering, you mentioned the Q1 activity that you've seen across the board. Why are we not seeing a bit more of a half over half uptake than in sort of the momentum in the back half? Thank you.
spk04: Thanks. You know, it's like anything else. Our numbers are getting larger and larger. So activity has to translate to larger numbers. So, of course, if we see it improve even more, we'll guide appropriately for the quarter. But at the moment, we're feeling very good just increasing our guide from 10 to 12 to 12 to 14. As you know, Arista doesn't traditionally do that so early in the year. So please read that as confidence, but, you know, cautiously confident or optimistically confident, but nevertheless confident.
spk10: Thank you.
spk23: And your next question comes from the line of Ben Reitzes with Melius Research. Your line is open.
spk05: Ben, if you're talking, we can't hear you. Operator, can we hear you
spk23: back then? We will move on to the next question. Mr. Reitzes, if you can hear us, please re-hit star one. And we will move to our next question from George Nauter with Jeffries. Your line is open.
spk09: Hi, guys. Thanks a lot. I want to key in on something I think you guys said earlier in the monologue. You mentioned that Ethernet was 10% better than InfiniBand and my notes are incomplete here. Could you just remind me exactly what you were talking about there? What is the comparison you're making to InfiniBand and just anything? I'd love to learn more about that.
spk04: Absolutely, George. You know, historically, as you know, when you look at InfiniBand and Ethernet in isolation, there are a lot of advantages of each technology. Traditionally, InfiniBand has been considered lossless and Ethernet is considered to have some loss properties. However, when you actually put a full GPU cluster together along with the optics and everything, and you look at the coherence of the job completion time across all packet sizes, data has shown, and this is data that we have gotten from third parties, including Broadcom, that just about every packet size in a real world environment, and independent of comparing those technologies, the job completion time of Ethernet was approximately 10% faster. So you can look at these things in silos, you can look at it in a practical cluster, and in a practical cluster, we're already seeing improvements on Ethernet. Now, don't forget, this is just Ethernet as we know it today. Once we have the UltraEthernet consortium and some of the improvements you're going to see on packet spraying and dynamic load balancing and congestion control, I believe those numbers will get even better.
spk09: Got it. I assume you're talking about Rocky here as opposed to just straight up Ethernet, is that correct?
spk04: In all cases right now, pre-UEC, we're talking about RDMA over Ethernet, exactly, Rocky version 2, which is the most widely deployed NIC you have in most scenarios. But with each level Rocky, we're seeing 10% improvement. Imagine when we go to UEC.
spk09: I know you guys are also working on your own version of Ethernet. Presumably it blends into the UEC standard over time, but what do you think the differential might be there relative to InfiniBand? Do you have a sense on what that might look like?
spk04: I don't think we have metrics yet, but it's not like we're working on our own version of Ethernet. We're working on the UEC compatible and compliant version of Ethernet. There's two aspects of it, what we do on the switch and what others do on the NIC. What we do on the switch, I think, will be we've already built an architecture, we call it the Etherlink architecture, that takes into consideration the buffering, the congestion control, the load balancing, and largely we'll have to make some software improvements. The NICs, especially at 400 and 800, is where we are looking to see more improvements because that will give us additional performance from the server onto the switch. So we need both halves to work together. Thanks,
spk09: George. Thank
spk23: you. Thanks, George. And your next question comes from the line of Ben Reitzes with Milius Research. Your line is open.
spk11: Gosh, I hope it works this time.
spk23: Yeah, we can hear you now.
spk11: Oh, great. Thanks a lot. I was wondering if you can characterize how you're seeing NVIDIA in the market right now, and are you seeing yourselves go more -to-head? How do you see that evolving? And if you don't mind, also, as NVIDIA moves to a more systems-based approach, potentially with Blackwell, how do you see that impact in your competitiveness with NVIDIA? Thanks so much.
spk04: Yeah. Thanks, Ben, for a loaded question. First of all, I want to thank NVIDIA and Jensen. I think it's important to understand that we wouldn't have a massive AI networking opportunity if NVIDIA didn't build some fantastic GPUs. So, yes, we see them in the market all the time, mostly using our networks to their GPUs. And NVIDIA is the market leader there, and I think they've created an incremental market opportunity for us that we are very, very rejoiced by. Now, do we see them in the market? Of course we do. I see them on NVIDIA's GPUs. We also see them on the, you know, Rocky or RDMA Ethernet NIC side. And then sometimes we see them, obviously, when they're pushing InfiniBand, which has been, for most part, the de facto network of choice. You might have heard me say last year or the year before, I was outside looking into this AI networking. But today we feel very pleased that we are able to be the scale-up network for NVIDIA's GPUs and NICs based on Ethernet. We don't see NVIDIA as a direct competitor yet on the Ethernet side. I think it's 1% of their business. It's 100% of our business. So we don't worry about that overlap at all. And we think we've got, you know, 20 years of founding to now experience to make our Ethernet switches better and better, both on the front end and back end. So we're very confident that ARISTA can build the scale-up network and work with NVIDIA's scale-up GPUs.
spk23: Thank you, Ben.
spk11: Thanks a lot.
spk23: And your next question comes from the line of Amit Daryanani with Evercore ISI. Your line is open.
spk03: Good afternoon. Thanks for taking my question. I guess, Jash, given some of the executive transitions you've seen at ARISTA, can you perhaps talk about, Dixon, you can, the discussion you've had with the board around your desire, your commitment to remain the CEO. Does anyone have any thoughts on that? That would be really helpful. And then if I just go back to this job completion data that you talked about, given what you just said and the expected improvement, what are the reasons a customer would still use InfiniBand versus switch more aggressively towards Ethernet? Thank you.
spk04: First of all, you know, you heard Anshul. I'm sorry to see Anshul decide to do other things. I hope he comes back. We've had a lot of executives, you know, make a U-turn over time and we call them boomerangs. So I certainly hope that's true with Anshul. But we have a very strong bench. And we've had, we've been blessed to have a very constant bench for the last 15 years, which is very rare in our industry and in the Silicon Valley. So while we're sorry to see Anshul make a personal decision to take a break, we know he'll remain a well-wisher and we know the bench strength below Anshul will now step up to do greater things. As for my commitment to the board, I have committed for multiple years. I think it's the wrong order. I wish Anshul had stayed and I'd retired, but I'm committed to staying here for a long time.
spk23: Thank you. And your next question comes from the line of Antoine Chquivon with New Street Research. Your line is open.
spk15: Thank you so much for taking my question. So, as you can see, NVIDIA introduced in-network computing capabilities with NVSwitch, performing some calculations inside the Switch itself. Perhaps now is not the best time to announce new products, but I'm curious about whether this is something the broader merchant Silicon and Ethernet ecosystem could introduce at some point.
spk04: Antoine, are you asking what is our new product for AI? Is that the question?
spk15: No, I'm asking specifically about in-network computing capabilities. You know, NVSwitch can do some matrix multiply and add inside the Switch itself. And I was wondering if this is something that the broader merchant Silicon and Ethernet ecosystem could introduce as well.
spk04: Yeah. So just for everyone else's benefit, a lot of the in-network compute is generally done as closest to the compute layer as possible, you know, where you're processing the GPU. So that's a very natural place. I don't see any reason why we could not do those functions in the network and offload the network for some of those compute functions. It would require a little more state and built-in processing power, et cetera, but it's certainly very doable. I think it's going to be six of one and half a dozen of the others. Some would prefer it closest to the compute layer and some would like it network wide for network scale at the network layer. So the feasibility is very much there in both cases, Antoine. Thanks, Antoine.
spk23: Thank you. And your next question comes from the line of James Fish with Piper Sandler. Your line is open.
spk01: Hey, thanks for the question. Antoine, we'll miss having you around. I quote my sentiments there, but hope to see you soon. Jayshree, how are you guys thinking about timing of the 800 gig optics availability versus kind of use in systems? And you keep alluding to kind of next-gen product announcements, you know, for multiple quarters. Not just this one, but should we expect this to be more around adjacent use cases, the core, including AI or software? Kind of take us in the product road, that direction, if you can.
spk04: Yeah. You know, James, you might remember like deja vu. We've had similar discussions on 400 gig too. And as you well know, you know, to build a good switching system, you need an ecosystem around it, whether it's the NICs, the optics, the cables, the accessories. So I do believe you'll start seeing some early introduction of optical and switching products for 800 gig. But to actually build the entire ecosystem and take advantage, especially of the NICs, I think will take more than a year. So I think probably more into 25 or even 26. That being said, I think you're going to see a lot of systems. I had this discussion earlier. You're going to see six of one and half a dozen of the other. You're going to see a lot of systems where you can demonstrate high rating scale with 400 gig and go east west much wider and build large clusters that are in the tens of thousands. And then once you need once you have GPUs that source 800 gig, which even some of the recent GPUs don't, then you'll need not just higher ratings, but higher performance. So I don't see the ecosystem of 800 gig, you know, limiting the deployment of AI networks. That's an important thing to remember. Thanks,
spk03: James. Thank you.
spk04: Thank
spk23: you, James. And your next question comes from the line of Simon Leopold with Raymond James. Your line is open.
spk19: Hi, guys. This is Victor Chuen for Simon Leopold. Do you expect Arista to see a knock on effect from AI networking in the front end or at the edge as customers eventually deploy more AI workloads based, I'm sorry, biased towards inferencing and then maybe help us understand how we might be able to size this if that's the case?
spk04: Simon, that's a key question. We haven't taken the internet into consideration. That's basically production. But you're absolutely right to say as you have more backend, then the backend has to connect to something, which typically rather than reinventing IP and adaptive routing, you would connect to the front end of your compute and storage and WAN networks. So while we do not take that into consideration in our 750 million projection in 2025, we naturally see the deployment of more backend clusters resulting in a more uniform compute storage memory, you know, overall front end, back end, holistic network for AI coming in the next phase. So I think it makes a lot of sense. We just we but we first want to get the clusters deployed and then we'll do the a lot of our customers are fully expecting that holistic connection. And that's one, by the way, one of the reasons they look so favorably at us. They don't want to build this disparate silos and islands of AI clusters. They really want to bring it in terms of a full uniform AI data center. Thanks so much.
spk23: And your next question comes from the line of Mita Marshall with Morgan Stanley. Your line is open.
spk20: Great. Thanks. Maybe I'll flip James's question and just kind of ask, you know, what do you see as kind of some of the bottlenecks from going to from pilots to ultimate deployments? You know, it sounds like it's not necessarily 800 gig. And so, you know, is it just a matter of time? Are there other pieces of the ecosystem that are that need to fall into place before some of those deployments can take place? Thanks.
spk04: I would I wouldn't call them media bottlenecks. I would definitely say it's a time based and familiarity based situation. You know, the cloud, everybody knows how to deploy that it's sort of, you know, plug and play in some ways. And but even in the cloud, if you may recall, there were many use cases that emerged. The first use case that's emerging for AI networking is let's just build the fastest training workloads and clusters. And, you know, they're they're looking at performance. Power is a huge consideration. The cooling of the GPUs is a huge part of it. You would be surprised to hear a lot of times it's just waiting on the facilities and waiting for the infrastructure to be set up. Right. Then on the OS and operating side and, you know, Ken has been quiet here and love him to chime in. But there's a tremendous amount of foundational discovery that goes into what do they need to do in the cluster? You know, do they need to do some hashing? Do they do need to do load balancing? Do they need to do this at layer two, layer three? Do they need visibility features? Do they need to connect it across the WAN or interconnect? So and of course, as you rightly pointed out, there's the whole 400, 800 where but we're seeing less of that because a lot of it is familiarity and understanding how to operate the cluster with the best job completion time and visibility, manageability and availability of the GPUs. Nobody can tolerate downtime. Ken, I'd love to hear your point of view on this.
spk08: Yeah, thanks, Jaystree. Look, I think that what's blocking people's deployment is the availability of all the pieces. And so there's a huge pent up demand for this stuff. And we see these clusters getting built as fast as people can build the facilities, get the GPUs and get them the networking they need. And I think that, you know, we're extraordinarily well positioned here because we've got years of experience building scaled storage clusters, some of the world's largest cloud players and storage clusters are not identical to AI clusters, but they have some of the same issues with managing a massive scale back end network that needs to be properly load balanced, needs a lot of buffer to manage bursts. And so and then some of the congestion management stuff we've done there is also useful in AI networks. And in particular, this InfiniBand topic keeps coming up. I just like to point out that Ethernet is about 50 years old. And over those 50 years, Ethernet has come head to head with a bunch of technologies like, you know, token ring, sonnet, ATM, FIDI, Hippie, scalable coherent interconnect, mirror net. And all of these battles have one thing in common. Ethernet one. And the reason why Ethernet one is because of Metcalfe's law, that the value of a network is quadratic in the number of nodes that can interconnect. And so anybody who tries to build something which is not Ethernet is starting off with a very large quadratic disadvantage. At any temporary advantage they have because of some detail of the tech cycle is going to be quickly overwhelmed by the connectivity advantage you have with Ethernet. So I think, you know, exactly how many years it takes for InfiniBand to go away from fiber channel, you know, I'm not sure. But that's where it's all headed.
spk23: Thank
spk20: you.
spk23: And your next question comes from the line of Ben Bolin with Cleveland Research Company. Your line is open.
spk13: Good afternoon, everyone. Thanks for taking the question. J3, you made a comment that back when you had guided in November, you had about three to six months of visibility. Could you take us through what type of visibility you have today and maybe compare and contrast the different subsets of customers and how they differ? Thank you.
spk04: Thank you, Ben. That's a good question. So let me take it by category. Like you said, in the cloud and AI titans in November, you know, we're really searching for even three months visibility. Six would have been amazing. Today. You know, I think after a year of tough, tough situations for us where the cloud titans were pivoting rather rapidly to AI and not thinking about the cloud as much, we're now seeing a more balanced approach where they're still doing AI, which is exciting, but they're also expanding their regions on the cloud. So I would say our visibility has now improved to at least six months. And maybe it gets longer as time goes by on the enterprise. You know, I don't know. I'm not I'm not a bellwether for macro, but everybody else is citing macro, but I'm not seeing macro. What we're seeing with Krishnit and Ashwin and the entire team is, you know, a profound amount of activity in Q1 better than we normally see in a Q1. Q1 is usually, you know, come back from the holidays, January slow. There's some East Coast storms to deal with. Winter is still strong. But we have had one of the strongest activities in Q1, which leads us to believe that it can only get better for the rest of the year. Hence the guide increase from an otherwise conservative team of Chantelle and myself. Right. And then the tier two cloud providers, I want to speak to them for a moment because not only are they strong for us right now, but they are starting to pick up some AI initiatives as well. So they're not as large, of course, as the cloud titans. But the combination of the service providers and the tier two specialty providers is also seeing some momentum. So overall, I would say our visibility has now improved from three months to over six months. And in the case of the enterprise, obviously, our sales cycles can be even longer. So it takes time to convert into wins, but the activity has never been higher.
spk23: Thanks, Ben.
spk06: Thank you.
spk23: And your next question comes from the line of Michael Ng with Goldman Sachs. Your line is open.
spk16: Hey, good afternoon. Thank you very much for the question. It was very encouraging to hear about the migration of trials to pilots with ANET production rollout to support GPUs in the range of, I think you said, 10,000 to 100,000 GPUs for 2025. First, I was just wondering if you could talk about some of the key determinants about how we end up in that range, high-end versus low-end. And then second, assuming $250,000 per GPU, that would imply about $25 billion of compute spending. ANET's target of $750 million would only be about 3% of the high end. And I think you've talked about 10% to 15% networking as a percentage of compute historically. So I was just wondering if you could talk about what I'm missing there, if there's anything to call out in those assumptions. Thank you.
spk04: Yeah, thank you, Michael. I think we could do better next year. But your point is well taken that in order to go from 10,000s of GPUs to 30,000, 50,000, 100,000, a lot of things have to come together. First of all, let's talk about the data center or AI center facility itself. There's a tremendous amount of work and lead time that goes into the power, the cooling, the facilities. And so now when you're talking this kind of production as opposed to proving something in the lab, that's a key factor. The second one is the GPU, the number of GPUs, the location of the GPUs, the scale of the GPUs, the locality of these GPUs. Should they go with Blackwell? Should they build with a scale up inside the server or scale out to the network? So the whole center of gravity, what's nice to watch, which is why we're more constructive on the 2025 numbers, is that the GPU lead times have significantly improved, which means more and more of our customers will get more GPUs, which in turn means they can build out the scale out network. But again, a lot of work is going into that. And the third thing I would say is the scale, the performance, how much ratings they want to put in. And I'll give a quick analogy here. We ran into something similar on the cloud when we were talking about four-way ECMP or eight-way ECMP or these rail-based designs, as it's often called, and the number of NICs you connect to to go eight-way or four-way or 12-way or switch off and go to 800 gig. The performance and scale will be the third metric. So I think power, GPU locality, and performance of the network are the three major considerations that allow us to get more positive on the rate of production in 2025.
spk05: Thanks, Nino.
spk23: And your next question comes from the line of Matthew Nicknam with Deutsche Bank. Your line is open.
spk17: Hey, thanks so much for taking the question. I got to ask one more on AI. Sorry to beat a dead horse. But as we think about the stronger start to the year and the migration from trials to pilots specific in relation to AI, is there a ramp towards getting to that 750 mil next year? And I guess more importantly, is there any material contribution baked into this year's outlook or is there any contribution that may be driving the two percentage point increase relative to the prior guide for 2024?
spk22: Thanks. Pentel, you want to take that? I've been talking about AI a lot. I think you should. Yeah, I can take this AI question. So I think that when you think about the 750 million target that has become more constructive to JSTRI's prepared remarks, that's a glide path. So it's not zero in 2024. It's a glide path to 2025. So I would say there is some assumed in the sense of it's a glide path, but it will end in 2025 at the 750 in the glide path, not a hockey stick. Yeah,
spk04: it's not zero this year.
spk22: Yeah,
spk04: Matt,
spk05: for sure. Yeah. Thank you.
spk23: And your next question comes from the line of Sebastian Naji with William Blair. Your line is open.
spk18: Thanks. Good afternoon. I've got a non AI question here. So maybe you can talk a little bit about some of the incremental investments that you're making within your go to market this year, particularly as you look to grab some share from competitors. You know, a lot of them are going through some type of disruption, one or the other acquisitions, etc. And then what you might be doing with the channel partners to land more of those mid market customers as well.
spk04: Yeah, Sebastian, we're probably doing a little more on investment than we have done enough progress on channel partners, to be honest. But last couple of years, we were getting very apologetic about our lead times. Our lead times have improved. So we have stepped up our investment on go to market, where I'm expecting Krishnad and Ashwin's team to grow significantly. And judging from the activity they've had and the investments they've been making in 23 and 24, we're definitely going to continue pedal to the metal on that. I think our investments in AI and cloud type remain about the same because, you know, while there is a significant technical focus on the systems engineering and product side, we don't see a significant change on the go to market side. And on the channel partners, I would say, you know, where this really comes to play, and this will play out of a multiple years, it's not going to happen this year, is on the campus. You know, today our approach on the campus is really going after our larger enterprise customers. We got 9000 customers, probably 2500 that we're really going to target. And so our mid market is more targeted at specific verticals like healthcare, education, public sector. And then we appropriately work with the channel partners in the region, in the country, to deal with that. And to get to the first billion, I think this will be a fine strategy. As we aim beyond 750 million to a billion and we need to go to the second billion, absolutely we need to do more work on channels. This is still work in progress.
spk23: Thanks, Sebastian.
spk13: Thank you.
spk23: And your next question comes from the line of Aaron Rakers with Wells Fargo. Your line is open.
spk10: Yeah, thanks for taking the questions. I'm going to shift gears away from AI actually. You know, if we look at the server market over the past handful of quarters, we've seen unit numbers down quite considerably. I'm curious as you look at some of your larger cloud customers, how you would characterize the traditional server side and whether or not you're seeing signs of them moving past this kind of optimization phase and whether or not you think a server refresh cycle in front of you could be a paper metal catalyst to the company.
spk04: Yeah, no, I think if you remember, there was this one dreadful year where one of our customers skipped a server cycle. But generally speaking on the front end network now, we're going back to the cloud and we do see service refresh and server cycles continue to be in the three to five years. For performance upgrades, they like three, but occasionally some of them may go a little higher. So absolutely we believe there will be another cloud cycle because of the server refresh and the associated use cases because once you do that on the server, there's appropriately the regional spine and then the data center interconnect and the storage and so much ripple effect from that server use case upgrade. That side of compute and CPU is not changing. It's continuing to happen. In addition to which we're also seeing more and more regional expansion. New regions are being created and designed and outfitted for the cloud by our major titans.
spk05: Yeah, thank you.
spk23: And your next question comes from the line of Carl Ackerman with BNP Parabot. Your line is open.
spk14: Thank you. Jashree, you spoke about how you are not seeing slowness in enterprise. I'm curious whether that is being driven by the growing mix of your software revenue and do you think the deployment of AI networks on prem can be a more meaningful driver for your enterprise and financial customers in the second half of fiscal 24 or will that be more of a fiscal 25 event? Thank you.
spk04: Well, that's a really good question. I have to analyze this some more. I would say our enterprise activity is really driven by the fact that Ken has produced some amazing software quality and innovation. And we have a very high quality universal topology where you don't have to buy five different OS's and 50 different images and operate this network with thousands of people. It's a very elegant architecture that applies to the data center use case that you just outlined for the spine. The same universal spine can apply to the campus. It applies to the wide area. It applies to the branch. It applies to security. It applies to observability. And you bring up a good point that while the enterprise use cases for AI are small, we are seeing some activity there as well. Relative to the large AI titans, they're still very small, but think of them as back in the trial phase. I was describing earlier, trials, pilots, production. So a lot of our enterprise customers are starting to go in the trial phase of GPU clusters. So that's a nice use case as well. But the biggest ones are still in the data center campus and the general purpose enterprise.
spk05: Thank
spk23: you. Operator, we have time for one last question. Thank you. And your final question comes from the line of David Vogt with UBS. Your line is open.
spk07: Great. Thanks, guys. And congratulations. So, Jason, we have a question about, I want to go back to AI, the roadmap and the deployment schedule for Blackwell. So it sounds like it's a bit slower than maybe initially expected with initial customer delivery late this year. How are you thinking about that in terms of your roadmap specifically and how that plays into what you're thinking about 25 in a little bit more detail? And does that late delivery maybe put a little bit of a pause on maybe some of the cloud spend, you know, in the fall of this year, as there seems to be somewhat of a technology transition going on towards Blackwell away from the legacy product? Thanks.
spk04: Yeah, we're not seeing a pause yet. I don't think anybody's going to wait for Blackwell necessarily in 2024 because they're still bringing up their GPU cluster. And, you know, how a cluster is divided across multiple tenants, the choice of host, memory, storage architectures, optimizations on the GPU for collective communication libraries, specific workloads, resilience, visibility. All of that has to be taken into consideration. All this to say a good scale out network has to be built no matter whether you're connecting to today's GPUs or future Blackwells. And so they're not going to pause the network because they're waiting for Blackwell. They're going to get ready for the network, whether it connects to a Blackwell or a current H100. So as we see it, you know, the training workloads and the urgency of getting the best job completion time is so important that they're not going to spare any investments on the network side. And the network side can be ready no matter what the GPU is.
spk02: Thanks, David. This concludes the Arista Network's first quarter 2024 earnings call. We have posted a presentation which provides additional information on our results, which you can access on the Investors section of our website. Thank you for joining us today and thank you for your interest in Arista.
spk23: Ladies and gentlemen, thank you for joining. This concludes today's call and you may now disconnect.
spk02: Thank you.
Disclaimer