Example
Ana Kovač
Founder and engineering lead
Sets the scope and the architecture on every engagement, and stays on it through handover. Writes the first migration and reviews the last pull request.
About the studio
A small studio in Belgrade.
MetaThema DOO designs and builds software for teams who need the reasoning behind a system as much as the system itself.
The studio
Why the name is MetaThema.
Thema is the subject — the thing under discussion. Meta is the step back from it. MetaThema is the studio that takes that step before anyone writes code: what problem is actually on the table, who carries it, and what would count as solved.
We work from Belgrade, in English and Serbian. The team is deliberately small, so the person who scopes your work is the person who writes it, and the decisions stay in one head rather than in a queue between three.
What we leave behind is meant to outlast us: your accounts, your repositories, and a written record of every decision that shaped the system.
What we hold to
Five things we do not trade away.
Values are cheap to write down. These are the ones you can hold us to on a Tuesday afternoon, mid-project.
Say what the work actually costs
If a request is larger than it looks, you hear it before the work starts rather than in the week it slips. We would rather lose a brief than win it on a number we do not believe.
The people who scope it, ship it
There is no account layer between you and the engineers. Whoever sits in the first call is on the last deploy.
Plain language, including the bad news
Architecture explained in the words of your business, and problems raised the day they appear rather than the day they become visible.
Your accounts, your keys
Everything runs on infrastructure you own. Nothing we build should tie you to us once the engagement ends.
Finished means someone else can carry it
Runbooks, decision records and a walkthrough are part of the work, not a favour at the end of it.
Belgrade
Where the work happens.
Belgrade, from the studio window.
The team
How the team is put together.
Small on purpose, and no rotation halfway through a project. You meet everyone who ends up working on it.
The profiles below are illustrative examples while the roster is being finalised — the names and portraits are not real people.
- Example
Marko Ilić
Senior platform engineer
Owns infrastructure, pipelines and observability. His measure of a good release is that nobody remembers it happening.
- Example
Jovana Petrović
Product designer
Shapes interfaces and the design systems behind them, so the parts a client keeps after we leave still fit together.
- Example
Nikola Savić
Backend and data engineer
Works on domain models, migrations and the retrieval layer under our AI work. Prefers a boring schema to a clever one.
- Example
Milica Radovanović
Front-end engineer
Builds the component layer and guards accessibility and performance budgets from the first commit rather than the last week.
- Example
Stefan Đurić
Delivery lead
Runs the weekly cadence, keeps the decision log current, and is the person a client calls when a date is at risk.
Studio facts
The details, on the record.
Everything we can state today. The rest is added here as it is confirmed, not before.
- Legal name
- MetaThema DOO
- Location
- Belgrade, Serbia
- Working languages
- English · Serbian
- Contact
- [email protected]
Stack
What we build with.
- TypeScript
- React
- Next.js
- Node.js
- Python
- PostgreSQL
- Redis
- Docker
- Kubernetes
- Terraform
- AWS
- Cloudflare
- Playwright
- Figma
Chosen per project — these are the tools we know well, not a house rule.
The team profiles and photography on this page are illustrative placeholders. No real person is pictured or named here, and no client is identified anywhere on this site.
Next step
Tell us what you are trying to build.
One conversation, no deck. Describe the problem in your own words and we will say plainly whether we are the right studio for it, and what we would do in the first two weeks.