03
画面
PRODUCT · TOUR
The observatory, in motion.
Seizu turns your Neo4j graph — cloud inventory, identities, vulnerabilities, relationships — into dashboards, ad-hoc Cypher, and an MCP endpoint for the agents investigating alongside you.
Seizu (星図) is the Japanese word for star chart. It's also a React + Python frontend for Neo4j graph databases — built for humans who need to navigate sprawling infrastructure graphs, and for the LLM agents that investigate them alongside you.
Point it at a Cartography graph and you get dashboards, ad-hoc Cypher, scheduled reporting, and an MCP endpoint your agents can query — all from one configuration.
Assemble dashboards and reports visually, the way you would in Grafana — rows, panels, charts, tables, graphs. Config can still be imported and exported as code.
Interactive Cypher with graph, table, and raw result views. A collapsible schema browser shows every node label, relationship, and property key.
Expose user-defined Cypher-backed tools at /api/v1/mcp. Claude and other agents investigate your graph the way your analysts do.
Run queries on a schedule or trigger them from graph changes. Route results to Slack, SQS, or any action plugin.
Watch for interesting changes in the graph — a new admin policy, a fresh CVE on a production host — and fan out to downstream action plugins.
Native JWT authentication — point Seizu at your identity provider and inherit SSO for Neo4j itself. No proxy required.
Seizu pairs naturally with cartography (CNCF) and Starbase. Cartography ingests your cloud, identity, and SaaS inventory into Neo4j — Seizu is the lens that makes it legible.
MATCH (u:AWSUser)-[:MEMBER_OF*0..]->(g)
-[:POLICY]->(p:AWSPolicy)
WHERE p.admin = true AND u.mfa = false
RETURN u.arn, g.name, p.name
Seizu ships an MCP server at /api/v1/mcp. Define Cypher-backed
tools in YAML, and Claude, Cursor, or any MCP-aware agent can investigate your graph the way a
security engineer would — but at machine scale.
investigate_vulnerabilities()
audit_iam_posture()
trace_blast_radius()
“When an IAM user gets an admin-policy attached, who approved it and what can they reach?”
“Which internet-facing workloads still have CVE-2024-XXXX, and which identities can access them?”
“What changed in our blast radius since last Tuesday?”
“If this GitHub token leaks, what production resources are reachable?”
Spin up Seizu with docker-compose in under ten minutes, point it at your Neo4j instance, and start seeing your infrastructure the way it actually connects.