Artifacts

An artifact is any file or piece of content CloudPeek stores for you: a log you uploaded, a report the AI generated, an exported investigation result. Artifacts are kept in one place, made searchable, and linked to the incident or investigation they belong to.

Open them from the sidebar → Artifacts (/artifacts).

What becomes an artifact

Uploads: files you add yourself (logs, evidence, documents).
AI-generated content: reports and outputs the agent produces during an investigation.
Exports: when you click Export Results in an investigation, the result is saved as an artifact.

The Artifacts screen

The Artifacts page lists your artifacts in a table. For each you can see its details and:

Download the original file.
Link it to a target (an incident or investigation): or unlink it.
Delete it.
Retry processing if indexing didn't complete.

Search, including by meaning

Artifacts aren't just stored, they're indexed. Beyond ordinary listing, CloudPeek supports semantic search: finding content by meaning rather than exact keywords. That means you can search for the concept you remember ("failed VPN logins from overseas") and find the relevant artifact even if it used different words. The search runs over the artifact contents.

How artifacts connect to your work

Files attached to an incident show up on that incident's view (see Incident Management).
An investigation's exported results and generated reports are linked back to that investigation (see Investigations).
Because artifacts are indexed, the AI can also draw on their contents as context.

Visibility

Artifacts respect your tenant's isolation, they belong to your tenant and are only visible within it. When created, an artifact has a visibility setting (for example scoped to a specific target) that controls where it appears.

Artifacts API: upload, list, download, link and semantically search artifacts programmatically (including batch/ZIP uploads).
Investigations: the main source of generated artifacts.