Your map lives in your workspace and is only visible to members you invite. Imports run with credentials you control — Phanes stores the topology (hosts, processes, ports, edges), not your secrets. You can delete a board or your account at any time.

No — that's the point. Every workspace starts with a set of generic defaults (service, database, queue, cache, load balancer, domain, external API, and so on), and you edit the catalog freely: add your own types with their own icons and colours, rename or remove ones you don't use. A node's type is just a reference to your catalog, so you can model any stack.

Phanes is a remote MCP server you connect over OAuth — add the connector with "claude mcp add --transport http phanes https://api.phanes.dev/mcp", then sign in and approve access in your browser once. No API keys to manage. Claude can then read your board and catalog and write to both: scan a server over SSH, pull cloud inventory, define a new resource type, and update nodes and edges accordingly. Every change it makes is attributed to the import in the timeline.

Yes. Built-in importers bring in AWS (instances, security groups, IAM roles) and Tailscale (devices, mesh links, ACLs); server scans over SSH discover processes and listening ports. Beyond those, Claude can record anything you describe using your own types, so you're not limited to a fixed list of vendors.

Your boards switch to read-only — nothing is deleted. You can still view and trace the map; subscribe to keep editing and importing.

Not yet. Phanes is currently cloud-hosted only. If on-prem matters for your team, tell us at support@phanes.dev — it helps us prioritize.