artifacts

one file in. one url out.

publish a page from a single file. versioned, shareable by link, and rendered on an origin of its own.

publishing

write the content.
we do the document.

your file is the page. the platform wraps it in a head, a reset, and the inference shell design tokens, so it matches the product in light and dark without you thinking about it.

publishing the same name again appends a version and updates the page in place for everyone who already has it open.

terminal
$belt artifact publish ./deploy-failures.html --title "why friday broke"
✓ published okaris/why-friday-broke v1
→ https://app.inference.sh/artifacts/0gahj24m
# same name again is a new version, live for anyone watching
$belt artifact publish ./deploy-failures.html --label "with the rollback"
✓ published v2
terminal
# a page is static until it asks
$belt artifact publish ./poll.html --capability db --capability user
✓ published okaris/team-poll
db — its own store
user — who is viewing
# in the page
$await window.inferencesh.db.set("votes", me, { choice })

capabilities

pages that remember
what people do on them.

a page has no network at all until it asks. declare a capability and it gets a small runtime: its own store, who is viewing, and files kept beside it.

a poll, a sign-up sheet, a checklist that survives a reload — without a backend of your own.

isolation

a page you were handed
can never act as you.

artifacts are served from their own domain, one hostname per page, and your session cookie cannot reach it. every call a page makes is made with the session of whoever is looking — so it can only ever do what that person could already do, and nothing on their behalf elsewhere.

when terminal output is the wrong medium.

a dashboard, not a dump

an agent just pulled the numbers. hand over the chart instead of two hundred lines of json.

options side by side

three designs, three approaches, three query plans — laid out to compare rather than scrolled past.

something the team acts on

a checklist, a poll, a sign-up sheet. it remembers what people did, and the link is the whole handover.

faq

frequently asked questions

can't find what you're looking for? we're here to help.

contact us →

A single self-contained HTML or Markdown file published as a real page with a URL. inference shell wraps it in a document with the platform design tokens, serves it under a strict Content-Security-Policy, and keeps every version you publish.

ready to ship?

start with the hosted platform. deploy your own when you're ready.

we use cookies

we use cookies to ensure you get the best experience on our website. for more information on how we use cookies, please see our cookie policy.

by clicking "accept", you agree to our use of cookies.
learn more.