Replit private deployments and Jiayang Cloud

Updated 17 October 2026

Replit lets you publish an app to the public, behind a password, to your workspace or to people you invite, and its private options ask visitors to sign in through Replit. On Jiayang Cloud every app starts private, people you share it with sign in without an account, and your app gets a signed token saying who is calling.

What follows about Replit comes from Replit's docs, read on 16 and 17 October 2026 and listed at the end.

How Replit keeps a deployment private

A published app can be Public, Password protected, Workspace only or Invite only. The last two are the private options.
Apps in a personal workspace start public. Apps in an organization workspace start with a private option.
Visitors to a password-protected app don't need a Replit account. For the private options, visitors without access are asked to sign in through Replit.
Replit Enterprise lets admins require private deployments, ban public apps, require security scans and stream an audit trail to their own tools.
The docs don't say whether a deployed app is told who the visitor is.

Side by side, for an internal app

What	Replit	Jiayang Cloud
New apps	Public in a personal workspace, private in an organization's	Private, in every workspace
Viewers	Workspace members, or invited users and groups, signed in through Replit. Or anyone with a password	Any email address, everyone at your company's domain, or a group. No account needed
The caller, in your code	Not stated	A signed token on every plan, checked by SDKs for Node, Python, Go and Rust
Security scans	Dependency and package checks free. An Agent review of the code on paid plans. Admins can require scans on Enterprise	Every deploy, on every plan, for keys left in the code and packages with known vulnerabilities
Rules for who may publish	Admins can require private deployments on Enterprise	A publish policy, on Enterprise, and on Business for early customers for a limited time
Audit log	Streamed to your tools, on Enterprise	Every request let in or refused, and every change with who made it, on every plan. Streaming on Enterprise, and on Business for early customers for a limited time

When Replit is the better fit

When you want to write, run and publish code in one place in the browser, and the people who use the app work in your Replit workspace.

Move a Repl here

Replit has no public API for reading a Repl, so the import works from the Repl's files:

Push the Repl to GitHub from its Git pane, or download it as a zip and unzip it.
In the Repl, open Secrets, then Edit as .env, and copy what it shows into a file outside the project, such as ~/bot-secrets.env.
Import the folder, or the repository by its address:

jiayang import replit acme/bot ./bot --env-file ~/bot-secrets.env

The import reads .replit for how the Repl runs: its run command becomes the container's start command, its port the container's port, and a scheduled deployment becomes a schedule. Replit Auth and Replit Database don't come along. Everyone signs in through us, and the app has a database of its own. A container app needs the Team plan or above. See Import from Replit.

Sources

Private deployments, Replit's docs. Checked 16 October 2026.
Replit Enterprise, Replit's docs. Checked 16 October 2026.
Security scan levels, Replit's docs. Checked 17 October 2026.

Import from Replit, in the docs
How we differ from other ways to keep an app private
Pricing