Two hosts
Each instance uses two hostnames:- The app host serves the dashboard,
/mcp,/api/, and the viewer shell at/a/{id}. - The content host serves only raw artifact files. It never sets cookies.
The sandbox
The viewer shell loads each artifact from the content host in an iframe withsandbox="allow-scripts allow-forms allow-popups allow-modals allow-downloads". It never adds allow-same-origin or allow-top-navigation, so every artifact runs in an opaque origin: it can’t read cookies, the dashboard, or other artifacts.
Every content-host response also sends Content-Security-Policy: sandbox with the same flags, so opening a content URL directly is just as isolated.
An image artifact’s file is stricter still: it’s served with its real type (image/png, image/jpeg, image/gif, image/webp or image/svg+xml), X-Content-Type-Options: nosniff, Content-Disposition: inline and Content-Security-Policy: default-src 'none'; img-src 'self' data:; style-src 'unsafe-inline'; sandbox, with no allow-scripts. A script inside an SVG never runs, even when the SVG is opened on its own, and the viewer shows images only through <img>. An image’s thumbnail is the image itself only for a PNG, JPEG, GIF or WebP of at most 200 KB and 4096 pixels a side; an SVG never becomes a thumbnail.
Private content URLs carry a signed token that expires after 10 minutes, because the content host has no session. Public artifacts need no token. Revoking a share, unsharing, or deleting an artifact refuses new content URLs immediately, but a URL that was already issued keeps working until it expires, up to 10 minutes later.
Live pages without credentials
The runtime API talks to the shell overpostMessage. The shell checks each call against the artifact’s declared capabilities and makes it with the viewer’s session. The artifact itself never holds a credential.
Login
Cloudflare Access is the identity provider, using a one-time PIN by email, or GitHub or Google if you turn them on. Open Artifacts stores no passwords. After login, the Worker issues its ownHttpOnly, Secure, SameSite=Lax session cookie that lasts 7 days. Requests that change data with that cookie must also send the header X-OA-Request: 1.
Who can see what
- Roles: the owner and admins manage members and settings. Members publish. Guests see only what’s shared with them.
- Removed members: someone an admin removes and later restores gets their space roles back, but not their old tokens or agent connections. They have to log in again, and a former admin comes back as a member.
- Shares give a person
vieweroreditoraccess by email. Editors can publish new versions, edit the title and description, and restore versions. - Only the creator can share an artifact, change its visibility, or delete it. Admins can’t see other people’s private artifacts.
- No access looks like no artifact. Anything you can’t see returns
404, never403.
Tokens
Personal access tokens look likeoa_pat_ followed by 32 characters. Only a SHA-256 hash is stored. Tokens belong to one user and can be revoked from Settings → Connections.
Audit log
Admin actions, such as changes to members, roles, spaces and the Google directory, are recorded in an audit log. The owner and admins can read and export it. Each event records who did what using account ids, and emails are looked up only when the log is read. Events are kept for 400 days. A daily job then deletes older ones; a large backlog can take a few extra days to clear.Never indexed
Public links are for sharing, not search. Both hosts sendX-Robots-Tag: noindex, nofollow on every response, and their robots.txt disallows everything except the app host’s agent guides. Only public artifacts get their real title in link previews; private links show a generic title.