Skip to content

What runs, what turned on without you, what is coming.

For IT leadership and IT teams: Ojja reads, read-only, your licenses, your settings and the applications your employees have authorized, and keeps each AI feature on its own line: who turned it on, on which model, hosted where, and what was decided.

Request a readoutTry it with the Arvenne example

An IT department's questions

  • What is connected, on which model, hosted where, and who decided?
  • What did our vendors turn on by default this month?
  • Which applications have our employees authorized on our data?
  • The AI models behind our tools, did we choose them, or did they arrive with them?
  • An employee asks for a tool: what do we already have that does the same thing?

Ojja does not answer for you. It gives you the facts to answer.

What you see in Ojja Watch

  1. The IT view. The register grouped by vendor, filtered by type of AI (agent, assistant, built-in feature, model access) and by underlying model, with two layers: sovereignty and the decision.
  2. The origin and provenance of each line. Turned on by the vendor, by an administrator or by an employee; extracted from your tools, declared by you, or inferred.
  3. The models behind your tools. How many features and agents rely on each model, and in which country it is processed.
  4. The agents. Those that run, and those that never run.
  5. What is coming. The public feed, filtered on your software, and five alerts, as soon as the event is read: new AI application connected, usage billing turned on, vendor terms or features changed, new model behind a feature, new data access.
  6. The activation circuit. Nothing new arrives without going through a decision: an announced novelty goes to waiting in the register, you can defer it as long as the vendor allows, you decide, the employee portal announces it with its rule, and the next snapshot records that it is done.
  7. The Connections page. Tool by tool, what is read, and the rule on data: “we never have access to it” when the tool separates settings from content, “we never touch it” otherwise.

Your tools are read every day or every week, depending on the tool; an alert on five events as soon as they are read; a dated snapshot every week to decide.

The logs of your AI tools

For each feature, what the vendor documents of its logs: whether it gives them to you (yes, partly, no), how long it keeps them, whether you can export them; “not documented” as long as it says nothing. Ojja does not read these logs: it records what the vendor documents of them.

The framework the catalog links to certain types of feature: the European regulation on artificial intelligence, Article 26(6), applicable from December 2, 2027 for the systems of its Annex III, with the points to review with your counsel.

On the Arvenne example

Arvenne's readout reads 37 applications and 14 AI features. Grouped by vendor: at Microsoft, Copilot Chat, enabled by the administrator for all 412 accounts, the Teams meeting recaps, enabled by the vendor with no decision, and a Purchasing agent built in Copilot Studio; at OpenAI, ChatGPT, connected by employees on 14 accounts. During the week, Arvenne's AI lead regularizes the meeting recaps and turns off the AI companion of the video conferencing tool. The administrator applies; the next snapshot records it.

Arvenne, a fictional company · sample data

See an example: Arvenne

What you get out of it

  • The before-you-buy sheet: the AI fact sheet of the candidate software, in the same template as the others, and the equivalent you already pay for.
  • The answer to a tool request: an employee asks, the sheet goes out with the equivalent already paid for, you decide; the answer holds for the next ones.
  • A client's AI questionnaire, filled in from what is read.
  • The COMEX page, every quarter, with Ojja Watch Committee.

What Ojja never does

  • Ojja never writes in your software: it turns nothing on, turns nothing off and configures nothing. Your administrator applies; the next snapshot records that it is done.
  • Ojja reads registers and configurations, never your content.
  • Ojja installs nothing on workstations. The list of permissions is published before the button.
  • Ojja gives no figure per person.

Ojja does not provide legal advice: it records and documents; how the law applies to your situation is for your counsel to determine.