Helsinki, Finland — taking on new projects
Codepuro is a boutique software studio. We build software and the AI systems that now sit inside it — scoped honestly, in your hands every two weeks, handed over clean.
Every client gets one of these. Every Friday.
Services
An AI system to build, a product to ship, a decision to check, or a senior pair of hands inside your team — the commitments are the same.
LLM applications, MCP servers and agents that do real work inside your business — not demos. Built the way the rest of our software is built: tested, deployed to your own cloud, and documented well enough that your team can take them over.
From an empty repository to production traffic. Web applications, APIs, integrations and the infrastructure that carries them — built by the same people who will maintain them until you take over.
Architecture reviews, technology decisions and honest second opinions — including whether AI belongs in your problem at all — before the budget is committed. You get a written recommendation you can act on, with or without us.
A senior developer inside your team: your standups, your board, your codebase. By the week or by the month, remote or on site in the Helsinki region — with a clean handover written in from the start.
Approach
Most software projects do not fail on technology. They fail on silence. These four promises exist to remove it.
If your idea is bigger, smaller or simply different from what you think it is, you hear it in week one — not in month five, when the money is gone.
Working software in your hands on a fixed cadence, from the second week onwards. No black-box phases, no first demo three months in.
Every Friday: what shipped, what slipped, what it cost, and what changes next week. In writing, in plain language, whether the news is good or not.
Documentation, credentials and a codebase your next developer can read without us. The code and the IP are yours from the first commit — there is nothing to unlock.
A promise you cannot measure is a slogan. Each of these is measurable, and each of them is written into the contract.
See how a project startsSelected work
Recent engagements. Client names on request — we never publish one without written permission.
An internal assistant that answers operational questions against live company data. Claude on the reasoning side, PostgreSQL and BigQuery underneath, and Slack as the only interface anyone had to learn.
A retrieval chat interface and an MCP server over the same knowledge base, so people and their AI tools query one source instead of two. Google Vertex for the model, Terraform for everything under it.
Lead engineer on a serverless SaaS platform for cemetery administration — records, maps, billing and the AWS infrastructure beneath it. Eighteen months, one delivery cadence, a clean handover.
Lead engineer on a platform for managing fleets of devices and the digital content running on them. React and Node.js, a Go service where throughput mattered, Terraform for the AWS underneath.
Process automation inside a multinational retailer's customer care operation — React and Node.js over a Kubernetes microservice estate on AWS, replacing work that used to be done by hand.
A platform that runs self-contained HTML apps out of Google Drive while honouring the permissions already on each file — no second access-control system to keep in sync.
React Native and Expo on the front, Next.js and PostgreSQL behind. Written specification-first with an LLM in the loop — the spec was the artefact under review, and the code followed it.
Capabilities
AI where it earns its place, and boring, well-supported technology everywhere else — so what we build still runs long after the project ends.
The studio
Codepuro is a senior software consultancy in Finland. No account managers between you and the people writing the code, and no junior handoff once the contract is signed — the developer who scopes your project is the developer who builds it.
Everyone who works on a Codepuro project is senior before they get here, with production systems behind them: enterprise cloud platforms, AI systems, consumer applications at scale. Tools change and we expect to keep learning them; the bar does not move, and it will not as we grow. The training here is commercial as well as technical, which is why the first question is usually about your business, not your stack.
Getting started
You will know whether we are the right studio for your project after one conversation, and what it costs after one document.
You describe the problem. We tell you whether it is something we should take on, and roughly what it takes. If it is not a fit, we say so and point you somewhere better.
Scope, sequence, price and the date of the first working increment. Two pages, no jargon, nothing hidden in an appendix.
We start with the riskiest part first, so you learn the most in the first two weeks — while changing course is still cheap.
Practicalities
Both. Fixed price suits work we can scope tightly — a defined product, a migration, an audit. Time and materials suits open-ended development and team extension. In either case you get a written budget ceiling before we start, and we tell you when we are approaching it rather than after we have passed it.
From a two-week architecture review to multi-month product development. What matters more than size is that the problem is real and the decision-maker is reachable. We would rather turn down a large project we cannot do well than staff it badly.
Yes — that is a large part of what we do. We join your standups, your board and your review process, and we follow your conventions rather than importing ours. Expect the first week to be slower while we read the code and ask uncomfortable questions.
You do, from the first commit. Work is done in your repositories and your cloud accounts wherever possible. We do not keep licence hooks, hosting dependencies or anything else that makes leaving us expensive.
Two separate things. We build AI into products for clients — LLM applications, MCP servers, agents. We also use AI tooling in our own work, spec-first: the specification and the tests are written and reviewed by a human, and every line that ships is read by the engineer whose name is on it. It makes small projects land in weeks instead of months. It does not change who is accountable for the result.
Into your own cloud account and your chosen model provider, under your agreement with them — not into ours. We default to EU regions, we do not train anything on your data, and if a workload should not leave your infrastructure we design it so it does not.
Remote by default. On site in the Helsinki region for kickoffs, workshops and whenever a room beats a call. Beyond Finland we work remotely across the Nordics and the EU, and with clients in the United States, Canada, Australia and New Zealand — we move our hours to overlap yours rather than asking you to take a call at midnight.
Codepuro is a Finnish company, Business ID 3336034-4, in the Finnish VAT register. Finnish clients are invoiced with Finnish VAT; EU business clients with a valid VAT number are invoiced under the reverse charge. Invoicing is monthly, 14 days net, e-invoice or PDF.
Gladly — yours or ours, before the first call if you prefer. We also never publish a client name, logo or screenshot without written permission, which is why some of our work is described here without one.
You get a handover session, written documentation, and a short list of the things we would do next. Many clients keep us on a small monthly retainer for maintenance and questions — but that is an option, never a condition.
Start a project
A few sentences is enough to start. You will hear back from a developer — not a sales team — within one business day.