Applications

Application management answers the question: what does an application really cost us? Each application (e.g. your SAP system) bundles contracts, licenses, cloud costs and VMs into a complete cost structure — the overview shows each application's cost/month at a glance.

Creating an application

Open Applications and click New application. You record:

• App code — the unique identifier (e.g. SAP-ERP)
• Name and description
• Vendor — chosen from the suppliers (with inline creation)
• Status (Planned, Active, Deprecated, Retired) and criticality (Low/Medium/High)
• Cost center and optionally an owner

The cost structure

The detail view of each application shows the monthly costs from four sources:

Source	Assignment
Contracts	Contract → application (on the contract or via Assign in the detail view)
Licenses	License SKU → application (in the license module or the detail view); cost = assigned units × price/month
Cloud	automatic via scope or tag mapping
VMs	automatic via tag mapping; cost = resources × chargeback prices

The sum yields the application cost per month — the basis for make-or-buy decisions, allocations and portfolio assessments.

App tags (automatic mapping)

For the automatic assignment of cloud resources and VMs, maintain one or more app tags (e.g. sap-erp) under Tags in the detail view. If cloud resources or VMs carry this tag, Contrixt assigns their costs to the right application on every sync — permanently and without manual work.

Tagging convention

Establish a company-wide tag convention (e.g. tag key contrixt-app, value = app tag) and maintain it in Azure/AWS/GCP/Hetzner and on the VMs. Once established, every new resource automatically flows into the right cost structure.

SaaS discovery

Under Administration → Integrations you'll find the SaaS discovery section with four configurable sources: Microsoft Entra, GitHub, Atlassian and Zoom. Each active source automatically detects which cloud apps are in use across your company — including ones you haven't recorded as an application in Contrixt yet. This brings shadow IT to light before it becomes a cost risk.

• Microsoft Entra detects which cloud apps your employees sign into via single sign-on (Entra enterprise apps).
• GitHub detects the apps and integrations installed in your GitHub organization. Provide a personal access token and your GitHub organization name.
• Atlassian detects the Atlassian products in use across your organization (e.g. Jira, Confluence). Provide an organization API key, which you create at admin.atlassian.com → Settings → API keys, and your organization ID.
• Zoom detects the Marketplace apps installed in your Zoom account. Provide the credentials of a server-to-server OAuth app from the Zoom App Marketplace (account ID, client ID and client secret).

On Applications you'll find the Discovered SaaS card — now with a source column showing whether each detected app was found via Entra, GitHub, Atlassian or Zoom:

• Sync now loads the current data from all connected sources. Contrixt automatically filters out Microsoft's own base services (Teams, SharePoint, Exchange, Power Platform and similar) — they are not shadow IT.
• Contrixt tries to match each detected app to an already recorded application by name. Unmatched apps are highlighted in amber ("Unmatched") — worth checking whether the application is missing or deliberately used.
• Use the dropdown in each row to manually assign a detected app to an application (or clear the assignment again) — this works the same way across all sources.
• Apps that don't need an application assignment (e.g. internal test accounts) can be hidden via Ignore — they then appear in the collapsible Ignored section and can be shown again there at any time.

Practical benefit

SaaS discovery surfaces unplanned cloud spend before it shows up in contracts or invoices — a simple first step toward shadow IT control, with no extra agent required. The more sources you connect, the more complete the picture.