# Publishing

Tensormorph does not have a confirmed publishing target of its own (no branded Hub to publish to) - this page covers what "getting a result out of Tensormorph and to other people" actually means today.

## What's confirmed: export

The concrete, confirmed action is [exporting](/docs/compare-and-morph/export-transformed-models) - writing a materialized morph result, or any transformed checkpoint, out as a standalone file in a standard format (safetensors or ONNX). An exported file is ordinary and portable: sharing it means sharing a file, the same way you'd share any checkpoint, through whatever channel you already use (a shared drive, an artifact store, or uploading it to a Hugging Face Hub repository yourself).

## What's confirmed: recipes

Alongside an exported checkpoint, its `recipe.json` (see [Model Morphing](/docs/core-concepts/model-morphing#expression-dag-not-an-edit-history)) is small, diffable, and portable in its own right - sharing a recipe rather than (or in addition to) a full checkpoint lets a collaborator re-materialize your result against their own base, which is often more useful than sharing weights alone.

## What isn't confirmed

A dedicated in-app "publish" action that pushes a result to a Tensormorph-hosted destination isn't part of the confirmed design - see [Model Repositories](/docs/hub-and-collaboration/model-repositories) for the nearest roadmap item (a Tile Server and thin web client) and why it's a narrower thing than a publishing platform. Until that exists, "publishing" from Tensormorph means exporting a file and moving it yourself.

## Related resources

-   [Export Transformed Models](/docs/compare-and-morph/export-transformed-models) - the confirmed mechanism this page is built around.
-   [Model Repositories](/docs/hub-and-collaboration/model-repositories) - where a published result might eventually live.
-   [Tensor Cards](/docs/hub-and-collaboration/tensor-cards) - carrying provenance forward into whatever you publish to.