> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.hyjal.cloud/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.hyjal.cloud/_mcp/server.

# Console tour

> A tour of the Hyjal Console: Organizations, Projects, the Board, the Explorer, the Resource workspace tabs, and the Inspector.

The Hyjal Console at [console.hyjal.cloud](https://console.hyjal.cloud) is
where you see and operate everything you deploy. This page walks the surfaces
you use every day so the names in the rest of the docs are already familiar.
Everything here is also reachable from the [`hyjal` CLI](/reference/cli); the
Console is the visual counterpart.

## Organizations and Projects

The Console opens on your **Organizations** list. An Organization is the
top-level account container: it holds members, roles, and billing. Selecting
an Organization shows its **Projects**.

A [Project](/platform/projects-and-resources) groups related Resources and is
the unit of collaboration and scoping. The example throughout these docs is
the `acme` Project, containing a `web` front end and a Go `api`.

## Inside a Project

Open a Project and you land on its workspace. Three surfaces anchor it: the
Board, the Explorer, and the Resource workspace with its bottom tabs.

### The Board

[The Board](/platform/the-board) is the visual canvas for the Project. Each
node is a Resource; each edge is a relationship between Resources: a path
mount, an allowlist grant, or a data connection. Drawing an edge from a front
end to an API configures a path mount between them, the same forwarding you
would otherwise write as `mounts` in [`hyjal.toml`](/deploy/hyjal-toml).

The Board shows a Project at a glance: what is public, what calls what, and
the path a request takes.

### The Explorer

The **Explorer** is the list-and-tree view of the same Project: Resources and
their Bucket directories in a navigable panel. Use the Explorer when you want
to move through files and Resources by name rather than by topology. Selecting
a file opens it; the same [Bucket](/data/buckets) contents are reachable from
the [`hyjal files`](/reference/cli) command.

### The Resource workspace

Select a Resource and its workspace opens with a bottom tab bar. Each tab is
one facet of the Resource:

| Tab      | What it shows                                                                                                                                  |
| -------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Logs     | One chronological table of requests and log lines, with a search box and HTTP method filter chips. See [Logs](/observability/logs)             |
| Stats    | Request counts, compute milliseconds, and peak memory, the same meters as billing. See [Stats and metering](/observability/stats-and-metering) |
| Config   | Policy for the Resource: `public`, `allowlist`, `env`, `runLimitSecs`, `egress`, and Domains                                                   |
| Tables   | Live, editable grids for [Hyjal Tables](/data/hyjal-tables) scoped to the Project                                                              |
| Activity | The history of deploys, rollbacks, and policy changes for the Resource                                                                         |

### The Inspector

The **Inspector** panel shows a Resource's identity: the facts that name and
address it, not its behavior:

* **Name** and **endpoint** URL
* **Status** (serving, or the current deploy state)
* **Digest** of the live artifact (`sha256:…`)
* **Tags**
* **Relations** to other Resources

When you need to know which exact artifact is live or which Resources call a
given Resource, the Inspector is the source of truth.

## The Overview page

Each Project has an **Overview** page. Alongside a summary of the Project's
Resources, it presents two deploy cards:

* **From the Board**: create and wire Resources visually, then deploy from
  the canvas.
* **From the CLI**: the copy-paste commands to
  [`hyjal init`](/get-started/quickstart) and `hyjal deploy` from your
  repository.

Both paths produce the same result.

## Where domains live

Custom domains are managed per Resource under **Config → Domains**. Add a
domain, and the Console shows a three-stage tracker (DNS, then Certificate,
then Live) as verification and TLS issuance complete. The full walkthrough,
including the required TXT and CNAME records, is in
[Custom domains](/deploy/custom-domains).

## Next steps

* Understand what the Board is modeling: [Projects and Resources](/platform/projects-and-resources)
* Ship from the terminal: [Quickstart](/get-started/quickstart)
* Read the request-level view: [Logs](/observability/logs)