Cafe · FAQ
Common questions.
Short answers for strangers comparing this hub to CI checklists, other brands (including ship.studio), and OS trust prompts. Deeper product boundary: Intent · Honesty.
Does Orbit Yard silence SmartScreen?
No. We never claim to suppress Windows SmartScreen or grant “verified publisher” status. Desktop cuts use Signet locally; graduate / notarize / store submit stay on you and official tooling. See human gates.
Is this the same as ship.studio?
No. This repo is the local shipping hub (CLI · TUI ·
Desktop) for sign → release → deploy. It is not the unrelated agentic
product at ship.studio. If you landed here from that brand, check the
other site’s own docs — our scope is offline-first final-mile sequencing.
Why pay $29 if the source is open?
The publish sequence itself is not paywalled — you can clone and build for free. Solo pays for packaged Desktop/CLI builds, a local license file, Paddle-hosted checkout/invoices/refunds, and not assembling the toolchain yourself. Details on Pricing.
Can Studio take Paddle, Creem, or Waffo for my app?
As a guide, yes. Desktop Integrations opens those vendor dashboards;
you create the product there and put keys on the deploy host. Studio does not process
those charges. Buying Orbit Yard Solo is Paddle overlay on this site
(when PUBLIC_PADDLE_* is set). Creem and Waffo stay customer-product guides.
Is Signet required?
For desktop / Signet release cuts — yes (Signet on PATH or
SIGNET_PATH). For Local docs-only or hosted-web work
without a desktop cut, Signet may be optional; Orbit matters when you use Orbit-hosted
deploy. Dashboard health tiles show Found/Missing honestly — missing Signet hard-blocks
only when the project layout needs a desktop cut.
Still stuck? Docs · Human gates catalog · Refunds.