Skip to main content

Content

Content is the authored, version-controlled resources you build in Perpetual.

Deployable content participates in Perpetual's processing workflow and produces or contributes to associated datasets. The remaining content resource types read query results, hold configuration, or define how Perpetual presents and acts on information. This category also documents the Spaces, folders, changesets, and content packs that scope, organize, version, and distribute content.

Shared mechanics​

These facts hold across every content resource.

  • Space-scoped. A content resource's spaceId identifies its Space. Each Space limits access to its content to a subset of the organization's users.
  • Folder-organized. A content resource's folderPath, such as Detections/AWS, identifies its place in the folder hierarchy within its Space. Folders are for organization only. They group content for browsing and do not change how it runs. A resource with no folder sits at the Space root.
  • Version-controlled. You stage mutually dependent edits to content resources in a changeset, then apply them together with one commit. Each commit increments a resource's version.

Content and supporting structures​

  • Deployable content is processing logic that can produce or contribute to an associated dataset.
  • Dashboards visualize the results of queries over a Space's datasets.
  • Webhooks send outbound HTTP requests when platform events fire.
  • Credentials hold the encrypted secrets that authorize outbound connections.
  • HTTP Tools define HTTP requests the Simba agent can call.
  • MCP Servers connect the Simba agent to remote Model Context Protocol tools.
  • Skills provide named instruction sets for the Simba agent.
  • Spaces scope content, datasets, and access within an organization.
  • Folders organize content within a Space.
  • Changesets stage content edits and apply them together on commit.
  • Content packs bundle reusable content for installation into one or more Spaces.