Skip to content

knowmind for companies

The project changes, the knowledge stays.

Shared project knowledge for teams working with several AI tools. Capture decisions, make handovers traceable and retrieve existing knowledge with sources.

Put shared knowledge to work

Start where context gets lost.

01

Project handovers

The next person on your team can read which decision applies and why it was made that way.

02

Consulting and support

Capture agreements and project notes in a shared workspace.

03

Development

Make architecture decisions and project knowledge retrievable from connected development tools.

Before organisational approval

Agree on requirements first.

See security and hosting ↗

Access and responsibility

Shared workspaces, roles and invitations give your team structure. Decide who may store and retrieve which knowledge.

The data processing agreement is included

Business customers need a data processing agreement under Article 28 GDPR. Ours applies from day one, on every plan, with nothing for you to sign.

Measurable acceptance

Agree on specific test questions. Check whether saved knowledge reaches the right tool with its source.

From Team and Business

What companies get in addition.

Setting up for companies (German) ↗

Sign-in through your company directory

From the Business plan on, you connect your company directory over OpenID Connect (Entra ID, Okta, Keycloak) yourself in the Cockpit and enter your company’s mail domains. Anyone who enters an address from one of them is sent to your company’s sign-in. Roles can be taken from the groups in your directory; if someone belongs to several, the strongest applies. If you wish, you block the sign-in link by email for your mail domains.

Each department sees its own knowledge

From the Team plan on, you create domains: areas of knowledge for a department, a product, a site or a project. In search, each person finds only the domains they belong to, plus the material without a domain. Whoever sets up domains does not need to be allowed to read their content.

You can prove who saw what

The log records which access retrieved which material, and when. Every new entry is chained to the one before it, and every hour an independent service confirms the state from outside. Anyone changing something afterwards is seen doing it. You download those confirmations and keep them. With them you prove a change yourself, without asking us. For a report to third parties you hand out a shortened log, for an auditor the complete one.

Report after an incident

For a period you choose, the report shows which material a particular access retrieved and who retrieved a particular piece of material. It comes as a JSON or CSV file.

Cockpit and emails under your name

From the Business plan on, you set name, logo and accent colour yourself; they appear in the Cockpit and in the system emails to your staff.

From use case to decision

Test the value with your project.