>> Hi everyone and welcome back to Tech Exceptions.
Today, we have a special guest, Casey O'mara.
Casey O'mara is the Head of Business Development for JFrog.
JFrog is the leading startup in the DevOps world.
Hi Casey.
>> Hi Adi. How are you doing?
>> I'm good. How are you doing?
>> Great.
>> Jfrog?
>> Yeah, JFrog. It's an amazing DevOps company.
We started 12 years ago in the open source community,
and it's been growing strong ever since.
Obviously, we started the DevOps revolution
and here we are 12 years later,
leading the package management space and the delivery of DevOps.
>> That's interesting.
Ten years ago or even today,
people are still saying, "Hey,
I want to do open source,
and I want to turn my open source into a business."
But they really struggle with putting together
this strategy of how they can make profit,
how they can work on a revenue stream,
especially when everything is free in open source.
It seems like JFrog definitely nailed it and know
how to do open source and how to build a business with Alphabet.
I remember something around
Liquid Software vision that JFrog really known for.
What is Liquid Software vision?
>> We started 12 years ago with the open source community,
and we really focused on the pain point of packaging
software and delivering it to customers.
The founders really had this deep vision of Liquid Software.
What Liquid Software really meant
was the ability to package something up and deliver it.
If you think about it, like water to your house,
you don't think about how the water gets there,
but you can go to your faucet,
your sink, your tub, you're outside,
your shower and you turn on
the faucet and the water is always there.
It's always flowing no matter where you
are in your house. It's not dripping out.
It's not pouring out. It's not dirty, it's clean.
It's free of any kind of impurities that you might have.
It not only serves you, but it serves
your entire community and all the houses around you.
When you think about this software vision
of software just flowing,
you can use this metaphor for how we deliver it to you today.
No matter what vertical,
whether it's health care,
whether it's your banking, whether it's automotive,
any of the verticals that we
serve that the software should always be there,
it should always be up to date, it should always be clean.
This is really the vision that fueled JFrog and fueled us over
this past decade where we've really focused
on how we deliver that value
to our community and to our customers.
>> I really like this analogy of flowing water.
You have energy, and electricity, and water, and everything.
It's the basic, it's the core of running a house.
For me, from what I understand,
it's the core of building software, right?
>> Exactly. Well, if you think
about building the core of software.
Anytime you get a new device,
so think about what you do.
You get this new device.
You plug it in, you charge it up, you power it on.
What's the first thing it typically asks you to do?
It asks you to update the software.
This is something that's key and fundamental.
If you think through all the things that power your life.
Software is really eating the world.
You look at that first software update
and making sure that you can
trust that software and that you have
all of the things you need to be able to utilize it.
That update is the first part of things that you do.
In some cases, take your automobile,
let's say you've got a vehicle,
you need to make sure that
the latest safety software is up to date.
It could even be a matter of life and
death to make sure that you have the software updates,
or if you're in the airline business,
you may want to make sure that your software there
is up to date and you have the latest fixes.
Updates really matter in this new world.
>> Absolutely. You want to update
often and you want to update fast.
Twelve years is a long time to
have an understanding of how software evolves.
How do you see what we used to have
12 years ago and all the way till what we have now?
>> Well, I think what you've seen over time
is just that the software is eating the world.
When you look back a decade ago,
you didn't have as many things that were powered by software.
What you've seen over that time is more and more things,
from your refrigerator, to your coffee maker, to your vehicles,
everything now is powered by software,
and so you need
a quick and easy efficient way to update that software,
no matter what language you're using,
no matter what package type.
This is where the universality of
JFrog really comes into play because what we
focused on is making sure no matter what
you use across the 26 different package types we have,
whether you're on-prem, whether you're hybrid,
whether you're in the Cloud,
that we're focused on making sure that you can
update the software that runs your life.
>> Absolutely. Software runs our life.
Software change the way we deal,
especially now with COVID and resilience.
We definitely see a high growth
in people building software and using
software for their day to day
tasks in business and in their personal lives.
Definitely the right area and domain to be at.
How do you work within the community?
There's the DevOps community,
and then there's the developers community.
Is there a specific area that you focus on?
>> I would say JFrog focuses on community first,
even in the core of our company.
When you talk to anybody, when you look at our codecs,
when you look at what we focus on,
community and customer happiness
are at the core of what JFrog does.
Even back 12 years ago,
it started with community.
It started with people that had an idea
of how software should be developed,
how it should be deployed.
The community and customers have been
a key part of giving us that feedback and letting
us know what they need and
how they want to deploy and how we can help make it better.
I think if you don't have that strong community bond,
if you don't have the community behind you,
you wouldn't be successful and you wouldn't
be where JFrog is today without them.
>> Absolutely. I definitely see it as well from our side,
community first and customer first.
Thinking forward, looking into the future,
how do you see JFrog progress and continue to enable
developers and DevOps folks to build
the best software and deliver the best software that they can?
>> This is a great question.
I think from JFrog standpoint,
we really look at how we become the universal DevOps tool.
What that really means is more than just words.
It's making sure that you're plugged in with all of
the other partnerships and
all the other companies that are out there that are doing DevOps,
and making sure that you have
the universality of choice between what you do.
Whether it's the fact that
you're plugging in with some kind of infrastructure tool,
whether you're plugging with Azure Cloud,
whether you're using your ID with, say,
VS Code or with Azure DevOps,
it's making sure that you have the ability
to connect with all of those tools and make it
seamless as you're deploying
your DevOps pipelines and as you're pushing to production.
I think from our standpoint,
we want to make sure that
no matter what you choose or what you integrate
with over 100 partners or
over 54 different integrations that we have,
that you have the choice and
the ability to just plug in what you use
today and be able to seamlessly and quickly release to production.
>> Yeah. Also security. I know.
>> Yeah. Security is a big part of where we're going and
shift left is definitely a part of our philosophy,
and looking at DevSecOps,
I think there's a lot of different tools out there,
but if you center on package management,
and use that as your focal point
for not only for container scanning,
but also for your open source scanning.
We're the only one that has it in your package manager where you
can scan both of these and have them right out of the box.
So if you're centralizing all of your development code,
you have all your packages,
all your binaries there,
and we can scan those,
and deploy those effectively with X-ray.
>> That's cool. I recently learned about X-ray,
and I'm always amazed by all the good stuff
that you are producing in JFrog.
I know you also gave a lot of things back to the community, right?
What is the latest thing that you can share with us?
>> We do. We have a couple of things.
I'll mentioned the latest one we did,
but we definitely give back to the community.
We've had JFrog Container Registry, we have Conan,
which is our C/C++ package management,
which you can go out there and get off our open source,
we also have a full OSS version of Artifactory as well.
But the latest one we do is we do a lot
of our centers back to the community.
Whether that's GoCenter, whether that's JCenter,
whether that's our latest one
which is going to be our ChartCenter,
which is about Helm.
We can definitely give
you-all of the ability of
our centers to give back to the community,
and allow you to use those as your public repos as well.
>> What are the centers mean?
>> We take GoCenter. It's really a place where you
can have your Go binaries. Be a part of that.
We scan those as part of delivering your binaries to that,
and then as developers,
you can connect to the GoCenter.
You connect to ChartCenter,
and use the charts out of there,
and know what's happening with those.
You can also get the X-ray
security information out of those as well.
It's one of the features and benefits that we give back
to the community that contribute to that.
>> From a developer point of view or the DevOps point of view,
I can leverage your centers and
take binaries that was already scanned,
and trusted, and deploy them with my code?
>> Yeah. You can pull those down from the Centers,
and use those in your code. That is correct.
>> This is really awesome.
I really like that idea.
It's a lot of giving back to the community that you do.
>> It is. Some people might not
realize that we're connected with things like Bintray,
and one of the things that I use a lot
as a developer is also a Homebrew,
and Homebrew, a lot of that is backed by Bintray.
There's a lot of ways that we connect and work with the community,
and package up different softwares and deliver on a minute.
It's really amazing that community can actually have,
and the bond we have with developers,
and we want them to be able to trust those binaries and use them,
and have an easy,
and consolidated way to do this.
>> Can you walk me through how do you
connect with Homebrew and Bintray,
and all the way to the developer that
actually use Homebrew in their terminal?
>> If you look at Homebrew today,
and you go up there,
and you do like a brew install,
or maybe do a cask install.
What you'll see in some of those bottles is the fact that on
the back-end it's using Bintray and of course
it has Cloudfront in there as well, that there to using.
But Bintray really backs where all those bottles and casks,
and other things that are behind there
that you install on your machines today.
It's the backbone if you want to think about it
that way of what Homebrew is doing.
>> Basically all the packages that I want to download.
Is actually going through JFrog infrastructure?
>> In some cases, yeah, and that's what you may
not realize is that JFrog,
a lot of the updates and a lot of the software that you
do today across a lot of verticals.
Eight out of the top 10 banks utilized us.
If you look at automotive,
we have a lot of the top automotive makers,
and when you look at health care,
and you look across a broad swath of verticals,
when you're updating your software,
you may not realize that you are using JFrog Artifactory,
like you may use Twitter, like
our Twitter handles are here right now.
Twitter uses us on the backend to update Twitter, or Facebook,
and a number of different software companies that uses for
their software updates that powers
a lot of the things that you do in your life today.
>> So you're holding a lot of data?
>> We're holding a lot of packages.
A lot of our thing is really that ben-ops kind of shift.
Today we have a lot of Get-Ops where
you're going from your Git repository out.
But what we think about is from ben-ops,
so from your binaries to your operations,
and how do we quickly get those out to production?
Abi Cavalli, a former Microsoftee as well.
Also talks a lot about the ben-ops and how we do it.
He spoke about that at our last swamp up,
and talked about what he's doing in
pipelines with JFrog to make this easier,
and to make it simpler,
and to have those native steps that just plug
in with things like GitHub, with Bitbucket,
and with other source repositories to make it
easier to operate on a Pin-Ups type operation.
>> That's cool. That's really cool.
I know you also do a lot of integration,
and lot of work with Microsoft.
Do you want to share us a bit about the integration,
the work that you deal with Microsoft services?
>> Yes. We integrate with a lot of Microsoft services right out of
the box from connecting with Azure DevOps,
and having the ability to natively use
our YAML pipelines with Azure DevOps.
We also connect with Visual Studio Code.
We have a plug-in with our X-ray that we talked about earlier,
that you can get the feedback right into
Visual Studio Code on those vulnerabilities,
and other things right in the IDE.
So the developer doesn't even have to leave where he's at.
The other thing that we integrate with our GitHub integrations.
So we have not only the ability to bring those into our pipelines,
but we also connect via CLI to the GitHub Actions v1 and v2.
So we have some great integrations there.
We integrate with Azure AKS,
and then we also have some Azure ARM templates that are out there,
and other things on the marketplace that
can connect you with pipelines, etc.
Lot of great Microsoft connections,
a lot of great tools,
and things that you can utilize today that are available.
>> The tight, tight relationship that cross
different domains and areas, and functionalities?
>> It does.
>> All right. Casey, thank you so much for being
here today and sharing all your knowledge with our audience.
>> Thank you Adi for having us.
Again, really happy to be a part of the Microsoft family,
and to be a part of your ecosystem, we appreciate it.