Database Schema

Entity relationship diagram and table reference for Scanopy's PostgreSQL database.

Scanopy uses PostgreSQL to store all network discovery data. This page provides an overview of the database schema and entity relationships.

Entity Relationship Diagram

Table	Purpose
`organizations`	Manage organization settings.
`users`	User account management.
`invites`	Organization invitations.
`user_api_keys`	User API keys for programmatic access.

Table	Purpose
`networks`	Network containers.
`hosts`	Network hosts (devices).
`subnets`	IP subnets within networks.
`ip_addresses`	IP addresses assigned to hosts.
`ports`	Ports that have been scanned and found open on a host.
`services`	Services running on hosts.
`bindings`	Service bindings linking services to IP addresses and/or ports.
`interfaces`	SNMP ifTable entries.

Table	Purpose
`daemons`	Daemons are scanning agents that connect to the server to perform network discovery.
`api_keys`	API keys for daemon authentication.
`discovery`	Network discovery operations.

Table	Purpose
`dependencies`	Service dependency relationships.
`topologies`	Network topology maps showing host relationships and connections.
`shares`	Shared network views.

Table	Purpose
`tags`	Custom tags for categorization.

The discovery pipeline creates this hierarchy:

This structure allows a single service to be accessible on multiple interfaces (e.g., a database listening on both LAN and Docker bridge networks).

All discovery data is scoped to a network:

Hosts, subnets, services, interfaces, ports, and bindings all have a network_id foreign key
Networks belong to organizations
Users are granted access to specific networks via user_network_access

Most foreign keys use ON DELETE CASCADE:

For the complete schema with all columns and types, see the detailed ER diagram below. Use the zoom controls or fullscreen mode to explore.