Launcher · App Store

One glass panel to boot your workflow — and an App Store that installs cleanly, shows progress, and doesn’t forget.

Why Launcher and App Store exist

Most “GPU cloud” experiences are the same story: you start a machine, then you’re left guessing — which port is Stable Diffusion, which tab is Jupyter, which window is “that A100,” and why everything needs SSH just to do normal work.

CloudDock takes a different approach: workflow first. The Launcher is the cockpit. The App Store is how your container evolves without turning into dependency soup.

CloudDock Launcher Workflow: One panel to boot SD, JupyterLab, DeepSpeed Console, and the Model Store. No SSH circus. No guessing which screen is “that” A100.

CloudDock Launcher: one glass panel, zero confusion

The Launcher is the first screen you should see. It’s designed to answer two questions instantly:

  • Where do I go? (SD / Training / App Store / DeepSpeed / Model Store)
  • What state is my session in? (running, busy, resource usage, safe to proceed)
CloudDock Launcher home screen with buttons to SD, Training Center, App Store, and DeepSpeed Console
Launcher: everything you need is a button, not a port number.

Buttons wired per container (no dead links)

CloudDock containers aren’t all identical — some flavors focus on SD, some on training, some on heavy compute. The Launcher respects that.

Buttons are wired per container: Usagi shows what belongs in Usagi (SD, Training Center, App Store, etc.), DeepSpeed containers show what belongs there (DeepSpeed Console, tools, docs).

What that means for you: you don’t need to memorize ports, URLs, or “which service runs on which machine.” If it’s part of this container’s workflow, it’s a button.

No SSH circus

For normal SD work, SSH is an anti-feature. It turns a creative workflow into a sysadmin workflow. CloudDock’s goal is to make the default path: click → create, not SSH → fix → pray.

Design principle: If you needed SSH for something that isn’t truly necessary, we consider it a workflow failure — not “that’s how Linux works.”

CloudDock App Store: installs that don’t ruin your day

SD ecosystems are powerful, but they’re chaotic: random extensions, random scripts, random checkpoints from unknown sources, and installs that break the environment.

CloudDock App Store exists to make “adding tools” feel like adding apps: discover, install, track progress, and keep your workspace stable.

CloudDock App Store interface showing app listings and categories
App Store: curated tools, clean installs, fewer surprises.

App Store 3.0: a real app page (not a list of zip files)

App Store 3.0 is built around the idea that each app is a product page:

  • Per-app page with description and requirements
  • Screenshots so you know what you’re installing
  • Ratings to avoid wasting time on bad tools
  • Download status that survives refresh (no more “did it install?” panic)
App Store per-app page with screenshots, rating, and install button
Per-app pages: the difference between “app store” and “random download list.”
Refresh-proof installs: App Store 3.0 keeps install progress and status in sync — so you can refresh the page and still know what’s happening.

Hash-verified models only (no mystery checkpoints)

Models are the core of your output — and also the biggest source of risk and confusion. A “mystery checkpoint” from random corners of the internet can be: broken, mislabeled, low quality, or worse.

CloudDock’s approach is simple: hash-verified models only. If it’s in the Model Store / App Store pipeline, it’s traceable and verifiable.

Why this matters: You spend hours training, generating, and iterating. The last thing you need is a model that’s secretly not what it claims to be. Verified hashes = fewer surprises, safer workflow.

How this changes your day-to-day workflow

When Launcher + App Store are working together, the SD experience becomes:

  1. Open a machine → land in Launcher.
  2. Click SD → generate and iterate.
  3. Need a tool? Click App Store → install with visible progress.
  4. Need training? Click Training Center → run a guided workflow.
  5. Need serious compute? Click DeepSpeed Console (when available in your container).
Workflow diagram showing Launcher connecting to SD, Training Center, App Store, and DeepSpeed Console
The point is not “more features.” The point is fewer steps between you and output.

FAQ

“Can I still access ports directly if I want?”

Power users can do power-user things — but CloudDock is designed so you don’t have to. The Launcher is the default because it’s consistent and hard to mess up.

“Why does ‘survives refresh’ matter so much?”

Because in most web UIs, refreshing mid-install turns the process into a mystery. App Store 3.0 keeps state so you don’t waste time repeating installs or guessing outcomes.

“What does hash-verified models mean?”

It means the model you download is exactly the model intended — not an altered file with the same name. Verifying hashes reduces broken installs and eliminates “mystery checkpoints.”

What’s next?

Less guessing. More shipping.
← Back to SD Home