Deploy without signing in

Deploy your first application without creating an account or approving a browser sign-in. EOS automatically creates a guest workspace when you deploy an app or create a database from the CLI.

eos deploy --project=my-app
# Optional PostgreSQL database:
eos database create my-app-db

A guest workspace supports one application and one database. EOS adds no guest-specific limits on build frequency, build duration, runtime scaling, database connections, storage usage, or network usage. Existing platform limits still apply. AI inference, API keys, File Storage, accessories, and collaboration require an account.

Keep access from your deviceCopy Anchor Link

The CLI saves a private guest credential on your device. The server stores a hash of that credential and associates it with the guest identity and workspace. Subsequent deployments from the same CLI installation reuse the workspace.

Treat the credential as a secret. Anyone with it can manage the guest resources and claim the workspace. Losing it means losing the proof needed to claim the workspace; signing in alone cannot recover it. Do not commit or share credential files.

Guest applications are public. Database credentials remain private and belong in server-side configuration.

Claim before the deadlineCopy Anchor Link

EOS 4.15.5 shows a unique Activate workspace link before upload and again after a guest deployment. Open it to sign in with a new or existing account while the build continues; the browser opens the claimed workspace. The link expires after 30 minutes. Keep it private. The CLI waits until the source upload is accepted before claiming, and its background login helper can finish after the deployment command returns, while the device stays online. If the link expires or the device disconnects, run eos login.

Unclaimed workspaces and their applications and databases are deleted 14 days after workspace creation. Deploying again does not extend the deadline. The CLI displays the expiration time.

eos workspace current
eos auth login

Use the ID shown by eos workspace current. Login automatically claims and selects the guest workspace for the account you sign in with. This works for both existing accounts and accounts created during sign-in, in interactive and noninteractive CLI sessions. Your existing workspaces stay unchanged. If the automatic claim fails, the CLI preserves the guest credential; retry with eos workspace claim WORKSPACE_ID.

Claiming requires both your account login and the guest credential on this device. EOS transfers ownership to your account, revokes the guest credential, and removes the guest expiration deadline. Your application and database remain in the same workspace. You can claim additional guest workspaces when you hold their credentials.

You must sign in and claim the workspace before inviting users, including External Operators. Signing in without claiming does not unlock collaboration in that guest workspace.

Claiming does not change an application's public access policy. After claiming, review managed authentication and configure the intended audience.

Open your selected workspace with eos open. Dashboard links include /workspace/{workspace_id} so copied links retain their context. See workspace URLs and opening EOS.