A live map of your servers, domains, databases and SaaS: what runs where, how it's connected, and whether it's up
xNode360 helps developers and small teams keep track of their infrastructure. Place each thing on the map as a node, draw the connections between them, and every node gets a real health check. It also tracks when your secrets and certificates expire.
Start free · Try the demo without signing up
xNode360 in numbers
- 15 nodes per map on the free plan
- 5 cloud checks per map on the free plan
- 5 check types: http, tcp, dns, tls, postgres
- 18 MCP tools for your assistant
- 0 secret values stored
Two ways to build the map.
You draw it
Start from an empty canvas and build it like a diagram, except every node can have a real health check.
- Add nodes from + Add: VPS, database, domain, service or module.
- Drag connections between nodes to say what talks to what.
- One check per node (http, tcp, dns, tls) and YAML manifest import/export.
Your AI builds it
Give your assistant the repository and its .env: it reads the configuration and fills the map for you.
- Point Claude Code, or another MCP client, at the repository.
- 18 tools to read and edit the map, import a manifest and create agents.
- One key per map, read-only if you want, with an expiry.
Real status, not a diagram
Every node with a check gets a status computed from real measurements, not declared by hand.
- Cloud checks for public sites and services; the agent for whatever sits behind a firewall.
- The agent only makes outbound connections, with no open ports, and is a standalone binary: no Node needed.
- Statuses are online, degraded, offline and unknown (no data); a node without a check stays tracked.
Secrets and expiry, without holding secrets
xNode360 keeps a reference to a secret — where it lives, when it expires, where it is replicated — never the value.
- Never the value: only name, vault type, path, expiry and owner.
- Expiry and replicas that drift after a rotation show on the node and the edge.
- A ⚠ alert in the top bar counts expired, expiring and drifted secrets.
Export and share
Explain your setup to someone without app access, or keep it in the repository.
- PNG or PDF of the whole map, not just the visible part.
- YAML or JSON manifest of the architecture, versioned with your code.
- Import is additive: rebuild a map or merge another one in.
One map per project. One that sums them all up.
The Module node stands for another one of your maps (you need several maps: they are included in the pro plan). On the root map it shows the aggregated status of the map it wraps: the worst one wins.
- Create it from + Add → Module by picking one of your other maps; loops are blocked in the picker.
- Expand the module to see the inner nodes, read-only and live, and connect one of your nodes to an inner one.
- Modules do not use your node quota. Aggregation is one level deep.
- Over MCP, modules are imported with the manifest (moduleRef): add_node does not create them.
Your AI assistant can build the map for you.
Connect your MCP client, point it at your repository and ask it to map your infrastructure. Secret values are never stored — only where they live and when they expire.
Three situations where it helps.
Independent developer
Several VPS, domains and SaaS across different providers. One map to remember what runs where, what depends on what and when the certificate expires.
Agency
One map per client and a root map with one module each (needs several maps: pro plan): see at a glance which client has a problem, then expand to find where.
Small team
Who knows what is about to expire? TLS certificates and secrets with an expiry land in the top-bar alert, with replicas to realign after a rotation.
Free and pro plans
| Free | Pro (coming soon, indicative) | |
|---|---|---|
| Maps | 1 | 10 |
| Nodes per map | 15 | 500 |
| Cloud checks (public sites and services) | 5 | 100 |
| Agents | 2 | 20 |
| Nodes monitored per agent | 10 | 200 |
| Cloud check frequency | every 10 min | every 1 min |
| Inactive map | cloud checks paused after 7 days without opening it | never paused |
Frequently asked questions.
What is a map of maps?
A Module node stands for another one of your maps. On the root map it shows the aggregated status (the worst one wins) of the map it wraps, and you can expand it to see the inner nodes read-only. Use it to keep one map per project, client or environment: it needs several maps, included in the pro plan.
How do the plans and free limits work?
xNode360 is free today. The free plan allows 1 map; per map, 15 nodes, 5 cloud checks and 2 agents; cloud checks run every 10 minutes and pause after 7 days without opening the map. A pro plan with higher limits (up to 10 maps) is planned but has no price or date yet.
What happens if the agent goes silent?
Its nodes turn degraded after 2.5 minutes and offline after 20; if the agent is paused they stay unknown. A dead agent and a dead server cannot be told apart, so the change is gradual.
Does the agent need Node on the server?
No. There is a standalone binary for Linux x64 and arm64. You need Linux with systemd and root access; the agent only makes outbound connections.
Do you store my secrets?
No. We only store references: name, where the secret lives, expiry, owner and replicas. The value stays in your vault.
Does it replace PRTG or Zabbix?
No. It checks ports, HTTP endpoints, TLS certificates, DNS and Postgres. It does not do SNMP, ICMP ping or device metrics such as CPU or temperature. It focuses on how things are connected and what is actually reachable.
Can my AI assistant build the map?
Yes, through the MCP server: point Claude Code or another MCP client at your repository and its .env. Each key works on one map only, can be read-only, and expires.