Publish native formats
Send Markdown with optional assets, or a standalone HTML document. The API returns an opaque artifact URL.
Open source · v1.2.0
Private artifact delivery for AI agents
Don’t deploy Artifact Relay. Ask your agent to connect it. Hermes turns long output into readable Markdown or standalone HTML in a private library—hosted for you or self-hosted in minutes.
Managed beta — free during beta · Planned price: $24/year · Limited availability
you › Connect Artifact Relay for me. hermes › Plugin installed. Open the activation link to continue. Setup result { "configured": true, "base_url": "https://your-name.relay.lok-labs.com" }
01 / Relay
From agent output to a durable reading surface.
The publisher does not need your viewer password. Readers never receive the publisher token. Optional shares stay scoped to one artifact.
Read in a private library
A password session unlocks a mobile-ready library. Artifacts expire automatically unless pinned and can be deleted immediately.
Share only when needed
Create an expiring, revocable link for one rendered artifact. Sharing is disabled by default in the localhost setup.
02 / Product surface
A library for results worth keeping.
Long reports stop disappearing into chat history. Artifact Relay gives them a stable, focused reading surface for desktop and mobile.
Private by defaultUnauthenticated visitors see preview metadata and a login form, not artifact content.
Readable anywhereResponsive pages, bundled syntax highlighting, Mermaid, and fonts—with no CDN dependency.
Simple persistenceSQLite metadata and artifact bytes live in one Docker volume with documented backup and restore.
03 / Security contract
Concrete boundaries, not a security slogan.
Artifact Relay is a small, single-user gateway. Its controls are explicit and inspectable in the source.
Local and network modes differ on purpose.
The localhost path binds to 127.0.0.1, uses local HTTP, and keeps shares off. On a Linux VPS, the documented path puts Caddy HTTPS in front, keeps the app port on loopback, enables secure cookies, and can enable scoped shares.
- ✓Independent credentials. A bearer token publishes; a separate password opens the private viewer.
- ✓Narrow sharing. Share links grant one rendered artifact, can expire, and can be revoked. Treat the URL as a credential.
- ✓Bounded rendering. Markdown is sanitized. Standalone HTML runs in a sandboxed, opaque-origin iframe.
- ✓No CDN execution path. Mermaid, highlighting, and fonts are bundled with the release.
- ✓Operational limits. Payloads, login attempts, and concurrent Argon2 password checks are bounded.
- ✓Secret-aware bootstrap. Setup generates independent secrets, hashes the viewer password, and writes the environment file with mode
0600.
04 / Why not
Choose the boundary that matches the job.
Artifact Relay is not generic static publishing. It is for private, recurring delivery from trusted AI agents.
| Option | Good fit | Difference for this job |
|---|---|---|
| Artifact Relay | Private agent output, a durable single-user library, selective sharing | Separate publisher/viewer credentials and per-artifact expiring, revocable links are part of the product contract. |
| S3 / Pages | General files or public static sites with infrastructure flexibility | You assemble authentication, rendering, library UX, expiry, and share lifecycle yourself. |
| easl / htmldrop | Fast browser-based HTML publishing | Optimized for quick page publishing rather than a private agent-to-library workflow. |
| Hermes Telegram Artifacts | Viewing results inside a Telegram-centered Hermes flow | Artifact Relay keeps delivery channel-independent and provides its own private web library. |
| Open Artifact | Interactive artifact creation and preview workflows | A broader creation surface; Artifact Relay stays focused on receiving and reading trusted agent output. |
05 / Managed beta
Your private Artifact Relay, hosted and maintained for you.
Hermes installs the plugin, starts device authorization, stores the publish credential locally, checks the endpoint, and publishes a verification artifact. You do not handle Docker, tokens, or server configuration.
- ✓Managed beta — free during beta. Early access is limited while provisioning remains intentionally hands-on.
- ✓Planned price: $24/year. The price is shown before you request access; no payment is collected during beta.
- ✓Isolated instance. Each early customer gets a separate container, volume, hostname, and credentials.
- ✓Maintained for you. HTTPS, upgrades, backups, monitoring, and recovery are part of the managed service.
06 / Self-host
Prefer to run it yourself?
Docker Compose remains the supported self-hosted path. Start on localhost, or move to a Linux VPS with HTTPS when you need remote access and sharing.
Localhost
Private on one machine: loopback binding and sharing off by default.
git clone https://github.com/eloktev/artifact-relay.git cd artifact-relay docker build -t artifact-relay:1.2.0 . ./scripts/bootstrap.sh docker compose up -d curl -fsS http://localhost:8000/api/health
Linux VPS
Internet-facing with Caddy TLS, secure cookies, and the app kept on loopback.
# Set your HTTPS origin and domain first docker compose \ -f docker-compose.yml \ -f deploy/compose.vps.yml config docker compose \ -f docker-compose.yml \ -f deploy/compose.vps.yml up -d
07 / Hermes Agent
Give Hermes a private delivery path.
The portable plugin registers two tools and includes a skill that turns long results into concise private links. Hosted setup uses device authorization and keeps the publish credential out of the browser, chat, model output, and ordinary config.
artifact_publishartifact_read
hermes plugins install eloktev/hermes-artifact-relay hermes artifact-relay setup
Artifact Relay v1.2.0
Ask your agent to connect it.
Use the managed beta when you want the private library without operating a server, or inspect the source and self-host the same artifact service.