About
A small Tallinn team focused on useful AI
CODEAXIS OÜ (cdx-automation.eu) is a studio building AI lahendused — practical AI applications — for Estonian businesses. We are developers and analysts, not a sales network. Our work is implementation: connecting language models to inboxes, catalogues, and knowledge bases so office teams spend less time on copy-paste. We keep projects small, documented, and reviewable.
The same five-stage hand-off runs through every project on this page.
Where we work from
One Tallinn address, most work done on your side of the table
Our registered office is Sepapaja tn 6, Lasnamäe linnaosa, Tallinn, Harju maakond, 15551. Most client meetings happen online or at the client's office — that is where the actual workflow lives. Being in Tallinn matters because many buyers, from Tehnopol startups to public-sector teams, are within a short drive of us. You can reach us at [email protected] or by phone on working days.
What we believe about automation
Remove a defined chore. Not your company.
Automation goes wrong when it starts as an idea and never lands on a task. We start from one inbox folder, one product list, or one ticket queue — something a person on your team already handles and already knows the acceptable answer for. If we cannot name the input, the check, and the output on one page, we do not build. That keeps expectations honest and lets staff trust the tool because they know exactly what it does and where it stops.
-
Name the input
A folder, a list, a queue — something that already exists in your day. If we cannot point at it, there is no project to scope.
-
Name the check
The rule a human already applies before saying yes — a price band, a policy, a stock level. The system applies the same rule and every outcome is reviewable.
-
Name the output
A drafted reply, a listing row, a summary. The output reaches a person who decides; it does not quietly sign anything itself.
How we handle knowledge and sources
Every answer points back to a row, a file, or a price list
Inspired by approaches such as Atlaswiki, which structures company knowledge into attributable facts and flags contradictions, we keep every answer traceable. When two sources disagree, the system flags the conflict rather than guessing. Your team reviews the flag and fixes the source it came from. That review step is not optional — it is part of every project we hand over.
Where a conflict goes
- Flag The system marks the answer and shows the two sources that disagree, side by side.
- Review A person on your team opens the flagged row, reads both sources and decides which one is correct.
- Fix the source The corrected row is written back to the source of truth — your price list, your product feed, your internal wiki — not to a parallel copy we control.
- Log Every flag, review and correction is written to a log your team can read in plain language, not a black box.
What this means for staff
Nobody has to trust an answer they cannot check. If a figure looks wrong, the source is one click away and the correction is a one-line edit. That is the whole point of keeping the knowledge base attributable.
The review step is part of delivery, not an add-on.
Our link to the local scene
Practical apps sit between infrastructure and daily office work
We follow the same Tehnopol 2026 AI cohort that includes AveoTech and Auctologue, because those teams solve narrow business problems rather than general chat. We also watch infrastructure news such as the Nebius-operated AI factory at Greenergy Data Centers, since the location of compute affects latency and how data is handled in practice.
We are not affiliated with any of those organisations. We mention them because they show where CODEAXIS fits: our work sits in the layers between the infrastructure underneath and the daily office routines above — the invoices, listings, drafts and tickets that a person still has to touch.
Shapes the market — not partners of CODEAXIS.
Responsible delivery in practice
Controlled deployment, agreed before launch
Reason Reserve, run by Estonia's Information System Authority, shows the public-sector preference for controlled deployment over open experimentation. For business clients we apply a similar rule. Access limits, logging, retention periods, and human approval for money-related drafts are all agreed in writing before launch. Staff get a one-page guide on what the tool may quote and when to step in.
- Access limits
- Only the people who need the workflow get an account. Nobody outside your team can read the data the tool touches.
- Logging
- Every automated action against a draft is recorded with the time, the trigger and the person who approved what followed.
- Retention periods
- We agree how long logs and intermediate data are kept, and delete them on that schedule rather than leaving them behind.
- Human approval
- Anything that touches money, contractual language or a customer commitment waits for a person to sign off — before it leaves the building.
- Staff briefing
- A one-page guide for the team: what the tool may quote, what it may not, and the exact moment to step in and take over.
What we don't do
The line we do not cross
Knowing what a tool will not do is how a buyer knows what they are getting. These are the boundaries that hold on every project, no matter how useful the pitch is.
- Not autonomous We do not build fully autonomous sales agents that sign contracts alone. Money and commitments wait for a person.
- Not scraping We do not scrape private databases, and we do not resell client data — for training, benchmarking or anything else.
- No fake stamps We do not claim compliance certifications we do not hold, and we do not paste badges onto a page to look larger than we are.
- Not your lawyer If you need legal advice on vastavus or data protection, we ask you to involve your counsel — and we implement their requirements technically, in the build.
How we learn
Good tools teach process, not just answers
Estonian education pilots like ITI, developed with education researchers and the Institute of the Estonian Language to help learners plan and think independently, remind us that a tool earns its place by teaching the person using it, not by replacing them. Our pilots include short training for your team: how to correct drafts, how to update the knowledge base, and how to read the logs. After two sessions, most teams manage daily use without us.
The two-session handover
- 01 Session one walks your team through what the tool is allowed to quote and what it must hand back for review.
- 02 Session two is your team driving: correcting a real draft, resolving a source conflict, reading a week of logs.
- 03 After that, daily use sits with your people. When something needs extending, you write to us with the workflow, the volume and the current software.
Team and contact
You talk directly to the people who build your tool
CODEAXIS OÜ is a compact team. There is no account layer between you and the developers — the analyst who scopes your workflow is the person who builds it, and the person you write to when something needs to change. That is deliberate, because every project is small enough that a handover across departments would cost more than it saves.
For project enquiries, write to [email protected] with your workflow, its volume, and the software you currently use. We reply on working days, Monday to Friday, 9:00–18:00.
Next step
Send one workflow and we will scope it in writing
A short note is enough: the folder, list or queue you want handled; the approximate volume per week; and the software you currently use. We reply on working days with the input, the check and the output named in one page.