I build systems that hold up
Arkaadikas OÜ is a one-person software studio. System architecture, full-stack development, and rescuing legacy systems — no project managers, no handoffs.
What We Offer
Voidship: The Long Journey
Commercial game shipped on Steam. Finished, not abandoned at 80%.
LahinguVõrk
Internal website for managing Members, Tasks, Events for Estonian Defence League unit.
Kratt
Desktop app running multiple Claude agents, visualized as a pixel-art office.
TailRift
Desktop viewer for Serilog/CLEF logs, plus live browser and Postgres monitoring.
What We Offer
Tale of Many Kingdoms
A persistent browser game for squad-tactics fans: run a mercenary captain and warband, take contracts, craft gear, and team up for guilds, co-op and world bosses. A live auto-battler. Your units fight on their own tactics — you call the abilities and the positioning that turn it.
Our Services
Architecture and technical direction
System design, technology choices, and the hard calls: what to build, what to buy, what to delete. Includes technical scoping and honest cost estimation before anyone commits. For teams that need senior-level decisions without a senior-level headcount.
Full-stack product development
.NET and Vue on PostgreSQL with AWS, from empty repo to production. Built so your team can carry it forward after I’m gone.
Rescue and modernisation
Legacy systems, stalled migrations, and codebases nobody wants to touch. I’ve done this in production, not on a slide.
You’ll be talking to the engineer, not a salesperson
Arkaadikas OÜ is run by Madis Rääk. I joined a B2B SaaS company as a senior developer and I’m now its CTO — the same platform, used daily by over a hundred client organisations across the Baltics and Scandinavia, from first commit to running the engineering function. Arkaadikas OÜ takes on a small number of projects a year alongside that.
That means I’ve done both halves of this job. I’ve written the code, and I’ve been the one who signs off on the architecture, the security posture, the deployment pipeline and the budget. When I tell a client that a migration is worth doing, or that it isn’t, it’s from having lived with the result afterwards.
Alongside that I build Arkaadikas’s own products. They aren’t demos: the game runs with real players, Lahinguvõrk with a real organisation. That’s where the problems come from that client work rarely surfaces — determinism, tamper resistance, keeping something alive for years.
Experience
Modernisation at scale
Took a live production backend through a full framework-generation migration, and rebuilt the frontend on a modern stack. Designed the architecture behind a growing customer base, moved heavy processing off the critical path, and introduced automated testing to a codebase that had none.
Cloud, infrastructure and security
Automated deployments and database migrations so releases stopped being manual risk. Built monitoring and alerting that covers business-critical signals, not just server health. Improved backup and disaster recovery, hardened both infrastructure and application layers, and ran the groundwork for an information security certification.
Integrations and platform expansion
Multiple integrations with external HR, payroll and healthcare-related systems. Moved integration configuration to self-service, so clients could connect without booking engineering time.
Leadership and product
Built and scaled an engineering department from the ground up — hiring, onboarding, mentoring, and the processes and documentation standards that outlast individuals. Contributed to product strategy and long-term technical direction, with cost modelling and capacity planning ahead of demand.
How I work
One engineer accountable, output of a team
I run AI-assisted engineering workflows — agents handle volume, I handle judgement. That’s not a shortcut around expertise. It’s what lets one experienced engineer take on work that used to require a small team, and deliver it faster than that team would have.
The quality stays mine. Every architectural decision, every review, everything that ships is signed off by the person you hired. You get the throughput of a team and exactly one name to hold responsible.
The projects in this portfolio were built this way. They’re the evidence, not the pitch.
Why me
One person, start to finish
No handoffs, nothing lost in translation. Whoever designs it, builds it.
Built to be handed over
Code your team can take ownership of. Not a dependency on me.
Systems that actually run
Everything in the portfolio is either in production or shipped.