Dashboard

The dashboard at app.rl.trydaytona.com is the visual counterpart to the SDKs and REST API: everything you can do programmatically against a project, you can see and manage here, plus the organization-level operations (members, invitations, credits) that don't belong to any single API key. Sign in with your account; on first sign-in a personal organization and default project are created for you automatically.

The header carries an organization and project switcher — every resource page below shows the currently selected project's resources, so if something seems missing, check which project you're looking at first.

Sandboxes

The Sandboxes page lists the project's sandboxes with their state, resources, and image, and is where you create new ones interactively — from a registry image reference or from a registered snapshot. Lifecycle actions (stop/start, pause/resume, fork, delete) are available directly from the list. It's the quickest way to sanity-check what your automation created and clean up leftovers.

Sandbox details

Clicking a sandbox opens its details view, organized into tabs:

• Overview — state, resources, image, and metadata at a glance.
• Terminal — a fully interactive shell into the sandbox, right in the browser. Ideal for debugging a misbehaving agent run without writing any code.
• Files — browse, inspect, upload, and download the sandbox's filesystem.
• Preview — reach HTTP services listening inside the sandbox (see port forwarding).
• SSH — connection instructions for reaching the sandbox over SSH.
• Usage — live CPU, memory, and disk charts plus the sandbox's usage history.
• Logs — the sandbox's console output, live while it runs and persisted after it terminates.

Snapshots

The Snapshots page manages the project's images in three tabs: Snapshots (named aliases you register from a registry reference or an inline Dockerfile build), Project images, and Cached images. Registering a snapshot here is equivalent to the SDK's daytona.snapshot.create — see snapshots.

Volumes and Object Stores

Two pages for the project's attachable storage. Volumes creates and manages platform-hosted persistent volumes; Object Stores connects your own S3-compatible buckets, including a guided credentials flow that saves the access keys as project secrets for you — see object stores.

Secrets and Registries

Secrets manages the project's write-only secrets: set or replace values, edit allowed domains, and delete. Values are never displayed after saving. A toggle reveals the platform-managed secrets that back object-store credentials. Registries stores private registry credentials per host so private image pulls authenticate automatically.

Spending

The Spending page shows the organization's credit balance and a usage report across sandboxes — the visual form of GET /usage/report. See Spending & Credits for how metering and billing work.

API Keys

Mint and revoke the project's API keys. A key's value (rlp_...) is shown once at creation — copy it then, because only a hash is stored. See Authentication.

Members, Invitations, and Settings

Members lists the organization's members and their roles, and lets owners invite (by email, as owner or member) and remove people. Invitations shows invitations addressed to you, waiting to be accepted. Settings holds organization and project settings, including creating and deleting projects.

Note: a few navigation entries (such as Wallet, Billing, Webhooks, and Audit Logs) are placeholders for upcoming functionality and currently show a "not implemented" notice.