Bryan Cantrill

I mean, I feel like that's never a lower concern.

That is like, I am just like- Then the B. I think the B was like, okay, we got a brace for storminess.

Yeah, yeah, brace, yeah.

And sure, maybe it was a hangover of that same fear of storminess, but I think like it was A consideration, not D consideration.

I just think the dot-com bust

Yeah.

I think the... But, you know, one of the bigger reasons, provided that it kind of made sense from a terms perspective, was...

we were no longer in this experimental phase with large enterprise customers.

Right.

And, and I think kind of like you saw in the, you know, kind of 2010, 2011, 2012, as folks had begun, like trying public cloud and then being, you know, starting to determine like, this is actually a substrate that I could depend on more.

And then that,

And then what does this mean if I'm going to actually start adopting this?

Like what's the longevity of service or how do I think about it architecturally?

We had started getting to phases with customers where they were not thinking about like, okay, well, what if we quadruple the size of our pilot?

And we're really starting to ask questions of like, what are the next 36 months, 48 months, 60 months look like?

going from a more traditional substrate that we have been running on for the last 10 years to one that is much more modern and cloud first.

And, oh, wait a minute, that all rides on top of oxide.

And how do we have the conviction and know that they are going to be here in not just three years, but five years, seven years, 10 years.

And so, I mean, put simply one big benefit of raising is,

is to give our customers and future customers the confidence that we are going to be here for a very, very, very long time.