Skip to content
Inora vs building it yourself

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.

Talk to our teamTake the 5-minute AI scan

No build project first. Your team works from day 15.

0 build hours

before the start: no installation, no connection to your record

Separate parts, or the whole job.

  1. One stepWhere it differs
    Building it yourself

    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: docs.dify.ai
    Inora

    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.

  2. Your own agreements
    Building it yourself

    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: learn.microsoft.com
    Inora

    Only your agreements

    Only from your agreements, with owner, version and source. The owner sees what is out of date before anyone asks.

  3. Into the record
    Building it yourself

    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: learn.microsoft.com
    Inora

    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.

  4. The day prepared
    Building it yourself

    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: learn.microsoft.com
    Inora

    The shift already prepared

    Before the first client, today’s clients and what changed since yesterday are ready.

  5. What was said
    Building it yourself

    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: learn.microsoft.com
    Inora

    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.

Show all 7 points
  1. What stays= Both do this
    Building it yourself

    Yours

    You deploy Dify yourself with Docker Compose. The installation and what you build in it stay with you.

    source: docs.dify.ai
    Inora

    Yours too

    Your organised knowledge, the files and the structure, even after you stop.

  2. Who maintains it
    Building it yourself

    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: docs.dify.ai
    Inora

    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.

What your own build still has to do after the chat. This is in Inora, and we keep it working.

The chat is the easy part. The record, the testing and every upgrade remain.

Read the full comparison

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, Dify). 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). 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).

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.

“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 leaderElderly-care platform, South-East Brabant

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.

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.

Build on Inora, over MCP.

Also compared: Attendi · Microsoft Copilot · The intranet handbook · Zenya · Tandem Health · Autoscriber · ChatGPT · Nedap Ons · Vilans Protocols. All comparisons