Skip to content
Gadsotek edited this page Jul 17, 2026 · 3 revisions

ArtifactFlow

A self-hosted vault for storing, versioning, searching, and previewing untrusted AI-generated HTML artifacts and Markdown. Generated code runs isolated in a two-origin sandbox, never on your application.

AI tools now produce dashboards, diagrams, runbooks, and one-file HTML apps by the dozen. Those artifacts are untrusted code: you cannot open them on a page that carries your session cookie. ArtifactFlow is the place to keep them, an internal knowledge base where AI-generated Markdown and single-file HTML stay searchable, versioned, and runnable, without ever letting untrusted HTML execute on your authenticated origin.

The core idea: containment by isolation, not sanitization

Most tools try to scrub untrusted HTML clean. ArtifactFlow does not trust scrubbing. It quarantines execution to a separate origin:

  • App origin: your authenticated, cookie-bearing surface. Untrusted artifact bytes never execute here, not even the pre-save draft preview.
  • Artifact-host origin: cookieless, on a different host. Artifacts render inside a sandboxed iframe under a strict Content Security Policy with no network and no same-origin access. Saved artifacts are reached through short-lived HMAC-signed URLs.

The artifact's JavaScript really runs, but in an opaque origin with no cookies and no reach back to your app, with the ordinary network APIs blocked (the threat model documents the residual, browser-dependent egress vectors). Isolation is the boundary; scanning is only advisory on top.

Start here

Status

Alpha. The security model and feature set are implemented and have been through repeated internal, AI-assisted adversarial review (not an independent third-party audit). Expect changes, and pin a revision for anything you depend on.

Project links

Clone this wiki locally