The system that enables European businesses to become agentic

Make your business agentic, while staying compliant.

Fundarem connects your systems into one map of your business, so AI finally understands how your customers, invoices and projects fit together. All while staying compliant with EU laws and regulation.

On that map, AI agents can do routine work or complex tasks, and every employee gets an AI assistant on the data they’re allowed to see.

Fundarem and your data run in your company’s own cloud, in an EU region. You choose the AI model that fits your regulatory requirements, quality needs and cost, while always tracking spend and maintaining control of your budgets.

Your own cloud, in the EU: Fundarem and your data
AI agentsExample work
  • Matching payments to open invoices
  • Flagging a late-paying customer
  • Drafting a payment reminder
readwrite back, where you allow
One map of your businesseverything linked

Your software systems

  • ComplianceBuilt to help you comply with GDPR and the EU AI Act, with every step logged
  • Connected systemsYour software systems, connected once
  • Your data, linkedCustomers, invoices and projects joined across systems
  • Understands your businessAgents and an assistant that know how your company works

How it works

Fundarem is built so your stored data always stays in your company’s own cloud in the EU. What you choose is where the AI model processes each request.

See how it works From call to running: the steps

Connect your existing systems

Bring in every system, whichever way it connects.

Pick a ready connector, use the system's own MCP server, or have us build a connector for a system nobody has connected yet. All three end the same way: in one model of your business, with your admin choosing which columns are sensitive. Later, your admin adds more from the library, which grows with software updates. Missing one? Request a connector and we send a quote.

  1. Browse the library
  2. Bring your own MCP
  3. Custom connector
One model of your business

Choose your AI model

Pick the AI model that fits your regulatory needs, the quality your work needs and your budget. Our Models page compares them side by side. An EU-only frame is possible too: chosen with us at setup, it keeps every request processed in the EU.

  • The best models, at the lowest priceWe always offer the best models and look for the lowest price, because we earn nothing on them.
  • Models combined by how hard the task isInside the frame you choose, a top model can take the hard tasks and a cheaper one the simple tasks. With EU-only processing, for example: the strongest model processed in the EU for hard work, and a cheaper model processed in the EU for routine work. Fundarem is built to send each kind of task to its own model. Your admin picks which model takes which kind of task.
  • No cut on your AI useYou pay Microsoft for the model directly, one to one, on your own Azure invoice. We take no cut of the tokens and have no part in that transaction. A model vendor’s own API, outside Azure, bills you directly too.
  • What you pay usPricing is on request. No onboarding fee. Spending is always tracked, and you set what the AI may spend per request and per day. Your admin sees each user’s activity and what it cost.
  • Foundry Azure, open sourceDefault

    Kimi K3

    Where a request is processed: Outside the EU

    Pros

    • Open-weights models at open-model prices, billed through your Azure subscription; the same weights can also run on your own machine.
    • No vendor account of ours: the deployment and its key are yours, with Azure governance and access control.

    Cons

    • Prompts are processed outside the EU: a third party serves this model, and Microsoft does not include that hosting in its EU commitments.
    • Paid per use, this model can be processed anywhere in the world; its host offers no regional option in the EU.

    Benchmark scores

    Source: model card, fetched 2026-09-28.

  • Foundry Azure EU, open source

    DeepSeek V4 Flash

    Where a request is processed: In the EU (Microsoft Azure)

    Pros

    • Prompts never leave the EU: Microsoft processes them only within EU member countries.
    • Sold and supported by Microsoft under one Azure agreement.

    Cons

    • Fewer models than where processing may happen anywhere in the world, and weaker than the default on the published benchmarks.
    • New models arrive here later than where processing may happen anywhere in the world.

    Benchmark scores

    Source: model card, fetched 2026-09-28.

    Source: model card, fetched 2026-11-03.

  • Frontier models in Foundry

    Claude Opus 5.5

    Where a request is processed: Outside the EU (Microsoft Azure)

    Pros

    • The highest-ranked models on Foundry's quality index and the Artificial Analysis Intelligence Index.
    • Sold through Azure under one agreement, billed on your Azure invoice.

    Cons

    • Closed weights: you cannot move the model to your own machines.
    • Prompts are processed outside the EU; for some of these models the model's vendor, not Microsoft, is the data processor.

    Benchmark scores

    • GPQA Diamondno public figure
    • Terminal-Bench 2.1no public figure
    • SWE-Bench Verifiedno public figure
  • Self-hosted VM in your Azure

    DeepSeek V4.1 Flash (open weights)

    Where a request is processed: Your own machine

    Pros

    • Ahead of the default on 3 of the 4 published scores they share.
    • Full isolation: no prompt ever leaves machines you run, in the region you chose.
    • Any open-weights model whose licence allows it, including your own fine-tuned one.

    Cons

    • You patch, scale and monitor it; Spot prices are cheaper but the machine can be evicted.
    • The largest models need a multi-GPU machine; the price list shows no H100 or A100 machine in Norway East today, so Sweden Central or West Europe it is.

    Benchmark scores

    Source: model card, fetched 2026-11-03.

  • Direct access

    Claude Opus 4.8

    Where a request is processed: Outside the EU (the vendor's own API)

    Pros

    • A direct connection to the vendor's own API, with no Azure deployment to set up.
    • Billed by the vendor per token, on your own account with it.

    Cons

    • Prompts are processed outside Azure and outside the EU, by the model vendor: you need a DPIA and a transfer safeguard.
    • Closed weights: you cannot move the model to your own machines.

    Benchmark scores

    Source: model card, fetched 2026-09-28.

GPQA Diamond
Graduate-level science questions
Terminal-Bench 2.1
Multi-step tasks in a real command-line terminal
SWE-Bench Verified
Fixing real, human-checked issues in open-source code

Scores in percent, as published on each figure's source page; higher is better. Tap a score to open that page. Where no public page gives a score, the card says so: we never estimate one.

Compare the models

An AI assistant for every employee

It works like the AI assistants you already know, but on your own company’s data.

  • Ask in plain wordsQuestions about customers, invoices, projects or people get an answer from all your data, not one system at a time.
  • Sees only what you may seeEach person’s assistant follows their role. A salesperson and the finance lead get different answers to the same question.
  • Prepares the workIt finds, summarises and drafts, and makes changes only where your company allows it.
  • Every question is loggedWho asked what, and what was done, is kept in your own log.
  • Knows how your company worksEach company has its own company brain, built to be kept in your own installation, and the assistant answers with it.
  • Knows the manualAsk the assistant how something in Fundarem works or where to find it. It answers from the product’s own manual and links to the screen. Parts written for admins are for admins and managers; a member does not get them.

Example, fictional data

Which customers are behind on payments this month?

Three customers have overdue invoices:

  • Nordvik Bygg ASkr 48 312
  • Fjordlys Designkr 21 900
  • Berg & Sønnerkr 9 450

Nordvik also has an open deal worth kr 450 000. Shall I draft a friendly reminder to each of them?

An agent at work, example with fictional data
AI assistantDone
Linked data
  • CustomerNordvik Bygg AS
  • Overdue invoicekr 48 312
  • Open dealkr 450 000
Draft
Friendly reminder

Invoice 1187 for kr 48 312 is now 14 days overdue.

A gentle tone, since a deal is open.

Allowed by your write settings
Written back, where allowed

Reminder sent and noted on the customer

How we solved this before

Four walls stand between a business and AI. Before Fundarem, we took them down in a live, working system for one of Norway’s three largest accounting firms.

  1. Wall 1

    No integrations

    The firm’s ERP systems had no standard way to connect an AI agent, and some had none at all. We connected Xledger, Tripletex, PowerOffice and Business Central.

  2. Wall 2

    No map of the business

    The data was not joined. We built one map of customers, invoices, assets, employees and VAT, and the links between them, ready for AI to read and write.

  3. Wall 3

    Regulation

    Personal data could not simply go to an AI model. Personal data in the marked columns was masked before each model call, and the firm completed and signed a DPIA, starting from our prefilled template.

  4. Wall 4

    Control of the AI models

    The models ran inside our own secure Azure setup, not in a separate AI tool. They processed requests outside the EU, but inside Microsoft’s cloud.

The result: one dashboard for all the firm’s accounting operations, with agents doing the routine work and taking part in the complex tasks. AI agents working on that map saved around 40% of the time on accounting work in general.

What we built: the firm’s ERP systems, one map (the ontology) and one dashboard with AI agents at work
ERP systems
  • Xledger
  • Tripletex
  • PowerOffice
  • Business Central
One map
  • Customer
  • Invoice
  • Asset
  • Employee
  • VAT return
One dashboard
  • Supplier invoices
  • Depreciation
  • VAT return
  • Payroll
  • Bank reconciliation
An agent at work, example with fictional data
Bookkeeping agentDone
Linked data
  • Supplier invoicesNot yet booked
  • SupplierBerg & Sønner
  • Earlier bookingsSame supplier
Draft
Supplier invoices to book

Book every outstanding supplier invoice.

Use the account and VAT code this supplier had before.

Allowed by your write settings
Written back, where allowed

Supplier invoices posted

Fundarem is the same method, built as a product for any business. It joins your systems into one map and puts AI agents and an assistant to work on it, and it is built to run in your company’s own cloud.

Questions

What is Fundarem?

An integration platform that turns a company's software systems into one ontology, so agents and dashboards can work on it. It is built to run in your own Azure tenant, in an EU region.

Which systems can we connect?

Ready connectors: Microsoft 365, HubSpot, Salesforce, Tripletex, Xledger and Gitea. Any system's own MCP server. Or we build a custom connector from the system's API documentation, and you confirm it.

Where is our data stored?

In your own Azure tenant, in the EU region you choose at setup. What can leave is an AI model call, and each route says where it is processed.

Is personal data sent to the AI model?

The anonymiser is on by default for every model. It replaces marked columns, recognised names and patterned values (national ID numbers, phone numbers, IBANs) with placeholders. Your admin can switch it off per kind of personal data.

Do we have to replace or migrate our systems?

No. Fundarem reads from them and writes back only where you allow.

What does it cost?

Priced on request, with no onboarding fee. The AI model is billed on your own Azure invoice.

See it working on an example company.

The live demo runs on a made-up company with made-up people. Nothing you do there touches a real system.