# Inora vs building it yourself (2026)

**The chat is quick. The work comes after.**

Your knowledge stays yours, with Inora too. Answers, follow-up and filing to the record are a product, not a build project.

Last checked: 2 November 2026

## Separate parts, or the whole job.

| | Building it yourself | Inora |
| --- | --- | --- |
| Your own agreements | **Grounded in what you connect** Knowledge sources ground the answers in your data. With ungrounded responses allowed, the agent also answers from the model’s general knowledge. ([source](https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-copilot-studio)) | **Only your agreements** Only from your agreements, with owner, version and source. The owner sees what is out of date before anyone asks. |
| One step (Where it differs) | **An answer from your knowledge base** In Dify you decide how your content is chunked, indexed and searched. Chatbot and workflow apps answer from it. ([source](https://docs.dify.ai/en/guides/knowledge-base/readme)) | **Know, do and record** In one question Inora looks up how it is done here and drafts the follow-up and the report, in the client’s home. They go in on the care worker’s approval. |
| Into the record | **An integration you build** Connectors link an agent to other systems. For a service without one, you create a custom connector on its public API. ([source](https://learn.microsoft.com/en-us/microsoft-copilot-studio/advanced-connectors)) | **Into Ons on approval** Inora drafts the report in your organisation’s format, the care worker signs, and it goes into Ons on approval. Nobody retypes it. |
| The day prepared | **On a trigger you set** With an event trigger an agent acts on its own when an event you defined occurs, without anyone asking. ([source](https://learn.microsoft.com/en-us/microsoft-copilot-studio/authoring-triggers-about)) | **The shift already prepared** Before the first client, today’s clients and what changed since yesterday are ready. |
| What was said | **A month, unless you change it** Conversations sit in Dataverse and are deleted after a month by default. Answers from SharePoint knowledge are not in the transcript. ([source](https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-transcripts-powerapps)) | **Every answer, with source and version** Every answer is traceable to its source and the version that applied at the time. 15 steps behind every question, every one on record. |
| What stays | **Yours** You deploy Dify yourself with Docker Compose. The installation and what you build in it stay with you. ([source](https://docs.dify.ai/en/self-host/quick-start/docker-compose)) | **Yours too** Your organised knowledge, the files and the structure, even after you stop. |
| Who maintains it | **Your team, at every upgrade** Self-hosted, after every upgrade you compare the .env variables and re-apply your own changes onto the new docker-compose file. ([source](https://docs.dify.ai/en/self-host/quick-start/docker-compose)) | **We do, every day** Upkeep, integrations, testing and the build to NEN 7510 and ISO 27001. 99.6% of answers with no refusal, error or empty reply. |

An assistant on your documents is up quickly. The work comes after: the record, testing every answer, every upgrade.

## Building it keeps control with you.

An agent in Copilot Studio fits the Microsoft estate your IT already governs, with the permissions already set there. Dify you can even run on your own servers. And an IT partner who knows your organisation knows where the switches are. The instinct is right: your organisation should own its knowledge, not rent it.

## The chat is the easy part.

What a build in Copilot Studio or Dify delivers first is a chat over your documents ([Microsoft](https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-copilot-studio), [Dify](https://docs.dify.ai/en/guides/knowledge-base/readme)). The hard part is what comes after, and keeping it working: the report in the record, the day prepared, at night on a phone.

And every answer tested, against test sets you build yourself ([Microsoft](https://learn.microsoft.com/en-us/microsoft-copilot-studio/analytics-agent-evaluation-intro)). Those are hours, for years, on top of the Copilot Credits every answer costs, except for what an agent draws from your own Microsoft environment for users with a Microsoft 365 Copilot licence, in Copilot Chat, Teams and SharePoint ([Microsoft](https://learn.microsoft.com/en-us/microsoft-copilot-studio/billing-licensing)).

## Your own layer around the client record.

A layer around your client record that writes reports is quick to prototype. The work is in the connections, the versions, the recorded approvals and keeping it running after every release of the record. Inora is that layer, and it works now.

On a home-care round, the care worker goes from procedure to action to report. With Inora, your organisation gets that whole workflow as a product, with versions and your quality adviser’s approval.

## In the client’s home, what comes after counts.

Half past seven in the evening. A care assistant sees a red patch on Mrs Peters’ heel and asks Inora, on their phone, what the agreement is. The answer comes from the pressure-ulcer agreement, the version that counts today: offload the heel, reposition every two hours, check the skin every shift. Inora drafts the repositioning for the next shifts and drafts the report, which goes into Ons on the care assistant’s approval.

## Copilot reads the same agreement.

Your organised knowledge can also be read from Copilot, so the same version counts in Copilot as in the client’s home. Your IT partner keeps its role: accounts, policies and the estate around it. Inora delivers knowing, doing and recording, and keeps that working.

## Eight weeks. Your manager signs.

- **Live from day 15.** One team, a fixed price, within your manager’s own budget. You see up front what each part costs.
- **Stop after the evaluation, no notice period.** After eight weeks you decide whether to go on.
- **Two regions chose a second year.** ZorgConnect Zuid-Limburg (16 organisations) and VVT Platform Zuidoost-Brabant (13), after their first year with Inora.

> “In my experience, Inora helps me work out how to solve something right now, and it looks at the information it has from different angles. How do I go on from here? Can I solve this? How do I hand this over?” Project leader, Elderly-care platform, South-East Brabant

## Your IT partner keeps its role.

### How much work is it for our IT?

No connection to your record on day one. Your team signs in with single sign-on through your identity provider, set up once; accounts run through SCIM, and there is nothing to install. Accounts, policy and the environment around it stay with your IT partner. Inora is built to NEN 7510 and ISO 27001; your CISO gets the whole file before the first conversation.

### Where does Inora run?

In the EU or on your own servers. No model trains on your data, not even a supplier’s. What runs underneath, we choose and test; you rebuild nothing.

### What is each answer based on?

Every answer comes from your own approved agreements and carries the source and the version that applies. The professional decides, with that evidence to hand.

### What does it cost, next to a build of our own?

A pilot at a fixed price, then a licence per team or location. No build project up front.

## Other comparisons

- [Inora vs Attendi (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-attendi.md): You do not have to choose: Attendi writes the report from the dictation, Inora drafts the follow-up: incident report, care plan and message.
- [Inora vs Microsoft Copilot (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-microsoft-copilot.md): Copilot searches what is there. With Inora, Copilot and the care worker get the agreement that applies today, with source and version.
- [Inora vs the intranet handbook (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-the-intranet-handbook.md): Your handbook is good and it stays. Inora makes it answer in the client’s home, at night too, with the source and the version that counts.
- [Inora vs Zenya (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-zenya.md): Zenya knows which version of a protocol counts, and AI Chat answers from it. Inora answers from that version and drafts the follow-up and the report.
- [Inora vs Tandem Health (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-tandem-health.md): Tandem Health, formerly Juvoly, writes the consultation note, and with PhoneAssist through Vcare the phone call. Inora works for the whole practice.
- [Inora vs Autoscriber (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-autoscriber.md): Autoscriber records the conversation. Inora gives you the agreed plan and writes the report in the group home or on the ward, on your own agreements.
- [Inora vs ChatGPT (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-chatgpt.md): Your people reach for ChatGPT because the answer isn’t at hand. Inora gives them that answer from your own agreements, on record and safe for client data.
- [Inora vs Nedap Ons (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-nedap-ons.md): Ons stays the client record. Inora prepares the day from Ons and drafts the report; it goes into Ons on approval, so nothing is typed twice.
- [Inora vs Vilans Protocols (2026)](https://axiomatic.digital/en/expertise/compare/inora-vs-vilans.md): Vilans stays your national baseline. With Inora you write and keep your own work instructions, approved by your quality adviser, with source and version.
