All right. Good morning. Welcome to day four of the Morgan Stanley TMT Conference. I have to say, this is the best Thursday lineup I've ever seen. This is my 11th Morgan Stanley TMT Conference. We're going to continue the program with the JFrog Management Team. We have Chief Financial Officer Ed Grabscheid and VP of IR, Jeff Schreiner. Ed and Jeff, thank you for joining us, once again at the Morgan Stanley TMT Conference.
Thank you for having us.
Awesome. I don't see my disclosure. Will you give me one second? Here we go. Get the disclosures out of the way. For important disclosures, please see the Morgan Stanley Research Disclosure website at www.morganstanley.com/researchdisclosures. If you have any questions, please reach out to your Morgan Stanley sales representative. With that, let's go ahead and start the conversation from a high level. In 2024, the business grew 22.5% from about 25% in 2023, while operating margins expanded about 400 basis points to just under 15%. Ed, looking back, where do you feel the team executed well, and what were some of the challenges that 2024 presented?
Well, 2024 in general was a very interesting year. So let me just kind of summarize what happened. We released a new product. We did an acquisition. We were faced with a macro, you know, macroeconomic headwind. We also had a geopolitical situation that we had to deal with. And it was an administration year, an administration change. Five headlines that normally you have one or two in a year, we had five. So that in itself created challenges. But we're very happy with where we ended for the full year. First, security. When I look at security and what we did in terms of the achievement in security, and we'll talk more about that, I'm sure, but the fact that we delivered 3% of our revenue in security was a big win for us and the penetration in terms of security budgets. Secondly, the cloud.
You remember after Q1, we were punished. We did 47% growth in the cloud, and we were punished for 47% growth. We still, for the full year, after we saw cloud growth decelerate for many companies, not just JFrog, we still delivered more than 40% growth in the cloud. With all of these challenges, we delivered three of the largest wins in the history of JFrog. So this was the efforts that we've invested in over the past several years with our go-to-market efforts. And we brought in three of the largest deals, multi-year deals, multi-million dollar deals. So it was a significant win in terms of second half for us, and we're very pleased. Now, what did we learn? There were also learnings. We have to be patient.
As we move more upstream and we start to work more towards enterprise large deals, we need to be patient with those deals. Those deals will not happen overnight, and by waiting, the magnitude of those deals can become much larger. Secondly, we also have to think about how we guide, and these deals, because of the negotiation, the time to close, a rigid procurement environment like we saw during Q2, we have to de-risk those deals from our guidance and from our outlook, so we learned that as well. And we've taken that into our philosophy going forward.
Yeah, that's a very important call out. And so let's talk a little bit about the outlook before we get into the meat of the business. For the full year, you guided a 17% revenue growth, a similar growth rate for Q1 as well, which implies a similar level of growth throughout the year. So can you sort of outline for us the key assumptions with respect to the outlook in terms of what you're baking in for those large, large deals, migrations, the security uptake, and maybe the size of the renewal base? How should we, how should we think about the assumptions that underpin this year's outlook for a growth of 17%?
So first off, we only have real clear visibility in the first half. And this is what we're guiding to right now is what we see in the first half. There's a lot of unknowns, as I mentioned. Administration change, tariffs, no tariffs. How is it going to impact interest rates? So for us to make a decision around where we're going to be for the full year and be bold would not be prudent. That would be a mistake. So we're only guiding really based on what we know in the first half. Secondly, we saw what happened, the dark side of what happens when we had these large deals in our guide. And when you miss the magnitude of revenue that contributes from those deals could have a significant impact on the revenue that we deliver in that quarter.
Therefore, many of those deals, these are multi-year deals. They typically include a migration security component to them. And these are large enterprise deals, typically in the seven to eight figures. We have de-risked those deals from our guidance going forward. We also know that many of these deals, regardless of when we start negotiations in the sales process, tend to land towards the back half of the year. And this is what we're seeing. We de-risk them. We don't include them in our guidance. They're not part of the first half. If those deals were to mature and likely convert, it would be more towards the second half. And this is why you see this philosophy and the, what you're calling the flat 17% from first half to second half.
If there was to be an acceleration, we would start to see some of these large deals closing, maybe even cloud today, where we do not see usage over minimum commits, where there's a re-acceleration in the cloud. That could also impact, and much of that would happen towards the second half of the year.
Can I just add, Sanjit?
Yeah, please.
I apologize. Investors have been asking me, you know, well, is there a threshold? Is it $1 million? Is it $5 million? Is that what pulls it out of the pipeline? And I think just for clarification purposes, it's really more, as Ed discussed, the fact that it's a complex deal because security is being brought in. You know, look, some of those eight-figure TCV deals we closed in Q3 of last year were certainly not that size at the beginning of the year. So I don't think it's anything in terms of a dollar figure that we're looking at. It's more of the complexity of the deal.
Yeah, that makes, that makes perfect sense. I want to spend a decent amount of time talking about security, but just, I did have a follow-up on those three of the largest deals in JFrog history. Conceptually, does that become like a referenceable customer base? If you're signing like really, really large customers, their peers find out that they're using JFrog, is that turning into a sort of those guys sort of vouch for JFrog, maybe unlock larger deals or build that large deal pipeline, if you will?
We certainly believe that. Although we haven't given the customer names, we certainly talked about the industry. This is the automotive industry. It's the financials. It's the healthcare. And we believe that when you close these type of deals, the magnitude of these deals, especially when you're bringing security into that deal and a migration, we believe then that creates confidence, not only in our ability to close those deals, but confidence in JFrog to deliver. And many of those industries, I think, will start to look at those customers as a first stage of completion and start to look at opportunities with us with a similar construct.
And I know we'll get to it, Sanjit, but we also believe that the partnership with GitHub is something that demonstrates a standard practice, to the extent that we start to see that being deployed much more and talked about much more, that, as you noted, that the large enterprises are going to be working with these two organizations, then perhaps that becomes a standard that other organizations adopt as well.
Yeah, that's a great point, Jeff. So let's talk about security. I remember when we were doing the IPO back in 2020, we had this like offering around X-ray and Shlomi sort of framed out like, "Hey, this is a security capability." I had no idea the scale of the ambition that was to come on the, on the security side. And now we're starting to see some traction. So the big reveal in Q4 is there were new disclosures around the security business in which the team unveiled that security represents about 3% of revenue, 5% of ARR, 12% of RPO. To sort of level set, what offerings are included in the security revenue disclosure, and how often do you plan to update this metric?
So listen, we felt the same way. We thought when we did the IPO, and I've been here almost six years now at JFrog, so I was part of that IPO with Morgan Stanley, by the way, that led that. X-ray was what we thought a tool that we were creating for developers by developers because the conversation around security was never happening with the developer and the CIO or the CISO. Therefore, we thought, "All right, we'll create the tool and they'll take X-ray as a security tool." And we were very naive. This is why we did the acquisition with Vdoo. This is why over the last three years we've been investing in security. Now, what is included in that? We have JFrog Advanced Security and we have JFrog Curation. So the disclosures are primarily driven around those two products.
But in addition to that, we released Runtime in the second half of 2024. That is also included. So those are separate SKUs, separate add-ons, and it does not include X-ray, just to be clear.
Great.
Now.
Sorry, continue, please.
Yeah. So in terms of what you talked about in the disclosures, the three disclosures, and the reason why we thought this was important to highlight all three, one, we talked about delivering material revenue, and therefore, you know, giving the revenue number and the traction that we've done in revenue, 3% of revenue, even though we had a delay in the first half of 2024 because of decisions around taking a larger position and a multi-year position with JFrog, we still delivered very strong revenue. But we also wanted to highlight the fact that, from an ARR perspective, looking forward, we have 5% of our ARR. And more importantly, these are multi-year commitments to JFrog, 12% of our RPO.
So this is a commitment that's being made by very large enterprise customers on a multi-year basis to be with JFrog to replace point solutions.
Yeah, that was going to be my follow-up question. Can you give us a sense of the types or profile of customers that are taking on the security offerings of Advanced Security, Curation and who, if anybody, are you displacing?
So we talked about it on the public call. We have nearly 250 customers today that are on Advanced Security. So that excludes X-ray customers, Advanced Security customers. And if you were at SwampUp, you saw the list. These are enterprise customers. Now, some of them will take a smaller position with us at a base package, maybe introductory pricing. And then some we have very, very large commitments to JFrog, as I mentioned, multi-year commitments. But the vast majority of these customers are enterprise-type customers, which is important. Now, who are we displacing? We're displacing point solutions, what they consider best-of-breed point solutions. Many of these companies are private companies: Mend, Aqua, Snyk, Veracode, Black Duck. Those are, to name a few. But typically what happens and what you've seen is a long commitment to replace those point solutions over multiple years.
They may choose to replace one to two of those point solutions in year one, but ultimately the goal is to use JFrog, the Advanced Security platform, to replace all of those point solutions.
In terms of the scale of the ambition, how much do you think, how much of ARR do you think the security portfolio can represent on a sort of three- to five-year window?
So the intention is to continue to report on an annual basis, more on the revenue side, not necessarily on the ARR. But today, as I mentioned, we have 250 customers that are in Advanced Security. We have over 7,000 customers, so 7,300 customers. And we know that the vast majority of those customers already have security in their tech stack. So we know there's a budget for them. Half of those customers today are using X-ray. So we have what we believe a very long runway in terms of penetration of at least half of those customers today that we know today are using JFrog for X-ray for some bit of the security and will go and penetrate those customers first.
Yeah, that's a great way to frame it. Let's talk about the go-to-market motion behind, the security sale, which is always sort of complex. What is the process that the sales team is executing on to drive more of that security sales attach? It's probably links to the sales cycle because the deals are becoming more strategic. On the other side of that, what kind of uplift on deal sizes are you seeing when security is included?
So when we guide the team and our sales team and we build the targets, we look at it in a three-tier process. First are those customers that we have today that are using Advanced Security, and we can add incremental seats to that subscription. So we monetize based on the developer seats, so contributing developer. So we have, as I mentioned, 250 customers. Some of those are in minimum packages. Others have taken a long commitment, but we have an opportunity to expand those customers. That's number one. Number two are those customers that are currently using X-ray. So we have thousands of customers today that are using X-ray, and this creates a pipeline of opportunity for us and for our sales team to go and start the discussion around Advanced Security. Number three would be as a renewal happens in a lower subscription.
Security is only offered in our Enterprise X and Enterprise+ subscription. As a lower subscription is renewing, there's an opportunity to discuss not only an upsell to a higher subscription, but also bringing security into that discussion as well. Then lastly, on a magnitude of order, very low, is new customers that are coming in. There are some customers that come specifically for security, and we have the discussion. You are required to have Artifactory with our Advanced Security. Those customers that are coming in at a higher subscription level then will open the discussion around security as well. If you're coming in as a new customer to JFrog in Enterprise or Enterprise+ , we'll open the discussion around security as well.
And if I could just add to that, to what Ed had alluded to there, Sanjit, is the fact that I think that yourself and what other investors may start seeing, and I think this is going to be unique to how we have structured our go-to-market, which is the playbook still being written. We have a handful of deals that we've won today, but you're starting to see in the large global enterprises, the CIO and CISO budgets becoming one. And in some cases, the CIO is now the boss of the CISO. And why is that important? I think that's important in the fact that JFrog and our named account executive will always have that relationship with the CIO and will always be that face to that company. We use a strategy of security overlay when we're bringing in the security sale.
I think there's been a misconception that at some point we're going to have to ramp a huge security sales force in order to, to move the needle here. And I think that actually the industry is shifting in a way that's actually favorable to how we've implemented our go-to-market strategy.
That's a great point. It's always, I think that you're right. It's always the current concern is that if you're going into security, different buyer, different decision maker, how do you get the right skill sets in the sales force? And if you see a merging of the CIO and the CISO, it makes that a billionaire. It's a great point. Let's talk a little bit about Runtime Security. That's the newest addition to the security lineup. Why does it make sense for JFrog to enter the real-time vulnerability detection market coming from the DevSecOps world? And what's the strategy to drive adoption for JFrog at Runtime?
I'll start, Jeff, and if you have something to add there. First off, this was something that came to us by our customers. Our customers had asked us. They said, "At the end of the day, you own the asset. The binary is owned by JFrog. You're securing the software supply chain. The real point of when you're bearing fruit is in production. And the traceability to go from production back to the point of building, within the software supply chain is needed. As much as you can secure your software supply chain, there are times when you may have a vulnerability or some type of security breach that gets through into production. And because we own the asset, we want to have the end-to-end to be able to trace that back." And that's being asked by our customers.
So that was important, and this is why we addressed it. And we saw that there's an opportunity to want to address the pain. But number two, we don't want to leave necessarily money on the table. So what did we, what is the intention here? It's similar to what we do with our Advanced Security. It will be a separate SKU. We will charge for it, and we charge for it based on the developer, number of seats, contributing developer.
Yeah, no, I think Ed covered it. I think it just completes the circle for us, and it emphasizes how important metadata is from Runtime to the introduction or genesis of that code. So, the metadata and having that traceability when things do go sideways is really what's critical there.
And I'm going to just add one more thing that I forgot to add. Now, as much as we want to address the pain of the customer and we believe that this is the right thing to do, I don't know at this point yet, is it going to contribute like we saw in terms of Advanced Security and Curation? And that's still to be determined. It's still too soon. And we don't believe at this point that it's going to be a huge driver of revenue growth.
I think, Sanjit, as you know, I mean, right, getting someone to open up their production environment is an act of God sometimes.
Yeah, totally.
You know, there are people with agents out there, and we have things to offer, such as the metadata, and they have things to offer, such as agents. So maybe there's things that we can work on, with different partnerships within the industry.
Definitely, if you look at the Advanced Security part of the portfolio, I mean, that's definitely a more mature, established set of capabilities that buyers are well aware of and makes sense for the classic JFrog user community. Jeff, you mentioned you called out the GitHub partnership. Let's talk about that a little bit. What exactly does the GitHub partnership entail, and how has it impacted the business thus far, and what lies ahead in terms of the partnership going into 2025?
I'll start. Okay. So first off, first off, this was brought to us again by a pain from the customer. And so we're solving a pain for the customer. They came to JFrog, they came to GitHub, and they said, "Listen, at the end of the day, the two of you don't talk." So it solved two problems for us. Number one, it clearly defined the swim lanes: source code and binary, best of breed. 70% of our customers we know are using GitHub. Okay, so that's first. And now it's, it's a clear delineation between the two. Whereas maybe previously people had questioned, is there overlap? Do we do the same thing? Now it's, it's clearly defined who is managing source code and who is managing the binary. Number two is, this is a co-marketing, co-engineering agreement.
Now, what's important about this is also CEO- CEO led. So Shlomi, our CEO, and Thomas, the CEO of GitHub. In fact, the reason Shlomi's not here today is because we have our Leap event. He's in New York together with Thomas. They're presenting today, and then moving to Germany, flying to Germany to present to our top 50 customers around our roadmap in the code development that we're doing together with GitHub. So clearly, you know, there's value here that is being created between the two companies for our customers, and we believe that this will create opportunity from a security perspective. And why?
Because a curation can be used in order from a Copilot perspective to minimize what comes into your organization, but also now you have the traceability as a single pane of glass going from your binaries back to your source code with clear single pane of glass, easy traceability, and what will come out in this roadmap discussion is really around remediation, and that's the next step, so an important partnership together with GitHub. The question I'm sure is going to be asked, when do we get to a co-sell, so I will answer the co-sell because that's always a question that we get asked, obviously at some point we would love to have the opportunity to tap into Microsoft with the tens of thousands of sales reps that they have, but that's a different discussion. That's a discussion with Microsoft.
We're working together with GitHub, and we believe as we create value, there might be an opportunity to do a co-sell with Microsoft, but who knows when that will happen, but we're optimistic at some point we could see a co-sell.
But irrespective of a co-sell, Sanjit, I think as you and I have talked and I've talked with investors, given that 70% of our customers are already using GitHub for their source code, the opportunity is really, as Ed talked about, the security solution. And there was an opportunity in Q4 that had impact from the GitHub and JFrog partnership. And what Ed and I are looking to do as we move through 2025 is hopefully, as some of these deals close, be able to highlight that this deal was in fact driven by or had influence from the GitHub JFrog partnership on the security side. So, and as Ed has not talked about, I think curation is becoming very important because of the license function with Copilot and what could happen there with, you know, misuse of license with the integration of Copilot.
So I think that, as Ed noted, this partnership is more of a CEO- CEO partnership at this time, and there's more to come on the engineering front.
Yeah, that's exciting. Let's stay on the thread of partnerships for a couple of minutes. Let's talk about AWS. You signed a strategic collaboration agreement with AWS. It promises to help customers migrate workloads to the cloud and leverage its marketplace for seamless procurement. Can you elaborate on the ways that you think this partnership can translate to even better growth for JFrog?
Yeah, you know, let me talk about that real quickly, Sanjit. We had had a partnership, obviously, with all the cloud providers in their cloud marketplace. That was kind of our initial channel business that has been quite successful for us, quite successful in negotiating some of these large deals we closed in 2024. Thus, we've become a more important partner to AWS, being our largest cloud partner as it stands today. And we moved up tier into a new level. I would point you that others have had made press releases about this similar type of agreement within the infrastructure market. But what this does is it allows us to work with AWS in targeting co-customers where they're now willing to commit some resources.
And some of those resources are going to be in the form of discounts, given the size of commitment to the cloud that a customer makes on a migration process. So it helps us in that co-sell customers, we can certainly target them with AWS now. But again, it doesn't change our philosophy that it will be the customer's decision as to when they are ready to migrate.
Let's continue to stay on the partnership theme. I want to talk about JFrog ML because you guys made a recent announcement with Hugging Face. But before we get there, kind of some of the similar question on runtime security, why was it important for JFrog to enter the MLOps market where you're providing like model evaluation, model serving, experiment tracking capabilities? Why enter this, this part of the market? And then we can talk about, and maybe we can, give your perspective on the recently announced partnership with Hugging Face.
So I'll start with the why. Why would we do this? So we are, we learned, that many of our customers today are using Artifactory to store their large language models. And why? Because it's a binary. A model is a container, it's a binary, and who is the leader in terms of the binary management and storage? It's JFrog. So that was what we learned. Then what we saw was an opportunity to partner with companies like Hugging Face and SageMaker to bring from open source repositories, into JFrog and connect, to our platform. So that was what we did, in, I believe, the first half of 2024, announcing that. Now, we saw an opportunity to also, have discussions with the training of the models and going through the software supply chain and delivering those models as you learn and experiment and put those into production.
This is where the discussion with Qwak came into the fold. Number one is, we looked at it, we saw that this is a new budgetary line item. We think that there's huge potential, and we wanted to get in front of that wave quickly. We also know that valuations at the time were high, but could spike. We paid $230 million for that acquisition in at the end of Q2, beginning of Q3. Today, many of these companies are demanding $1 billion. So we wanted to get in front of that. That was the why of why we did that, and we think that this has an opportunity to be the next vertical of growth for JFrog. Okay, so from that perspective, it made a lot of sense for us to do it.
It seems like wherever binaries are being created, that's where JFrog wants to be and have a voice, in that market. Really interesting.
I jokingly say, Sanjit, that we've all talked about shift left in various aspects. This is the shift left of machines.
Yeah, understood. Yeah. Making machine learning and AI kind of a software delivery type process. Now, that makes a ton of sense. Let's spend a couple of minutes about the cloud business and just sort of market to market on the state of the cloud business. Cloud revenue reached $168 million, accounting for 39% of total revenue. As you mentioned, Ed, it grew 41% year over- year. If you decompose the growth that you saw last year from migrations, the month-to-month customer base, new logos, and organic expansions, what were sort of the trend lines if we kind of decompose that, that growth that we've seen in recent quarters?
Listen, the primary growth driver here is coming from the migration. A migration from self-hosted instance to cloud will generate anywhere from 20%-80% uplift. That's step one, is moving that customer from a self-hosted to a cloud subscription. Now, there's opportunity, of course, down the road to continue to grow as workloads grow and usage goes above commit. Today, that's not necessarily the case, but this is step one. We believe as we continue on this focus of migration, we're positioning ourselves well for when budgets start to open up and companies are allowed to spend more than just the minimum commits. The second step would be around expansion of those customers. In magnitude of order, then we see the expansion. As workloads are growing and commitments become larger, we see expansion in that.
Monthly customers are becoming less relevant. So we've taken proactive steps as part of our strategy to move many of those monthly customers to annual customers to kind of minimize the variability that we see on a month-to-month and quarter-to-quarter basis. So that percentage of revenue that's coming from our monthly customers that do not have commitments with JFrog has declined, again in 2024, and I would expect that to be the case in 2025. We are cloud-first strategy. So most of our customers today are now landing in the cloud, and that would be the last that we would see in terms of driving growth in the cloud is coming from those new customers.
Sanjit, maybe just a simple way that I talk to investors about that is that obviously our cloud NDR is higher than the corporate, and you can kind of do the math, and you can make an assumption of what percentage of that is from migration. What's really left then is a fairly strong renewal growth rate, that you can imply.
Great. Just as a follow-up to the point that you just made around the 20%-80% uplift, what drives that 20%-80%? What are some of the factors that are allowing customers to spend more with JFrog?
Yeah. So when you migrate from self-hosted to cloud, you're obviously taking more with JFrog because we're now managing the cloud for you. But typically what we see with that range from 20%-80%, it's the size of the workload that they're moving from their self-hosted instance to the cloud. Additionally, they may have multiple servers. So we monetize and self-host it on servers, and utilization across those servers may not always be at 100%. But when you have a global organization that's using across multiple territories and regions, geographies, we typically see a higher migration uplift on those.
Think about it like this, Sanjit. If I'm, to Ed's point, if I'm running a server and self-hosted at 20% and crank it to 80%, JFrog sees nothing. But if I move to the cloud, that entire monetization is captured immediately.
Yeah. That's a great point. And then probably a key factor when we think about growth going forward. Let's talk about the theme about moving up market. I would say the vast majority of my coverage in the last two years has talked about this. They see the enterprise opportunity, frankly, because that's where the enterprise is still underpenetrated in cloud. So I want to talk a little bit about JFrog's own journey there. How do you balance the increasing focus on large enterprise customers while maintaining a healthy mix of these smaller tech startup customers? In a sense, you want to have exposure to them because they tell you where the puck is going. And so that gives you that signal back into your product engineering group.
So, you know, the move-up market, and then while trying to, you know, keep a pulse on where the puck is going, how does the team think through that?
So we were founded off of a developer selling directly to the developer on an inbound. So we have the team, we have the know-how to do that, and we continue to operate with an inbound motion and teams that are focused on driving that inbound motion. So the investment over the last three years, plus that you talk about and the theme that you were discussing around the go-to-market has been made, excuse me, over the last three years. And the focus has really been around the investment from those activities. But the fact of the matter is we had to learn and we're continuing to learn. The impact of that was definitely seen in the second half of 2024 where we landed many of these large deals. But the focus in 2024 strategically was around landing these large customers, in particular penetrating in security multi-year deals.
But it doesn't mean that we're ignoring the mid and the SMB. We have the know-how to do that and we continue to invest in those areas. But where we see the money right now is with these large strategic deals and those customers that are interested in investing in software infrastructure and modernization of the software infrastructure.
Yeah. W e're putting money to work in 2025 for future opportunities. This is not a 2025 type of opportunity. But I think, as you noted, Sanjit, what we would like to see is maybe it's through the GitHub relationship, maybe it's some other methodology, maybe it's somewhere down the road we come out with a lack of a better name, an Artifactory Lite to start that engagement with the customer earlier on and saying, "Hey, you know, we understand here's JFrog. It's probably overkill for you today. Go to Sonatype, go to another competitor. When you get to the big boy status, you'll come to JFrog." I think that we would like to start that engagement a little bit earlier down the stream.
Makes sense. It actually leads into my next question around investments and margins, actual CFO questions now. So there was a significant amount of operating margin expansion in calendar 2023, over a thousand basis points, more modest expansion in 2024, and the initial outlook calls for generally flat margins in 2025 as you drive investments in your go-to-market organization. Can you talk to the early success you're seeing from these investments and the confidence that it gives you to continuing along this investment path?
So we're seeing a lot of momentum right now in security, and we also see ML. We made a pretty bold move in terms of the acquisition in the second half of 2024. We do not want to slow that down. And that's part of the reason why you see, in terms of the investments that are being made that we called out specifically in 2025, is to maintain that motion, and that momentum. Now, the investment in security has been made over the last three years, and you saw the results three years ago where we were essentially flat, and now we're starting to see the margin expansion. We will invest in ML. That's part of what we want to do, and we believe that that's going to be a significant growth driver for JFrog in the future.
Now, the other thing to point out is that the guide is conservative, and if we overachieve on the top line, my expectation is that that would start to trickle down to the bottom line. Part of the DNA of who we are, we're very efficient. We're from an operational perspective, we manage the business quite tight and making sure that we deliver profitable growth.
I would just note to Ed's point, it's conservative, is what I say. I mean, you know, look, I can't come to you, Sanjit, and say we've been conservative on the top line, but hey, let's let it roll on the EBIT margin line, right? I think you've also seen that over the last few years that not all our ambitions in spending initiatives may come to fruition in a year. And to Ed's point, I've been using a great new operating metric called incremental operating margin. And that's essentially to Ed's comment that, you know, dollars over the guidance that we provide should in fact see, you know, a higher contribution down to the EBIT one.
Let's wrap up on kind of the long-term model. Kind of analyst day, well, more than I think it was 2023, where you laid out some initial targets around $800 million in the revenue, 80% gross margins, 21%-23% operating margins, 26%-29% free cash flow margins. You know, if you look at where we stand today on a lot of these metrics, you're kind of right there. How relevant is the long-term model as you stand today both on like the revenue side as well as the sort of profitabilities and free cash flow side of the equation?
Yeah. I'll try and wrap it quick because I know we're up against time and there's a lot to unpack here. But the bottom line is this. I look at it from two perspectives. What have we done since we delivered the long-term model? And as you just rolled through, we're on track. Revenue, we're on track in terms of our growth. Operating margins, we're on track. Gross margin, we're on track. Free cash flow, we almost hit, for the full year, the number. So when I look at this, I feel confident that we're on track. Now, going forward, there's a lot of uncertainty, obviously, in 2025, and the visibility that we have is really in the first half. We'll see what ends up happening in 2025, you know, that's out of our control.
What's in our control is how we spend, when we spend, what we deliver in terms of our operating margin and our free cash flow margin. We'll see. We'll come back in the second half of 2025 and see if it's still relevant or not, and we'll provide updates.
Yeah, I think we're looking to hopefully provide an update in the second half, Sanjit. And at that point, we'll obviously only have a small delta in terms of what's left for that. And we'll have to see where things shake out for this year at that time.
Great. With that, we're out of time. Thank you so much, Jeff and Ed, for giving an update on the JFrog story. We really appreciate it.
Thank you for having us.