How we're structured
Codelight is an engineering unit within Avalanche Laboratory, operating from Tallinn as Codelight OÜ. We are deliberately small: a handful of senior engineers, one delivery lead, no account layer between you and the people writing the code. When you talk to Codelight, you talk to someone who can open the repository.
Senior-led delivery
Every engagement is led and staffed by senior engineers — people measured in years of production ownership, not project counts. We don't run a pyramid: there are no juniors learning on your codebase, and the person who scopes the work is the person accountable for shipping it. Modern tooling, including AI-assisted development, is part of our stack the same way an IDE is — but nothing reaches your repository that the engineer responsible doesn't understand line by line.
Delivery lead
Henri Parkja leads delivery and client relationships. Henri is the first call on every engagement and stays on it: scoping, priorities, and the honest conversation when something is harder than it looked. [PLACEHOLDER — one or two sentences on Henri's background, to be supplied.]
Since 2012
Codelight has been shipping software continuously since 2012. The same discipline has carried through every stack change since: capture the business rules, test them, own the system long-term. Most of what we built years ago is still running, still maintained — by us. That lineage is the point: frameworks have come and gone in that time, and the platforms are still here.
Part of Avalanche Laboratory
Being part of Avalanche Laboratory gives a small unit long-term stability: shared infrastructure, back-office, and the security of a larger organisation behind every contract — without diluting who actually does the work. Engineering stays inside the unit. [PLACEHOLDER — confirm phrasing of the Avalanche relationship and add any specifics worth publishing.]