Application auto-discovery
How Kabeen AI automatically identifies the applications actually used across your organization
Overview
Kabeen AI continuously watches the usage reported by the Kabeen agents (browser extension and workstation agent) and matches it against a catalogue of more than 80,000 business applications to build your application inventory automatically.
You have nothing to declare by hand: the applications your colleagues use every day show up on their own, with a description, a category and a criticality level.
Discovery runs as long as the Applications feature is enabled in Settings › Kabeen AI, which it is by default.
How it works
1. Collection
The browser extension and the workstation agent report the websites and software your colleagues use. Only usage that isn't attached to an application of your inventory is examined: an application already in your inventory isn't discovered again.
2. Grouping
Usage is grouped by candidate application. A candidate is usually a website's domain, for example example.com. For a platform shared by several companies (acme.zendesk.com) or shared hosting, the exact address counts; for software, it's its program.
For each candidate, Kabeen counts the users, the teams and the days of use.
3. Catalogue recognition
Each candidate is first compared with the Kabeen catalogue. An application the catalogue knows is recognised without further analysis. During the first weeks, a well-identified catalogue application can even appear as soon as it is first used.
4. Filtering
For the other candidates, only significant usage is kept. The threshold depends on your workspace's phase (see "Discovery pace" below):
| Phase | Minimum usage |
|---|---|
| Start-up | 1 user |
| Ramp-up | 2 users, on 2 different days |
| Steady state | 3 users from 2 different teams, on 3 different days, or 5% of the workspace's active users over the last 30 days |
In every phase, a website seen by a single user on a single day waits for a second user or a second day, unless it is a well-identified catalogue application.
These are also set aside:
- pages opened from a link someone sent: e-signature, file sharing, survey, unsubscribe…;
- the marketing pages of a site with no real use (pricing, features, blog);
- the sign-in, help or status pages of a known vendor;
- local addresses (
localhost).
5. AI analysis
Candidates the catalogue doesn't recognise are examined by an AI, using the provider chosen in Settings › Kabeen AI. It determines what they are:
| Nature | Added to the inventory |
|---|---|
| Business application | Yes |
| Internal application, built by or for your organisation | Yes |
| A client's or partner's system | No |
| Personal service (social networks, shopping, travel…) | No |
| Service that is both personal and professional (banking, insurance, government…) | No |
| Infrastructure | No |
| Advertising and tracking | No |
| Media | No |
| Search engine or portal | No |
| Company website (showcase site) | No |
A candidate whose nature remains uncertain isn't added: it will be examined again later. A domain already classified isn't analysed a second time.
For details on AI processing, see Use of artificial intelligence.
6. Creation
Only business applications and internal applications are added to your inventory, in the Discovery state; plain websites people visited are set aside. If the product is already in your inventory, whatever its state, Kabeen adds the new address to it instead of creating a duplicate.
As soon as it is created, the discovered application's usage is tracked like that of your other applications.
7. Qualification
Each discovered application gets a description (the Prism analysis, see below), a criticality (low, medium or high) based on its business function and its usage, and a category when a matching category exists in your workspace.
As long as the application stays in the Discovery state, Kabeen updates this information regularly. Validate it before editing it yourself: otherwise, your changes may be replaced.
8. Your decision
You stay in control: each discovered application waits for your decision. You validate, tolerate, refuse or archive it (see below). Kabeen doesn't go back on your decisions: a refused or archived application is never re-created by discovery. A deleted application, however, can reappear if it is still in use.
Discovery pace
Discovery is intensive during the first days, to build your inventory, then runs continuously to spot new tools:
| Phase | Period | Frequency |
|---|---|---|
| Start-up | The first 14 days, then as long as your inventory holds fewer than 20 validated, tolerated or refused applications | Every hour. The first analysis looks back over the last 30 days of usage. |
| Ramp-up | Until the workspace is 60 days old | Every 6 hours |
| Steady state | After that | Once a day |
Discovery pauses in a workspace with no usage at all for 30 days, and resumes as soon as usage comes back.
Reviewing and sorting discovered applications
- Open Applications, then the Discovery tab. Each discovered application shows there as a card, with its usage statistics and its Prism analysis.
- For each application, choose where to move it:
- Move to validated applications;
- Move to tolerated applications;
- Move to refused applications: the application stays in your inventory, in the Refused state;
- Move to the archives: the application leaves your inventory.
An application archived from discovery is in the application archives, From discovery tab.
Prism analysis
Each discovered application can come with a Prism analysis: a one- or two-sentence summary of its business use. The analysis also suggests a category and a criticality for the application. It shows in two places:
- on the application's discovery card (the Discovery tab of applications), under its statistics. When the summary is cut, See more unfolds it and See less folds it back;
- in the discovered application's panel, which opens from its card or from the list of discovered applications: its Prism analysis section shows the full summary.
The Prism analysis is rolling out gradually, starting with new workspaces.
Discovery timeline
During the first weeks, a well-identified catalogue application can appear a few minutes after it is first used. Other applications appear once their usage is deemed significant and their nature analysed, usually from the day after they are first used. Their description and criticality come a little later.
Best practices
- Sort discovered applications as they come, and validate them before editing their description or criticality.
- Check the Discovery tab regularly: new SaaS tools adopted by teams show up there as they go, with no IT action.
- Add tools used by one or two people by hand: in steady state, discovery only keeps shared usage.
- Combine auto-discovery with adding applications from the catalogue for very recent or very specific applications.
Privacy
For details on the data discovery uses and on AI processing, see Use of artificial intelligence and Data Privacy.