The product
What Fundarem is
Fundarem connects the software systems a business already uses into one map of the business, so AI agents, assistants and dashboards can work on it.
It is built for European businesses that want to use AI and keep to the EU rules. It is designed to run in the company's own Microsoft Azure, in an EU region, so the data stays in the company's own cloud.
The live demo shows it on a made-up company with made-up people. Nothing you do there touches a real system.
Sur le site :Live demo
How it works, step by step
Your systems keep running where they run today. Nothing is migrated or replaced: Fundarem reads from them, and writes changes back to them only where you allow it.
Each system is translated into one map of your business: objects such as customers, invoices, projects and people, the links between them, and the actions that can be taken on them. When the same customer is known in several systems, Fundarem finds the match by itself and puts it to your admin as a proposal; it counts on the map only after it is approved as your company's approval rules require.
Agents and assistants work on that map, never on a system directly. When a task needs an AI model, only the prompt for that one call goes to the model you chose, and the model keeps nothing between calls.
What is logged in your own cloud: every answered model call, with who or which agent made it, the model used and what it cost; every request an agent makes to your map; and every change, with who proposed it and who approved it.
Sur le site :How it works
Agents, assistants and dashboards
Agents do routine work: they read, check and prepare, and every change they want to make is proposed; your admin decides which changes may be written back and which run automatically. Ready-made company agents come with the product and run on the model your company chose; your company switches one on through a proposal, and every run counts against your spending limit. Each person can also pick agents or create their own.
Every employee has their own assistant, opened from the corner of every page and bound to that person's own access. It reads the page the person is on, answers in plain words and follows the person's role, so a salesperson and the finance lead get different answers to the same question. It answers from all your connected data, explains and proposes; every change it proposes needs approval. By default it answers in text, and it builds a widget or a report when asked.
Each company has its own company brain: written entries on how your company works, such as how you price or who signs off a discount, each with an owner and a review date, kept in your own installation. The first-run setup proposes a starter brain from your answers, and a change to a shared entry needs the approval your company has chosen. People search every entry and propose new ones on the brain's page, and a shared entry can be limited to who may read it. The product's manual is inside your installation too, and the assistant answers questions about it with a link to the screen.
Dashboards are built from the same map, so every figure comes from the same joined-up data.
Your IT admin can add sections to the side menu beside the dashboard, for example one for people records: chosen kinds of records with chosen fields, from one system or several, shown to the roles the admin picks. A section reads the data each time it opens and never shows more than the person's role may read; personal records show a person their own record, while a manager and the IT admin see them all.
Sur le site :How it works
AI models
How models are chosen
You choose the AI model that fits your rules, the quality your work needs and your budget. There are five kinds of offering: the default model, models processed only in the EU, models processed in any Azure region, frontier models, and a model on your own machine. Each is described below with every model in it, its licence and where it processes a prompt.
The frame is the set of offerings your company may use. It is chosen with us at setup, so a regulatory choice such as EU-only processing cannot be changed by accident later. An EU-only frame keeps every request processed in the EU.
Inside the frame, your IT admin picks which model takes which kind of task: a strong model for the hard work and a cheaper one for routine tasks. With EU-only processing, for example, the strongest model processed in the EU takes the hard work and a cheaper one processed in the EU the routine work.
We always offer the best models we can find and look for the lowest price, because we earn nothing on them. You pay for model use directly: we take no cut.
Sur le site :Models
Foundry Azure, open source
The best open-weights models in the Microsoft Azure AI Foundry catalogue, one per vendor, deployed into your own Azure and billed on your Azure invoice, at open-model prices. The default model is one of them.
Your stored data stays in your EU region, but the prompt of each request is processed outside the EU: the default model is processed by a third party that serves it inside Azure, and Microsoft excludes that hosting from its EU Data Boundary commitments.
The models in this offering:
FW-Kimi-K3, from Moonshot AI. Licence: Kimi K3 License. It is processed outside the EU, by a third party serving it inside Azure; pay per use, on your Azure invoice.
FW-DeepSeek-V4.1-Flash, from DeepSeek. Licence: MIT. It is processed outside the EU, inside Azure; pay per use, on your Azure invoice.
FW-GLM-5.3, from Z.ai. Licence: GLM-5.3 License (MIT-style). It is processed outside the EU, inside Azure; pay per use, on your Azure invoice.
gpt-oss-120b, from OpenAI. Licence: Apache-2.0. It is processed outside the EU, inside Azure; pay per use, on your Azure invoice.
Sur le site :Models
Foundry Azure EU, open source
For work where every prompt must stay in the EU. These are the best open-weights models sold by Microsoft with an EU Data Zone deployment, one per vendor: Microsoft processes each prompt inside Azure, only in EU member countries, under one Azure agreement.
The choice is smaller than the default's, and new releases reach the EU Data Zone later. Llama-family models are not offered.
The models in this offering:
DeepSeek-V4-Flash, from DeepSeek. Licence: MIT. It is processed only in the EU, by Microsoft; pay per use, on your Azure invoice.
Mistral-Large-3, from Mistral AI. Licence: Apache-2.0. It is processed only in the EU, by Microsoft; pay per use, on your Azure invoice.
Sur le site :Models
Frontier models in Foundry
The strongest closed models sold in Azure AI Foundry, one per vendor, for the hardest tasks. They are deployed into your own Azure and billed on your Azure invoice.
Closed weights cannot be moved to your own machines. The prompt of each request may be processed in any Azure region worldwide, including outside the EU; for some of these models the model's vendor is the data processor. The anonymiser is on by default for them as for every model.
The models in this offering:
Claude Opus 5.5, from Anthropic. Licence: closed, under Anthropic's terms. It may be processed in any Azure region worldwide, including outside the EU; pay per use, on your Azure invoice.
gpt-6-astra, from OpenAI. Licence: closed, under OpenAI's terms. It may be processed in any Azure region worldwide, including outside the EU; pay per use, on your Azure invoice.
grok-4.7, from SpaceXAI. Licence: closed, under SpaceXAI's terms. It may be processed in any Azure region worldwide, including outside the EU; pay per use, on your Azure invoice.
Sur le site :Models
Self-hosted VM in your Azure
For full isolation: open model weights run on a GPU machine in your own Azure, in Norway East, Sweden Central or West Europe. No model vendor is involved, and no prompt leaves machines you run. Any other open-weights model whose licence allows it runs there too, including your own fine-tuned one.
You pay for the machine every hour it runs, used or not, and you look after it. The largest models need a multi-GPU machine, which costs far more; the models page shows the monthly range per machine.
The models in this offering:
DeepSeek V4.1 Flash (open weights), from DeepSeek. Licence: MIT. It runs on your own machine, in your Azure region; you pay for the machine by the hour.
GLM-5.3 (open weights), from Z.ai. Licence: GLM-5.3 License (MIT-style). It runs on your own machine, in your Azure region; you pay for the machine by the hour.
Kimi K3 (open weights), from Moonshot AI. Licence: Kimi K3 License. It runs on your own machine, in your Azure region; you pay for the machine by the hour.
Qwen3.8 2.4T A95B (open weights), from Qwen. Licence: Qwen3.8-Max License (MIT-style). It runs on your own machine, in your Azure region; you pay for the machine by the hour.
Sur le site :Models
Direct access
A direct connection to the model vendor's own API, outside Azure, billed by that vendor. Your key to the vendor's API is stored in your own Azure subscription.
The vendor processes each prompt on its own service, outside Azure and outside the EU, as an independent data processor, so you need a DPIA and a transfer safeguard. The anonymiser is on by default for it as for every model.
The models in this offering:
Claude Opus 4.8, from Anthropic. Licence: closed, under Anthropic's terms. It is processed by the vendor on its own service, outside Azure and outside the EU; pay per use, billed by the vendor.
Sur le site :Models
The anonymiser
The anonymiser is on by default for every model. Before a request goes to a model, it replaces with placeholders the values in the columns your admin marks for masking, and the names and patterned values it recognises, such as Norwegian national ID numbers, phone numbers and IBANs.
The answer comes back with the real values put back in, so people see real names while the model never did.
Your admin can switch it off per kind of personal data, one model offering at a time; every other kind stays masked. On a model on your own machine it can be switched off for that model altogether. What it cannot catch, such as nicknames, is listed on the compliance page.
Sur le site :How it worksCompliance
How your data is processed
Where your data is stored
Fundarem is built so that everything it stores stays in your own Azure, in the EU region you choose at setup: the map of your business and its history, assistant conversations, the company brain and the log. Your database, files, credentials and model deployments are resources in your subscription, on your bill.
Nothing is stored with us. It is not a shared cloud service: if you part ways with us, there is nothing to hand back.
To bill per active user, your installation sends us one number each month, the count of active users, never who they are or any content.
Sur le site :How it worksCompliance
What flows where
Your systems to your map: connectors read your systems into the map of your business on a schedule, inside your own Azure. In the first-run setup your admin picks which kinds of personal data are always masked before anything goes to a model, and tags each column of a new connector as it comes in.
Your map to the model: when a task needs an AI model, only the prompt and context for that one call leave, masked by the anonymiser, to the model offering you chose. Which offering processes it where is said on each model above. The model keeps nothing between calls.
The model back to you: the answer comes back into your installation, with masked values put back in. Nothing else leaves: not the map, not the history, not the log.
Every step is logged in your own Azure: every answered model call with the model used and what it cost, every request an agent makes to your map, and every change, with who proposed it and who approved it.
Sur le site :How it works
Écrire dans vos systèmes
L’écriture dans vos systèmes est l’un des réglages que votre administrateur gère dans Fundarem, à côté des rôles, des modèles et de l’anonymiseur. Elle reste désactivée tant que votre administrateur ne l’active pas : rien n’est écrit dans un système connecté avant cela.
Chaque connecteur déclare les opérations d’écriture qu’il peut effectuer dans son système, comme créer ou modifier un enregistrement, et seules celles-ci peuvent être activées. La bibliothèque de connecteurs indique lesquels peuvent écrire.
Votre administrateur décide en trois étapes : d’abord quels objets d’un système peuvent être écrits ; puis quelles opérations d’écriture sur ces objets sont activées ; puis, par rôle et par personne, qui peut utiliser chaque opération et comment elle est décidée : deux approbateurs (une autre personne que le demandeur l’approuve), un approbateur, semi-automatique (elle s’exécute seule quand elle peut être annulée, sinon un approbateur décide) ou automatique. Votre administrateur choisit aussi qui approuve : les responsables, ou des rôles et des personnes choisis.
Une demande ne va jamais au-delà de ce que la personne ou l’agent qui la fait a le droit de faire, et chaque demande, décision et écriture est journalisée avec qui, quoi et quand. Si un système ne répond pas clairement sur le passage d’une écriture, elle n’est pas renvoyée : elle est marquée résultat inconnu, et votre administrateur vérifie le système avant toute nouvelle tentative.
Votre administrateur peut tout modifier à tout moment, à la connexion d’un système ou plus tard, sous Admin → Orchestrateur → Actions par système. Une modification y est proposée et s’applique dès qu’un responsable l’a décidée.
Sur le site :How it worksConnector library
Connecting your systems
Three ways to connect a system
A ready connector from the library: connectors are sorted by category, and each one says what it reads.
The system's own MCP server: a system that already offers one is connected as it is, and only the tools on its allow list, agreed with you at setup, are let through; your admin chooses the tools, fields and columns on a screen.
A custom connector: for a system with neither, we provide a connector and set it up with you.
All three end in the same map of your business, and before any data flows your admin confirms on a screen what a new connector brings in. After go-live your admin adds more connectors from the library at any time, and new ones reach the library with software updates. Missing one? Request a connector and we send a quote.
Sur le site :Connect your systemsConnector library
Who decides what
Your IT admin picks connectors and connects them, tags each column of a new connector for masking as it comes in, and chooses in the first-run setup which kinds of personal data are always masked.
A manager decides which connectors are switched on, and whether for everyone or for managers only. A change to a shared entry in the company brain needs the approval your company has chosen for the brain.
The sign-in details for your systems are entered by your IT admin and kept in your own Azure, not in Fundarem's own data.
Each person's assistant and agents see only what that person's role may see.
Sur le site :Connector library
From the first call to running
1. Contact us: tell us about your business, the systems you use and the AI model you prefer. 2. The call and the contract: we talk through your systems and your compliance needs, and agree the contract. 3. Your onboarding profile: the systems to connect, the AI models you may use, your region and your plan.
4. One standard edition of the software for every company, delivered ready to set up. 5. You choose who sets it up in your Azure: yourselves, with our steps, or us for you. 6. Fundarem is installed in your Azure, with sign-in through your own company accounts.
7. Your IT admin sets your preferences in the first-run setup and enters the credentials for your systems. 8. We check the installation in your Azure before it goes live. 9. Live: your company starts working with Fundarem.
After go-live, when we publish a new version, your admin approves it in the admin panel or sets an automatic window for it, and the installation installs it by itself.
Sur le site :How it worksContact us
Our access, and taking it back
Fundarem runs in one dedicated part of your Azure subscription. Your IT admin gives us access to that part only, in the Azure portal, and you keep full ownership of your subscription.
After go-live, your admin chooses in the admin panel how much access we keep, and can switch it later: we stay in, to monitor the installation and assist, or limited access, only what is needed to run it. The admin panel records the choice, and your admin then makes the matching change in your own Azure. Fundarem then checks in your Azure that the change matches the level chosen.
You can take the access back at any time.
Sur le site :Contact usCompliance