Universal Usagi & Momonga

Two faces, one brain. Usagi runs your daily waifu workflow; Momonga takes the night shift and heavy jobs.

Two faces, one brain

CloudDock ships two primary Stable Diffusion container flavors: Universal Usagi and Universal Momonga.

They share the same underlying foundation (“one brain”): the same core layout, the same CloudDock workflow design, and the same A/B/C/D machine compatibility. What differs is the update lane and risk tolerance.

Pick your lane: If you want the newest workflow improvements first, use Usagi. If you want a calm, stable environment for long runs, use Momonga.

What they share (the “one brain” part)

Whether you launch Usagi or Momonga, you get a consistent CloudDock experience:

  • Stable environment across A/B/C/D — same UI everywhere.
  • Prewarmed essentials — venv, ControlNet, VAEs, and common extras ready out of the box.
  • Click-first workflow — generate, train, and learn without needing a terminal.
  • CloudDock Launcher — a unified start hub and control panel.
  • CloudDock SD Training Center — training as a guided product, not a shell script.
  • CloudDock App Store — curated installs with fewer “dependency roulette” moments.
Usagi and Momonga showing the same UI across A/B/C/D groups
Same UI everywhere: A/B/C/D changes performance headroom, not the workflow.

Safety without spying: CloudDock Intelligent Dog™

Every container includes a per-container watchdog: CloudDock Intelligent Dog™.

Its job is simple: watch for bad behavior, not your art. It focuses on security signals (suspicious processes, abuse patterns, privilege escalation attempts), not on what you generate, view, or create.

In plain English: the Dog is here to keep the platform safe, not to judge your prompts.

Usagi: the beta lane (fast, aggressive, experimental)

Universal Usagi is intentionally a beta-lane product. It’s where CloudDock ships new workflow ideas first: UI improvements, new defaults, faster iteration loops, and experimental features.

  • For: early adopters, creators who love new toys, users who want the newest workflow first
  • Strength: fastest feature velocity, newest UX, newest integrations
  • Trade-off: higher risk of edge-case bugs because it’s the “front line”
Usagi promise: If something requires the terminal in a non-essential situation, we treat it as a product failure and fix it fast. But as beta-lane, Usagi may occasionally be more “adventurous” than calm.

Momonga: the stable lane (slow, careful, night-shift ready)

Universal Momonga is the stable update stream. It prioritizes predictability, long-run reliability, and “I don’t want surprises at 3AM.”

That also means Momonga’s feature adoption is intentionally slower: most new features land in Usagi first, then get proven, and only then do they move into Momonga.

  • For: long sessions, heavy jobs, production-like runs, training you don’t want to babysit
  • Strength: stability-first, fewer changes, fewer moving parts
  • Trade-off: new “shiny features” arrive later (by design)
Security patches are different: if it’s a safety/security fix, Momonga follows quickly. “Nice-to-have features” move slower — and that’s the whole point.

Release policy (how updates really work)

Think of Usagi and Momonga as two rails on the same train track:

  • Usagi ships first. It’s where features are born, tuned, and stress-tested.
  • Momonga ships after. It receives features when they are proven safe and predictable.

In practice, Momonga may sometimes run:

  • The same version Usagi used earlier (a “proven snapshot”)
  • An older base + critical patches (security fixes and system stability improvements)
Why we do this: Stable containers shouldn’t change behavior every time you log in. Momonga’s job is to be boring — so your results are repeatable.

Which one should I use?

If you’re not sure, use this decision rule:

  • Choose Usagi if you:
    • want the newest workflow improvements
    • like trying new features first
    • do daily generation and fast iteration
  • Choose Momonga if you:
    • run long sessions (night shift)
    • train heavier jobs and want fewer surprises
    • care more about stability than new toys
Diagram showing Usagi as beta lane and Momonga as stable lane
Usagi = fast lane. Momonga = stable lane. Same brain, different priorities.

FAQ

“Do they feel different to use?”

The workflow is intentionally consistent. The “difference” is mostly: how quickly features change, and how aggressively we ship new ideas.

“Do I ever need the terminal?”

For normal SD workflows: you shouldn’t. If you needed it for something non-essential, we consider that our problem.

“Does the watchdog monitor my art?”

No. The per-container Dog watches for bad behavior patterns and platform abuse signals, not your prompts, images, or creative content.

What’s next?

Two faces. One brain. Pick your lane.
← Back to SD Home