Oatfin Under The Hood - Part IV
Thanks again for subscribing to Cloud Musings! This week, we talked to a number of investors and potential enterprise partners. As always, I would love introductions to investors and enterprise partners who are excited about the cloud and developer tools space.
In this edition, the goal is to continue to de-mystify what Oatfin does under the hood. In part 1, I talked about the steps that happen when a user clicks the deploy now button. In part 2, I talked about managing cloud credentials among developers. In part 3, I talked about the cloning of an environment feature with code.
This week, I started researching how we can leverage AI in our app. In early 2022, we did a program with Google Black+TechAmplify and learned a lot about Google's DeepMind, but I felt we were too early.
Something I envision is instead of having to choose the parameters to create an infrastructure, you can simply describe it and the app will do it! This is still very early and just prototyping it.
For example, a user would type:
"Create an API on AWS with the name Oatfin using docker ecs"
It's a matter of parsing the natural language into a list of inputs that we can then feed into the API or function that creates the infrastructure.
{
"application_type": "API",
"application_name": "Oatfin",
"cloud": "AWS",
"infrastructure": "ECS"
}
Thanks for reading!
Jay