Skip to Content
🧩

Integrations

Updated 2026-11-20

Settings > Accounting > Service Costing. Each integration installs when you tick it and save. Once installed, each one can be switched off again for a company in the same place, without uninstalling it.

IntegrationWhat it adds
Occupancy from subscriptionsActive subscription lines fill the pools: each line uses the outputs of its product and brings its monthly amount as revenue. A cancelled subscription stays an occupant until the end of its period.
Equipment and maintenanceCapacity groups are built from your equipment. Equipment that is out of service is taken out of the room left, and the cost of maintenance becomes a cost of the pool (Maintenance (12-month average)).
Change managementA change request shows the customers, revenue and capacity it affects. Attach a scenario so approvers see what it does to costs and prices; once the change is done, you choose whether to apply it.
Helpdesk cost to serveTime spent on tickets becomes a cost of the pool (Support time (12-month average)), and each customer shows its Margin after Support. Tickets show the Room Left in the customer's pool.
Compliance scope and evidencePools join the scope of a compliance profile, and capacity management evidence is collected every month: occupancy, room left and alerts.
DashboardA spreadsheet dashboard of costs, revenue, occupancy and unit costs across your pools.
SaaS templatesReady-made pools for a software service: hosting, licences and staff per seat or per customer.
Cloud and hosting templatesReady-made pools for servers, storage with replication or erasure coding, IP addresses and Kubernetes clusters.

Note: If you deploy to a Kubernetes cluster from Lynx, a pool can follow that cluster: its nodes give the capacity, and its Namespaces tab lists every namespace with its requests and a role. A customer namespace is paid by one subscription or several; your own namespaces go to their cost centre; the platform and free shared services are shared overhead; a Sold service runs in the Service Pool you choose, which buys its capacity from the cluster. New namespaces take their role from the System, Shared Service and Own Use Namespaces patterns on the pool, and keep the role you set. An add-on priced in another pool counts there, not twice.

Was this article helpful?
Thank you for your feedback. Still stuck? Contact us