Node Types

DataParade supports four canvas node classes:

• asset
  A system or technical component that stores, processes, or transmits data.
• actor
  A human or automated identity that interacts with assets and data flows.
• third_party_service
  An external organization or service outside your direct control.
• generic_shape
  A visual-only diagram element used for annotation or structure, not entity modeling.

Each class has its own properties reference under Node Properties. For workspace-wide management of asset and third-party records, see the Data Catalog.

Asset Types

Canonical asset type values:

• application
  A deployable software application (web, desktop, or backend app).
• api
  A programmatic interface exposing data or operations to other systems.
• cloud_storage
  Cloud-managed object or file storage used to persist data.
• data_source
  A source system that provides input data to your architecture.
• database
  A structured datastore (SQL or NoSQL) for persistent records.
• file_system
  Local or network file storage organized as files and directories.
• infrastructure
  Underlying compute/network foundation such as hosts, clusters, or runtime infrastructure.
• iot_device
  A connected physical device that collects, sends, or receives data.
• mcp_server
  A Model Context Protocol server exposing tools/resources to AI clients.
• mobile_app
  A native or cross-platform mobile client application.
• other
  An asset that does not fit existing predefined categories.
• platform
  A foundational environment on which applications or services run.
• processing_node
  A component focused on transforming, enriching, or routing data.
• saas
  A software-as-a-service application consumed over the internet.
• service
  A backend service or microservice with defined runtime responsibilities.
• storage_node
  A storage-focused component in data flow modeling.
• website
  A browser-facing web property or frontend site.

Actor Types

Current actor type values:

• customer
  An end customer using your product or service.
• employee
  An internal staff member operating within the organization.
• privileged_user
  A user with elevated permissions (for example admin or superuser).
• developer
  An engineer building, deploying, or maintaining technical systems.
• support_agent
  A support role handling incidents, tickets, and user assistance.
• data_analyst
  A role focused on querying, interpreting, and reporting data insights.
• contractor
  A non-employee contributor with scoped or temporary access.
• automated_service
  A non-human service identity acting automatically in workflows.
• api_consumer
  A client system or role consuming exposed APIs.
• auditor
  A reviewer validating controls, compliance, or operational evidence.
• other
  An actor that does not fit existing predefined categories.

Legacy actor values may still appear in old diagrams (end_user, internal, third_party_support, service_account).

Third-Party Types

Current third-party type values include:

• b2b_customer
  A business customer organization that receives your services.
• saas_service
  An external SaaS vendor integrated into your workflows.
• payment_processor
  A provider that processes or settles payment transactions.
• cloud_provider
  An external cloud vendor supplying infrastructure services.
• api_provider
  A third party exposing APIs your system depends on.
• ai_provider
  A third-party AI or model platform used for inference or tooling.
• data_provider
  A provider that supplies datasets, feeds, or enrichment inputs.
• government_regulator
  A regulatory authority interacting through compliance obligations.
• partner
  A strategic or operational partner organization collaborating with your business.
• ad_network
  An advertising platform involved in ad delivery or attribution.
• professional_services
  External consultants, legal advisors, or managed service providers.
• other
  A third party that does not fit existing predefined categories.

Legacy compatibility values may still appear in existing data.

Generic Shape Kinds

Generic shape nodes support visual-only kinds such as:

• rectangle
  General-purpose container or grouping shape.
• diamond
  Decision or branch point visual marker.
• ellipse
  Rounded highlight for conceptual or logical grouping.
• text_box
  Freeform annotation node for explanatory text.