Reducing Management Overhead with DevOps – Arul Jegadish Francis, OpsVerse

This is Textron TV. Hey guys. Thanks for the throw.

We're here with the rule jaggedish who is co-founder for Ops first. They are provided with a managed devops platform and we're gonna be talking about the transition to these managed platforms because we've been spending the last decade or more just building out these platforms ourselves in a lot of cases and perhaps. There's a better way of thinking about this a real welcome to the show.

Thanks, Mike. Thanks for having me on the show. So you guys essentially have taken a set of Open Source tools curated them on behalf of people and created that integration.

So basically all the heavy lifting that goes with devops is now you guys have you seen an uptick in that kind of approach or more people inclined to go that route then go roll their own and if so, what's driving that Yeah, yeah. So upsource provides manage devops tools platform. And we definitely see an Arctic in companies using open source tools to take care of their devops needs and as the complexity of managing these tools have gone up with the cloud native and public Cloud adoption.

We see an uptick in customers looking for managed services for devops, too. So we're definitely seeing that that Traction in the market. Are they smaller companies or larger Enterprises or have you seen patterns in the types of companies that are more willing and more inclined to go into manage devops platform.

We actually see this trend across the board. There are smaller companies where they don't want to invest the engineering effort to like bring out all these tools. They want to they want to one click platform where their Engineers can form their core engineering problems their Core Business problems, and we are seeing bigger companies where they are unable to handle the scale.

Like for example, telementary data has increasing the scale of telemetry the volume of Elementary is increasing and they are they're finding it very hard to manage the scale. And hence. They need platforms where all these all these tools are available out of the box an example is elastic search is a classic example, but it's easy to get an elasticsearch cluster up and running but beyond a scale you need like dedicated Engineers.

Just managing your last six for Management so in those cases companies are increasingly looking for out-of-the-box Solutions. And to your point it seems like we're trying to pull more of the Telemetry data and the metadata out of these tools and that's hard to do if you're managing on your own. So how do you perceive that manage devops is going to evolve what kind of insights might I get from an observability perspective that I don't get today.

I mean there's more to it than just, you know, lifting and shifting responsibility for the platform. I understand. Yeah, so so yeah, I mean these are valid points the approach we are taking is we are operationalizing in open source tools which are built on top of Open Standards, which means which means for an existing customer for a customer who's already using some of these tools.

It's all these Integrations are already available. So it's very easy to make that suits to to manage manage provider. What's the challenge in getting people to wrap their brains around this and are you seeing new customers kind of drive to this or people swapping out their existing devops platforms to go to this more managed service approach?

So we we see both so we see some green field environments where where they are trying to formalize their devops tool chain as well as we see customers who who have gone like one or two iterations trying to build this on their own and as they hit the shoulder scale they want somebody else to manage it for them. They want out of the box solution. So we see we see both kind of adoption in the market right now.

Um, another another driving factor that we see is the ability to manage multiple troops. So if you look at a software delivery pipeline, there are definitely multiple tools involved and customers find it hard to integrate and manage these multiple tools. So there is so people increasingly look for an integrated solution an end to end platform where some of these Integrations are already walked out for them.

And courses a lot of folks who have resisted opinionated Platforms in the past because they think that they want to add a new tool here and they want that flexibility. Is there a way to extend the platform add my own tools if I feel so compelled or how do I get after that? Yeah, I think that's that's an very important important aspect of any devops platform because the tools landscape will change very fast.

It has been changing and building very fast. So you should be able to bring in a new tool into the platform fairly easily. And the way upsource has brought out the platform.

It's very Plug and Play So prospective customer can select what tools they want from our platform and they can very easily incorporate their rest of the ecosystem of tools into the platform and to be very specific here. We are offering a unified interface layer. We call it as an IDP internal developer platform with the idea.

They can bring out those and other tools into one interface. So so it's very very pluggable. Um, it's not a very opinionated platform.

It's very easy for customers to put together their tools. When you have that whole approach. Where does that reside does it sit in the cloud somewhere?

And what cloud or can I pick the cloud or how does that work? Yeah, so we offer it in two flavors soon as a traditional sass player where customers can just run these tools and obso US framework will run it in our Cloud. So it's just a cloud-based SAS offering.

We also offer it as private SAS. This is the model that we are pioneering where we can orchestrate and run these tools within a customer's Network. So so all the customers data lives within their network, but also framework takes care of managing these tools and taking care of like day two operations for the tubes.

So this is also a general Trend. We see with respect to devops tools because devops tools need to talk to your like source code repository. Yeah, most of the tools will need access to your production systems.

So in those cases, it's very it's not very optimal to have a cloud provider have access to your production systems. It's better to have these tools run within your network under your control under your governance and with our private SAS framework. We are able to that I mean people are figuring out that perhaps my core intellectual property shouldn't leave the four walls of the building.

Is that kind of the idea? But then why AWS account or a public cloud account? There's no point in like sending your Telemetry and other data to a cloud vendor who's also running in the same age of us right here under their account.

So so why not have everything within my cloud within my AWS account under my data governance? This next for you guys. Where do you go from here?

I mean, you've got the platform up and running. What as you look at into 2023. What's on your mind?

IDP solution that I described Is fairly new even from us that's a fairly new offering. So we will be doubling down on our IDP offering and and ensure that the IDP becomes sort of the single pane of glass for any software organization to do anything with their software delivery pipeline. So you can expect to see a lot of developments both from us and from the industry on the IDP on the IDP layer.

So it's a it's a it's a new thing that the industries are opting. A lot of a lot of organizations are beginning to realize the need to have a good idea. So you can expect to see a lot of updates from us on the on the ID side of things.

How much is the devops platform itself becomes something of a bottleneck in organizations? We kind of hear the phrase Jenkins Stein which is you know, all these extensions and all these Integrations. Have we got to the point where we're spending more time managing the platform than we are writing code.

Yeah, I mean that that's sort of the reality today what we've seen the industry is typical engineer needs about 15 or more tools to do their day-to-day tasks, which means now you every organization needs a platform where there are like 15 different tools that are that are interacting. So this platform if it's not the loyal and not manage correctly become so single biggest bottle neck for a software organization and that's where platforms like obsource helps to ensure organization can focus on their Core Business and this pipeline is solved and taken care of them. All right, folks.

You heard it here the tools maybe get in the way of a productivity. Hey, I really thanks for being on the show and best of luck. Yeah, thank you.

Thanks for having me here. All right guys back to you in the studio.