I fell in love with programming with Logo and BASIC in grade school. In college, it was when I studied hardware, compilers, and programming tools that I realized I wanted to devote my career to making it easier for people to create software. This led me to pursue a PhD at MIT, where I worked first on software correctness and then on designing programming models where correctness is built-in. By the time I started Akita, I was a tenure-track professor at Carnegie Mellon University.
During the time that I was in academia, the world had moved towards more services and more APIs. The kinds of application-level tooling I had been working on described a smaller and smaller part of the whole picture. At the same time, there were a growing number of companies in the observability space, working on making it easier to understand these systems as a whole. I saw that I was uniquely positioned to fill gaps in the observability space, using my experience in programming languages research. This led me to take a leave from CMU, sell my furniture, and drive across the country to start Akita.
Since then, I’ve been working with a small team to build the future of API observability. We’re excited about one day being able to use Akita to watch interactions with any API, get back a summary of what happened (what data formats were sent where; how the API was called), and be able to track these interactions over time. We are super grateful to our investors, advisors, and beta users for believing in the dream!