Cloud Infrastructure — a new App that keeps one catalogue of every server, virtual machine, service, API, database, storage volume, IP address, load balancer and certificate the company runs, with its environment (production, staging, development, DR), criticality, provider, region, specs and owner client/project.
Cloud Infrastructure: relationships — an asset links to the records other Apps already hold: Password Manager credentials, Terminal connections, NizuUptime monitors, Crudy databases, DomainManager domains, clients, projects, files, tickets and tasks. Nothing is copied; each App keeps owning its own data, and a link to an App that is switched off simply shows as unavailable.
Cloud Infrastructure: costs — every asset carries its planned cost and billing cycle. "Post to expenses" books it once in the Expenses module as a recurring expense (net amount plus tax), linked both ways, and the platform generates every following cycle. Billable assets recharge to the client through the normal expense-to-invoice flow.
Cloud Infrastructure: reports and reconciliation — monthly and yearly run-rate by client, project, provider, environment and type; and a read-only reconciliation screen comparing each provider's planned cost with the expenses posted in a month, listing assets with no expense and decommissioned assets whose expense still recurs.
Cloud Infrastructure: dashboard findings — critical assets without an uptime monitor, decommissioned assets still costing money, renewals due, and a warning on the asset page when a linked credential or monitor disagrees about the host.
Cloud Infrastructure: fleet tiles for the general dashboard — eleven widgets to add to any dashboard (Edit dashboard → Add widget): managed devices, cloud consumption per month (with the yearly figure), cloud providers, CPUs, total RAM, total disk, IP addresses (IPv4 / IPv6), architectures in use (ARM, x86, x86-64), GPUs, firewalls, and live CPU usage — the load reported by the NizuUptime heartbeats of the monitors linked to your assets, weighted by cores. Decommissioned assets never count; the cost tile follows the "view costs" permission.
Cloud Infrastructure: GPUs and firewalls — an asset now records how many GPUs it has (form, CSV import, detail pages, Marvin), and Firewall is a new asset type. Provider sync brings both in: firewalls from Hetzner Cloud, DigitalOcean, Vultr and Linode, and GPU counts from DigitalOcean, Vultr and Linode.
Cloud Infrastructure: provider sync — compare the catalogue with Hetzner Cloud, DigitalOcean, Vultr, Linode and Infomaniak. Always a diff first; you tick what to apply, and an asset that vanished at the provider is proposed for decommission, never deleted. A Credentials button on each provider chooses which API it speaks and holds its API keys — as many as you need: Hetzner tokens are scoped to one project, so add one key per project and every sync reads them all. Each key is tested when saved and keeps its last result; the diff shows which key sees each asset, and a key that stops answering is reported without proposing its assets as vanished. An existing token becomes the provider's "Default" key automatically.
Cloud Infrastructure: uptime — create a NizuUptime monitor for an asset from its Monitoring tab (linked and checked immediately), link one that already watches the host, or re-check on demand; every asset list shows an Up / Down badge, the dashboard shows what is down now, and one click matches existing monitors to assets by hostname or IP.
Cloud Infrastructure: CSV import — move a spreadsheet in with a preview of what will be created or updated before anything is written.
Cloud Infrastructure: client portal — optionally let client contacts see the assets run for their own company, with separate switches for specs, costs and monitoring status. Credentials are never shown to clients.
Cloud Infrastructure: daily check — an optional daily digest by email (and Telegram) of renewals due, warranties ending, decommissioned assets still costing and critical assets without a monitor.
Cloud Infrastructure: Marvin and Agents — ask Marvin about an asset by name, and give connected AI agents the asset list, asset detail and cost report tools.
Cloud Infrastructure: activity history — every change to an asset is recorded field by field, with who changed it and when.
Isometric Schema — a new App to draw your infrastructure on an isometric grid (servers, databases, load balancers, connectors, coloured regions, text), based on the open-source isoflow/FossFLOW editor and running entirely inside NIZU — no external service, no data leaves the workspace.
Isometric Schema: live links — any drawn item can be linked to a real record: a Cloud Infrastructure asset, a client, a project, a Password Manager server, a domain, a Crudy database, a NIZU Events endpoint, a Terminal connection or an uptime monitor. The item then shows the record's name and a live status pill on the canvas (environment, expiry, up/down…), and clicking it opens a side panel with the record's details and shortcuts (open the terminal, open the domain, browse the database…). Credentials are never shown.
Isometric Schema: nothing breaks when records change — a linked record that gets deleted is not removed from the drawing: the item greys out and gets a trash-can mark so you decide what to do. A record you may not see shows as "unlinked".
Isometric Schema: import from Cloud Infrastructure — one click adds a new view with every asset you can see, already linked and connected. The layout is made to be read: elements at least four tiles apart, a firewall that connects several elements placed in the centre, the other elements in rings around the best-connected one with their links fanning out instead of crossing, network interfaces and storage volumes tucked one block behind their server, one colour per kind of relation and no words on the lines, one region per client. Providers, credentials and other paperwork never appear on the canvas. Re-importing refreshes the elements already on the drawing.
Isometric Schema: autosave, history and exports — changes are saved automatically, every explicit Save keeps a version you can restore, and a schema exports as PNG or JSON. A conflict with someone else's save is detected and you choose to reload or overwrite.
Isometric Schema: sharing — each schema is visible to everyone with the permission, or only to named members and teams, as editors or viewers; a "Shared with me" tab lists what colleagues shared with you. Administrators and the creator always keep full access.
Isometric Schema: branded export — Download as PNG produces a high-resolution picture cropped to the drawing with the schema name, the company name and the date; list thumbnails are cropped the same way. Live statuses now refresh in the editor as well as in the viewer, and every save/link is available to NIZU Events webhooks. The App speaks all 14 workspace languages.
Isometric Schema: everywhere it belongs — a Schemas tab on each project, a read-only view for client contacts of the company a schema belongs to (portal switch in Client permissions), role permissions for viewing, editing and settings, and full dark mode.
Updates
Labels can now be attached to Cloud Infrastructure assets through the shared label system.
Projects and clients gain an Infrastructure tab listing the assets that run for them.
