The product
The people who design an interface are the people who answer for it a year later. That is what makes a shortcut cost something at the moment it is taken.
Twenty-three years of engineering, thirteen of them spent operating our own software. This is where that came from and what stays with the team after a launch.
AKOVANA is an independent European technology company. It began in 2003 as a small group of developers in Kharkiv, building web software for other people’s products.
In 2013 that group shipped something of its own. MyOwnConference launched as a webinar platform, and from that day the servers, the incidents, the support load and the cost of acquiring a customer all became the company’s own problem rather than a client’s.
The company was registered in Lithuania as AKOVANA, UAB in 2012 and works from Vilnius and Kharkiv. Four more products have followed the first, and the practice they are built on is the one that started two decades earlier.
Three of them were decisions and two were not. The ones that were not are the ones that shaped how the company operates, and the last is simply where all of it leaves us today.
A small group of developers came together in Kharkiv and started building web software. The engineering practice the company runs on today is the one that formed here.
AKOVANA, UAB was entered in the Lithuanian Register of Legal Entities. That gave the practice a European base to operate from and a legal identity that has not changed since.
MyOwnConference launched as a webinar platform. From that point the company was no longer only building software, it was running it.
The pandemic moved meetings, classes and conferences into the browser. Capacity had to follow in weeks rather than in planning cycles.
The war in Ukraine forced the company to streamline how it operates and to redesign the product around what people actually use.
Signal latency is under one second, a next-generation dashboard is in development, and every product the company sells runs on machines it administers itself.
The usual arrangement ends at delivery. Ours does not, because the same team is still holding the thing years later.
The people who design an interface are the people who answer for it a year later. That is what makes a shortcut cost something at the moment it is taken.
Servers, monitoring and incident response stay in house. An outage is the team’s own night rather than a ticket sitting in a vendor’s queue.
Search, paid acquisition and analytics sit with the same team, so what the product does and what the campaign promises cannot quietly drift apart.
Tell us what the system has to do and where it has to hold. You get an engineering answer, not a sales deck.
contact@akovana.com