Friday, 18 September 2026, 11:28 AM
Created by: Ruvenss G. Wilches
Cloud Infrastructure does not copy data from other Apps. It links to their records, and each App keeps owning its own. When an App is not installed, its link type simply does not appear; an existing link to an App that was switched off shows as unavailable instead of breaking the page.
Every asset can belong to a client. The client's page gains an Infrastructure tab listing the assets run for them, and an Infrastructure access tab where staff decide what each of the client's contacts may see in the portal.
Every asset can belong to a project, and can be linked to more. The project page gains an Infrastructure tab, visible to staff and — when the portal is on — to the client's contacts.
The asset's planned cost is posted into the Expenses module as a (recurring) expense, linked both ways. Billable expenses can be added to the client's invoice from Expenses. The reconciliation screen reads the posted expenses back per provider and per month.
Files from the file manager — contracts, diagrams, provider invoices — can be linked to an asset and are listed on its Files tab.
A ticket or a task can be linked to an asset as documentation of an incident or a change; a team member can be linked as its owner.
Assets have their own label context in the shared label system.
The App adds its own permission group to the role editor.
An overview widget shows the monthly run-rate (or the active asset count for staff who may not see costs), renewals due and critical assets without a monitor. Eleven more tiles are offered when you edit a dashboard (Dashboard → Edit → Add widget): managed devices, cloud consumption per month, cloud providers, CPUs, total RAM, total disk, IP addresses, architectures (ARM, x86, x86-64), GPUs, firewalls and CPU usage. Every figure counts the assets that are not decommissioned. The cost tile needs the "view costs" permission, and CPU usage is the live, core-weighted load reported by the NizuUptime heartbeats of the monitors linked to your assets — it appears only while NizuUptime is active, and reads "no host is sending a heartbeat yet" until a linked monitor reports.
The provider of an asset is a row in the Providers App. The provider's API token, stored there, is what the provider sync uses. Reconciliation groups by provider.
Server credentials and API keys are linked to an asset as "credentials for". They are shown on the Credentials tab to staff only and never to a client.
A Terminal connection is linked as "SSH access" and opens the console from the asset page. Staff only.
An uptime monitor is linked as "monitors". From the asset's Monitoring tab you can create a monitor in NizuUptime (linked and checked immediately), link one that already watches the host, or re-check on demand; the dashboard can match monitors to assets by host in one click. Every list shows an Up / Down badge per asset, the dashboard lists what is down now and flags critical assets with no monitor linked. NizuUptime keeps owning the checks, the schedule and the alerts.
A Crudy database connection is linked as "stores data for". Staff only.
A domain is linked as "serves" — the asset serves the domain.
Marvin can answer questions about an asset by name or hostname, and list the infrastructure of the active project, with the permissions of the person asking.
Three tools are registered for AI agents: list assets, get an asset, and the cost report.
The daily digest is also posted to the configured Telegram chat.
Cloud Infrastructure publishes the asset graph (nodes and edges) that the Isometric Schema App draws.