Skip to content
Jiayang Cloud Docs

Overview

Jiayang Cloud runs the apps you and your agents build, each at its own address. Only the people you share an app with can reach it, and your app gets a signed token saying which of them is calling.

From nothing to a shared app

Section titled “From nothing to a shared app”

The Getting started part of jiayang --help lists these four commands:

Terminal window
jiayang login
jiayang workspace create acme
jiayang deploy acme/hello ./my-app --create
jiayang share acme/hello someone@example.com
  1. jiayang login signs the CLI in. You approve a code in the dashboard.
  2. jiayang workspace create acme makes a workspace called acme. You own it.
  3. jiayang deploy acme/hello ./my-app --create works out what ./my-app is, builds it, uploads it and puts it live at https://hello--acme.jiayang-apps.cloud.
  4. jiayang share acme/hello someone@example.com lets one person in. They get an email with the link.

Deploy your first app runs each of these and shows what they print.

What you can deploy

Section titled “What you can deploy”
  • Static sites and single-page app builds.
  • JavaScript and TypeScript on Workers, including frameworks with a Cloudflare adapter: Hono, Next.js, Astro, SvelteKit, React Router, Nuxt.
  • Servers in a container: anything with a Dockerfile, or a Node, Python, Go or Rust project without one. Container apps need the Team or Business plan.

jiayang detect tells you what a directory is without building anything. How deploy decides what to build has the rules.

The parts

Section titled “The parts”
  • Workspace. Holds your apps, the people in them, the plan and the audit log. Everyone in one has a role: member, admin or owner. See Workspaces and roles.
  • App. Named <workspace>/<app> in every command, like acme/hello. Its address is https://<app>--<workspace>.jiayang-apps.cloud.
  • Version. Every deploy makes a new one and puts it live. jiayang rollback puts an earlier one back. See Versions and rollback.
  • Sharing. An app is private until you share it. Each person gets an app role: viewer, editor or owner. See Share an app.
  • Identity token. The platform signs a 60-second token for every request it lets through, except on a public path with no verifier. Your app verifies it with one of the SDKs to know who is calling. See How access works.
  • Bypass token. A credential for a script or a service that can’t sign in with a browser. See Tokens for scripts and machines.
  • Public path. A path on an app that you open to anyone, with no sign-in, so a webhook can reach it. Give it a verifier and the platform checks each delivery’s signature first. See Public paths and webhooks.
  • Audit log. Every request let in or turned away, and every change to the workspace. See Audit log.

The CLI is also an MCP server, so the agent that wrote your app can deploy and share it. See Use with Claude Code, Codex and Cursor.

Next

Section titled “Next”