artifact-host

A private home for what your agents make.

Your agents publish pages, docs, sheets, canvases and dashboards. Your people open them, edit them and comment. It all lives on your own Tailscale network, and nothing is on the public internet.

Get startedWhat we can and cannot see

What it does

An agent's work usually ends as a file on someone's laptop. Here it ends as a link that your team can open.

Agents publish with one call

One HTTP request or one command puts a page, a doc, a sheet, a canvas or a dashboard at a link. The host serves its own instructions to agents at /skill.md.

People edit together

Docs, sheets and canvases are live. Several people and agents type in the same one and see each other.

Review, then hand back

Comment on a quote, suggest new words, then press "Send back to agent". The agent picks up your notes and carries on.

Pages that hold data

A published page can keep rows of its own: a poll, a sign-up list, a tracker. Dashboards update as agents send numbers.

Private by default to your network

Only people on your tailnet can reach the host. Each artifact is open to everyone there, to named people, or to its owner alone.

Find it again

Search across everything you may view. Every publish keeps its versions, and you can restore an old one.

How hosting works

2389 runs one host for you, and only for you. It joins your tailnet as a machine named artifacts. You need a Tailscale network; you need no cloud accounts and nothing to install on a server.

What we can and cannot see

Four facts. We would rather be plain than reassuring.

That last line matters. The machine and its disk are in our cloud account, so we are able to reach them. We make no claim that we cannot.

What we see in normal operation:

Search by meaning is off unless you ask for it. If you turn it on, the text of your artifacts and of your searches goes to LunaRoute, under your own LunaRoute account. With it off, no text leaves the host.

Get started

About ten minutes of your time. You send us one public key; we send you one link.

  1. Make your backup key

    Install age, then run:

    age-keygen -o artifact-host-backup.key

    It prints a line such as Public key: age1.... That age1... value is what you send us.

    Keep the file. It holds the private key. Never send the file, or the line that starts with AGE-SECRET-KEY-, to us or to anyone. Store a copy where you keep secrets that must outlive a laptop. If you lose it, your backups are lost: nobody can recover them, and we cannot help.
  2. Turn on two settings in your tailnet

    In the Tailscale admin console, on the DNS page, turn on MagicDNS and HTTPS certificates. The host refuses to start without them.

  3. Send us the public key

    Send the age1... value to the person at 2389 who invited you. That is all we need. You send no admin email and no Tailscale key.

    Optional: if you want search by meaning, also send a LunaRoute key of your own.

  4. Open the link we send you once

    We create your host and send you one Tailscale login link. The person who should be the host's first admin opens it and signs in to your tailnet.

    Whoever opens the link decides which tailnet the host joins, and becomes its first admin. So open it once, with the right person.

  5. Switch off key expiry

    In the Tailscale admin console, open the machine artifacts and choose Disable key expiry. Without this, the machine's key expires (after 180 days by default) and the host drops off your tailnet until someone signs it in again.

  6. Use it

    Your host is at https://artifacts.<your-tailnet>.ts.net. The first request after a start can take up to a minute.

    Use the full name, and bookmark it. https://artifacts alone shows a certificate warning, because a certificate can only cover the full name.

    • Point your agents at /skill.md on your host. It tells them everything.
    • The command-line client for your system is at /download/ on your host.
    export ARTIFACT_HOST_URL=https://artifacts.<your-tailnet>.ts.net
    artifact-host whoami                        # the first admin sees "admin": true
    artifact-host admins add pat@example.com    # add another admin

After that

The things worth knowing before you need them.

Backups: only you can see whether they work

The host backs up every hour. Only your admins can see whether a backup failed. We cannot. Check now and then, and tell us if state is failed:

curl -sS "$ARTIFACT_HOST_URL/api/v1/backup"   # "state": "ok", and "sealed": true
If the host loses its data

We start a new machine. It cannot read its sealed backups, so it waits for your key.

  1. We send you a new login link. Open it as before.
  2. Send the key to the host over your tailnet: artifact-host unseal --identity-file artifact-host-backup.key

The key goes over your tailnet to the host. The host holds it in memory for that one restore and keeps no copy. You do not send the key to us. The host that receives it does run on the machine we operate.

Upgrades

We deploy new versions to every host when we ship them. The host restarts, which takes about a minute. We give no notice.

Leaving
  1. Take your work with you while the host runs. An admin switches the admin view on (the footer of any page), then runs artifact-host export-all --dir ./artifact-host-export.
  2. Tell us. We stop the host. We keep its disk and its backups for 30 days, in case you change your mind.
  3. After 30 days we delete the machine, its disk, every backup and the storage key.