Using the console

There is one console, in two places. Hosted, it's your organization's admin UI at https://snoozestack.com — the dashboard lists the organization's projects and provisions new ones. Locally, snoozestack dev serves the same pages over your local runtime at the link it prints. The two are built from the same components on purpose: what you learn in one is true in the other, and a page missing from either side is a bug, not a roadmap item.

One principle explains what the console will and won't do: where a committed file decides something, the console is read-only. Functions, schema, buckets, queues, schedules, auth providers, and email templates are declared in your project — so the console shows them, links the file that owns them, and never offers an edit box that would drift from it. Inside a project, the left rail groups everything the same way these docs do:

Project Overview#

The landing page for a project starts with the three setup steps: install and log in to the CLI, link your local project folder, then connect the management MCP. The project URL, API keys, and MCP access tokens all live directly below those steps.

Data: Database, Storage#

Database has two pages, both read-only views over the runtime: Schema (every table, its columns and indexes — the shape your committed schema.mjs produced) and Data (browse a table's rows). Changing either goes through the files — see Schema & migrations. Storage lists the project's declared buckets and their objects; files move with the CLI and signed operations, not through an upload box.

Platform: Authentication, Functions, Queues, Sites#

Authentication is Users — the project's own signed-up people, with delete and ban — and Providers, showing which sign-in methods the project declares (magic link, Google, Apple, email/password) and the one callback URL to register with each provider; see Authentication. Functions lists the declared functions with each one's code, auth mode, and capabilities read-only, plus sub-pages for Secrets (declared names and which namespaces override them — never values) and MCP endpoints. Queues shows each declared queue's depth and its dead-letter queue, with Notifications for the push services a queue trigger can send through. Sites is Websites — published sites, their versions, and which one is live — and Domains, where a domain you own gets connected and its DNS records managed. See Functions, Queues, Websites, and Domains.

Monitor: Signals#

Signals is everything the app reports, in one envelope — product events, logs, metrics, traces, audits: an events-over-time overview, a live stream, per-user activity, and a custom-chart builder. The same store answers the CLI (snoozestack signals) and the query/export APIs — see Signals and Logs.

Project Settings#

Hosted only (the local dev server has no settings to edit): rename the project, and the danger zone where a project is deleted, permanently, along with everything in it.