Friday, 18 September 2026, 11:23 AM
Created by: Ruvenss G. Wilches
NIZU Cloud Infrastructure is an App for NIZU Cloud WorkSpace that keeps one catalogue of everything your company runs: servers, virtual machines, services, APIs, databases, storage volumes, IP addresses, load balancers, certificates and SaaS subscriptions. Each one is an asset with an environment (production, staging, development, disaster recovery), a criticality, a provider and region, its specs, the client and project it is run for, and what it costs.
What makes it different from a spreadsheet is the relationships. An asset in Cloud Infrastructure points at the records other Apps already hold: the credentials in Password Manager, the SSH connection in Terminal, the uptime monitor in NizuUptime, the database in Crudy, the domain in DomainManager, the client, the project, the expenses, the files. Nothing is copied. Each App keeps owning its own data, and Cloud Infrastructure draws the lines between them.
Infrastructure and IT teams inside a company, and managed service providers and agencies that run servers and services for their clients. If you have ever asked "which server does this client's shop run on, who has the password, is anyone monitoring it, and what does it cost us per month?" and had to open four tools to answer, this is the App that answers it in one place.
Every asset has a type, an environment and a criticality. The dashboard tells you at a glance how many assets are active, what the monthly run-rate is, what renews in the next thirty days, and — the two findings that justify the whole App — which critical assets have no uptime monitor and which decommissioned assets are still costing money.
Each asset carries a planned cost and billing cycle. One click posts it into the Expenses module as a recurring expense, and NIZU generates every following cycle by itself. Billable assets are recharged to the client through the normal expense-to-invoice flow. A reconciliation screen compares, per provider and per month, what you planned to pay with what was actually posted.
If your provider is Hetzner Cloud, DigitalOcean, Vultr, Linode or Infomaniak, Cloud Infrastructure can compare your catalogue with the provider's API. It always shows the differences first; you tick what to apply. An asset that vanished at the provider is proposed for decommission — it is never deleted.
Every edit to an asset is recorded field by field, with who made it and when. Six months later, "who changed the IP of the production database?" has an answer.
Optionally, client contacts can see the assets run for their own company, with separate switches for specs, costs and monitoring status. Credentials are never shown to a client, whatever is switched on.
It is not a monitoring tool (NizuUptime does that), not a password vault (Password Manager does that) and not a terminal (Terminal does that). It is the map that shows how those pieces fit together, and the ledger that says what the whole thing costs.