If yes, skip to step 3. If no:
sharktopus needs permission to create a bucket, push a container image, and deploy a serverless service in your account. The minimum roles per provider are documented in ACCOUNT_SETUP.md → {{ meta.name }}. For the first deploy, the admin-equivalent role on each cloud works.
Console link: {{ meta.console }}
{{ meta.verify }}
No error = you're ready for step 4.
{% endif %}The interactive wizard lives in the terminal today. It offers 2-3 auth paths per provider (browser OAuth, CLI, static keys / service principal) so you can pick the one that fits your host.
sharktopus --setup {{ provider }}
Note: a streaming-in-the-browser version of this wizard is planned (milestones M8–M10). Today the terminal is the source of truth.
sharktopus --setup {{ provider }} will dosharktopus-crop image from GHCR.~/.cache/sharktopus/.