> ## Documentation Index
> Fetch the complete documentation index at: https://docs.selftune.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# SelfTune Cloud

> Use hosted review, distribution, and contributor workflows when a skill extends beyond one machine.

SelfTune Cloud is an optional creator and team surface. Start with local
SelfTune. Add Cloud when a skill needs hosted review, distribution, or evidence
from opted-in installations beyond your own machine.

## Use Cloud when

* a team needs a shared skill inventory and review history;
* a creator distributes versioned skills to other users;
* a proposal needs a hosted evidence and approval workflow; or
* opted-in contributor signals should inform the creator's next decision.

Cloud is not required for local skill discovery, local health, local
improvement, Desktop, or the local dashboard.

## Before connecting

Confirm the organization, account, destination, artifact types, and retention
that apply to the workflow. Local evidence and remote contributor aggregates
serve different purposes and should remain distinguishable.

<Warning>
  A Cloud login or configured token is not blanket permission to upload local
  data. Preview or describe the exact artifact before each new remote workflow.
</Warning>

## Connect deliberately

Sign in at [selftune.dev](https://selftune.dev), then follow the current product
setup for the chosen Cloud workflow. For headless environments, use the
version-matched CLI help and device flow rather than copying an old token into
shell history.

After connecting, verify the active organization and keep a local workflow
working independently. If Cloud is unavailable, local skill use and local
evidence should remain accessible.

## Related workflows

<CardGroup cols={2}>
  <Card title="Publish or share" icon="share-nodes" href="/guides/publish-or-share">
    Choose a destination and verify the exact revision and artifact manifest.
  </Card>

  <Card title="Privacy and permissions" icon="shield-halved" href="/guides/privacy-and-permissions">
    Review consent boundaries before connecting remote state.
  </Card>
</CardGroup>

Confirm that the user's goal requires a remote workflow. Keep local state
operational. Before login or upload, report the destination, organization,
identity, artifact types, and requested mutation. Use version-matched CLI or
product guidance. Stop for explicit consent before credentials, uploads,
publication, invitations, or billing changes.