Telecom · Backend & authentication
Elisa
Authentication for Elisa's back-end systems: who gets in, and with what rights.
- Authentication
- Access control
- Backend
We develop software for clients across Europe, from web and mobile apps to cloud solutions and AI.
working dayWe reply within one working day.
weeksWe ship working software every two weeks.
yoursThe code is yours, hosted in the EU.
Senior engineers, no middle layers, and a codebase you own on day one.
Most agencies scale by hiring juniors and adding project managers. That works for them and rarely for you: every layer between the person with the problem and the person with the compiler costs you clarity, time and money.
More about usFrom the first architecture sketch to the servers it runs on. You get one team accountable for the whole thing, not a handoff chain.
Agents, models and chatbots that do real work, not demos.
Marketing sites that load instantly, and SaaS products that hold up under real users.
One Kotlin Multiplatform codebase, native interfaces on both Android and iOS.
Spring Boot services and PostgreSQL schemas designed to still make sense in year three.
Reproducible infrastructure, automated deploys, and a bill you can explain.
Authentication that passes an audit, and the connections to everything else you run.
“Techbaltics OÜ is an Estonian software company. We are deliberately small: the people who scope your project are the people who write the code and the people you call when something breaks at 23:00.”
Three we can talk about publicly.
Telecom · Backend & authentication
Authentication for Elisa's back-end systems: who gets in, and with what rights.
Marketplace · Web & automation
Car rental and sales platform with an automated pipeline that keeps listings in sync with an external classifieds site.
Marketing site · Web
A charter company’s public site, built for the kind of client who judges the boat by the website.
A paid two-week sprint: we map the domain, agree the scope, and produce an architecture and a budget you can actually plan against. You keep the output whether or not we continue.
Data model, API contracts, infrastructure plan, and interface design. Decisions get written down with their trade-offs, so the next engineer to touch the system knows why.
Two-week sprints against a public board. Every sprint ends with something deployed to a staging environment you can click through, not a status report.
We ship it, monitor it, and hand over the runbook. Stay on a support retainer or take it fully in-house: both are normal endings.
The tools we actually use. Every one of them is running in a system we have in production.
Send a few lines about the problem. You will get a real engineer’s answer within one working day, not a sales sequence.