People ask us occasionally why we are building a deep storage infrastructure company from Tallinn. The implicit comparison is usually to a cluster of better-funded competitors based in the Bay Area or Berlin. The question is fair. This post is our answer, written from the perspective of engineers who chose this location deliberately rather than by default.
Leil Storage was founded in 2023. We are building distributed filesystem software for high-density SMR drives, aimed at AI training infrastructure teams who need petascale storage at disk prices. The technical product decisions and the company location decisions are less independent than they might appear.
Estonia as an Operational Context for Deep Storage
Estonia's climate is relevant to storage infrastructure in a direct, physical way. Tallinn averages around 6 degrees Celsius annually, with winter temperatures frequently below minus 10. Data centers in this environment run cooling systems at a fraction of the energy cost of equivalent facilities in warmer climates. For a company building software that runs on power-intensive storage hardware, proximity to low-cost, low-carbon data center capacity is a concrete operational advantage.
This is not just about our own infrastructure costs. It is about the customers we expect to work with. European AI training teams facing energy cost pressure and EU AI Act compliance requirements are increasingly looking at Nordic and Baltic data centers as the right venue for large training runs. Being based in Tallinn means being local to that infrastructure cluster, able to meet with data center operators, help customers evaluate colocation options, and respond quickly when something needs hands-on attention.
We are not claiming Tallinn is better for every technology company. We are saying it is a reasonable choice for a company building software for the infrastructure layer of compute-intensive AI workloads, where the physical environment of the compute cluster matters.
Engineering Culture and the Estonian Tech Ecosystem
Estonia's software engineering community is smaller than London or Berlin but more concentrated in systems-level work than the ecosystem mix in larger cities. Skype's technical infrastructure work, the deep pool of network and distributed systems expertise that came out of the Tallinn University of Technology, and a government digital infrastructure that has run on distributed systems principles for two decades: these created a local talent pool skewed toward exactly the kind of work Leil does.
The founders of Leil (Alexander Ragel and Raimo Lepp) met through the Tallinn tech community and share a background in distributed storage systems and kernel-level I/O work. The team we are building reflects the same technical profile: filesystem internals, block device drivers, distributed consensus protocols. These are not common specializations, and finding people with relevant experience in a smaller city is harder than in a larger one. The Estonian context makes it less hard than it would otherwise be.
Hiring in Tallinn is also honest about what we are. We are a small team building infrastructure software. People who join us are not joining a company that is pretending to be larger or further along than it is. That honesty is easier to maintain when the local ecosystem is not structured around the signaling games of later-stage fundraising culture.
EU Regulatory Clarity for Infrastructure Software
Distributing software that handles AI training data to European customers requires navigating GDPR, the EU AI Act, and data residency requirements that are evolving rapidly. Being an EU entity, operating under Estonian and EU law, simplifies a significant amount of this for our early customers.
Our software handles training datasets and model checkpoints, not personal data in the GDPR sense. But many of our prospective customers are using training data that includes EU residents' information and are subject to data residency requirements that effectively mandate EU-hosted infrastructure. An Estonian entity with EU legal structure is not an impediment to those contracts; a US entity often is.
The EU AI Act's requirements on high-risk AI systems include traceability and documentation requirements for training data infrastructure. We are building Leil with those requirements in mind, not as a retrofit. Being based in the EU and following EU regulatory discussions closely is an advantage in this respect. We hear about proposed requirements early and can design for compliance rather than discover a compliance gap after the fact.
Cost Structure and Operating Pace
Building deep tech infrastructure software takes longer than building SaaS applications. The development cycles for filesystem internals, kernel-level I/O scheduling, and distributed consensus protocols are measured in months per feature, not weeks per sprint. Sustaining that pace requires a cost structure that allows a small team to operate for extended periods without revenue pressure forcing premature pivots.
Tallinn's cost of operations is meaningfully lower than the Bay Area or London. Engineering salaries for the profile of people we hire are lower in absolute terms (though competitive by local standards). Office space costs are lower. Infrastructure hosting costs are lower. These are not the primary reasons for our location, but they are an honest part of the calculation for a team building on angel funding and planning to reach the point where the product speaks for itself before raising further capital.
We are conscious that operating cost advantages can become a rationalization for avoiding hard choices. Being in a lower-cost environment does not mean we can avoid hiring the best available people for the specific technical work we are doing. Cost efficiency is a constraint that enables longer runway, not a substitute for engineering quality.
What We Are Not Claiming
We are not claiming Tallinn is the optimal location for every infrastructure company. Access to the largest pools of capital, the densest networks of AI research institutions, and the highest concentration of potential enterprise customers are all in other places. If we were building a product that required constant proximity to hyperscaler engineering teams or US enterprise procurement cycles, being in Tallinn would create real friction.
We are also not claiming that Estonia's digital government reputation is directly relevant to what we build. The government's use of distributed systems for public services is a frequently cited differentiator for Estonian tech companies, and it is a real cultural signal about how software infrastructure is viewed here. But our product is filesystem software for AI training clusters, not a government services platform. The correlation is indirect.
What we are claiming is that the combination of factors described above adds up to a reasonable answer to "why Tallinn" for this specific company building this specific product. Cold climate, relevant engineering talent concentration, EU regulatory position, honest cost structure, and proximity to the Northern European data center infrastructure where our target customers are increasingly running their training workloads. Taken together, these are not coincidences or rationalizations. They are the conditions that made Leil a Tallinn company rather than a company somewhere else.
We founded Leil in November 2023. We are still in the early stages of building the product and establishing our first customer relationships. The location question will eventually be less interesting than the technical and commercial questions, which is how it should be.