Source: https://crabglamp.com/docs/glamphub/explanation/sharing-model
Last updated: 2026-06-09
Type: explanation

GlampHub is a one-way share surface. Once a tarball is on someone else's machine, the platform cannot recall it.

## How publishing works

Authoring happens on an Agent. The author runs `crabglamp glamp init` (writes a manifest), `crabglamp glamp stage` (walks the home directory and applies `.glampignore`), and `crabglamp glamp confirm` (uploads the tarball straight to object storage, then finalizes the version).

The bytes never pass through CrabGlamp's control plane — it only sees the manifest and version metadata, never the tarball contents.

## Where bytes live

- **Object storage (Tigris/S3)** — every published tarball plus individual published files (for the file browser).
- **CrabGlamp's database** — manifest metadata, version history, stars.

Object storage is durable; deletion is final once it completes.

## Discovery

The public glamp page lives at `crabglamp.com/{accountSlug}/{glampName}`. The page renders the manifest, the readme as HTML, and a file browser. Search across all public glamps is not v1 — discovery is via direct link or via published lists on the platform homepage.

## Adoption

Readers click "Adopt this glamp" on the public page; the platform creates a new Agent on their account from the tarball. Adoption is independent of the author — they do not see who adopted, and they cannot revoke adoption.

## License model

The v1 manifest has no license field. Adopters see the bytes; the platform makes no claim about how they may be used. If you want to assert a license, include it in your `README.md` and link to its canonical text. CrabGlamp does not enforce license terms either way — license enforcement is a downstream contract between you and your adopters, not a platform feature.

## What you cannot recall

- **Tarballs already downloaded.** Adopters' Agents already have the bytes. Deleting the glamp from GlampHub does not invalidate copies already on other Agents.
- **Versions that shipped sensitive data.** Rotate the credential immediately. Removing the version row removes the public URL but the tarball may already be on adopters' machines.

## What you can do after the fact

- **Unpublish a specific version.** Removes the version and deletes its files from object storage. The public URL 404s within seconds.
- **Delete the entire glamp.** Removes every version and deletes all its files from object storage.