Automations
Work that runs itself
A trigger, an action, a check. Every step logged, so you can see what happened and when.
Tools for modern IT.
Recurring work, sorted once
From a single task that runs itself to a complete system that replaces software you have outgrown. You can see what it does, you can check it, and your data stays yours.
What that looks like
- 09:14:02signal from the hr export
- 09:14:02account and licence ready
- 09:14:03added to four groups
- 09:14:04mailbox and signature
- 09:14:05laptop on the handout list
- 09:14:05done in 3.1 s, 0 errors
Every step with its time and its outcome. If something went wrong, you can see where.
Example, no customer data shown.
- reset a password
- access to a shared folder
- register a new phone
- book time off
- no ticket, no queue
Access through the account that already exists. You decide what is allowed.
Example, no customer data shown.
- open notifications
- 12
- older than five working days
- 2
- manual actions last week
- 41
- of those automated
- 33
- time recovered
- 6.5 hours
Not everything that can be measured, but what you actually use.
Example, no customer data shown.
Who we are
Mikrotools is the name Mikromedia builds under. Mikromedia is an IT company in Susteren, in the south of the Netherlands, close to the German border. It has been a managed service provider and a web developer since 4 January 2007. Since 1 September 2025 the development work has carried a name of its own.
That matters for one reason. Whoever builds your tool also looks after the systems it plugs into. A software agency cannot say that, because it does not know your environment. A managed service provider that does not build cannot say it either.
One person does the work. Over the years there have been colleagues and interns for particular skills, but the person you talk to is the person who builds. It also means we do not take on ten projects at once.
How we work
We start with the work as it actually happens, not with a list of requirements. Half a day spent watching it being done almost always turns up something a requirements meeting never does: the detour everyone takes because the system will not let them do it properly.
Then we pick one thing, build a tool for it, and after a few weeks we check whether it saved anything. If it did not, we adjust it or we stop. A tool nobody uses costs more than the manual work it was meant to replace.
Where we work
The Netherlands, Belgium and Germany. Correspondence and meetings in Dutch, English or German.
The rest of this site is in Dutch. If you would like any of it in English, send us a message and we will translate it for you.
Where we belong
Mikromedia is a member of the Dutch Cloud Community, the trade association for the Dutch cloud and internet sector, where the debate about digital sovereignty is actually being had.
What we build
Portals
Self-service without a ticket
One place where your staff or your customers sort things out themselves, using the account they already have.
Dashboards
The numbers you actually run on
One screen with the figures you use to make decisions. Not everything that happens to be measurable.
Integrations
Systems that finally talk to each other
Through the APIs of the software you already run. Your accounting package, the supplier portal, the ticket queue, joined up instead of retyped.
Full systems
When off-the-shelf software stops fitting
Sometimes the honest answer is that no single tool will cover it. Then we build the system ourselves, and leave the bookkeeping in your accounting package, where it belongs.
AI
Where it genuinely saves time
Language models where they take work off your hands, such as reading documents and pulling the figures out of them. Because it measurably helps, not because it is possible.
FAQ
Where does it run, and who can get in?
You choose. On our servers in Western Europe, or in your own Microsoft Azure tenant if that is where you already work. The same goes for signing in. If your people already work in Microsoft 365 and this is for a larger group, we recommend Entra ID with MFA, so nobody needs another password and your own access policy covers this tool as well. For a small team we usually pick something lighter, and we tell you what that means.
What if we need sovereign hosting?
That is possible. The application runs with a European or Dutch provider that is not subject to foreign jurisdiction, signing in goes through Keycloak hosted in the EU, which does what Entra ID does including two-factor, and if the application calls a language model, that model comes from a European provider or runs on our own infrastructure. There is less to choose from on that route and the field moves quickly, so we decide per project, based on what is available at the time. Both routes have a price, and you should know both before you decide. Stay with Microsoft and your people sign in with the account they already have, and your own access policy applies here too. European customer data is stored and processed inside the EU, while the company itself remains subject to US law, and that is what the discussion is about. Go the sovereign route and your processing falls outside that law, and you know which jurisdiction every link in the chain answers to. In return, Keycloak is a system somebody has to manage, and your people get one extra step when they sign in. The same question applies to how we build, not only to what we hand over. We develop with Claude Code from Anthropic and Codex from OpenAI, both American, which means data can pass through them while the work is going on. If nothing may leave Europe, we build without that help. That takes longer and costs more, and it goes in the quote rather than into a conversation afterwards. We have no preference either way. We put both price tags in front of you before you choose.
What happens to our data if we stop?
Your data is yours and stays yours. You can ask for it at any time in a common format, with documentation describing what is in it. Where it fits, the tool exports it regularly by itself. The software does not come with you: it is web-based, it runs on our infrastructure and it stays ours. You are buying the use of it, not ownership.
Do you work in English?
Yes, in writing and in meetings. The rest of this website is in Dutch, because most of our clients are Dutch. Tell us what you need in English and we will send it over.
Something in your week that keeps coming back?
Show us one recurring task and we will show you what a tool changes about it.