# UI walk-through

> A guided tour of the Falak panel: the canvas, the Create picker, service panels, deploys, logs and metrics, databases, servers, observability and settings.

Source: https://falak.sh/docs/getting-started/ui-walkthrough/

A tour of the Falak panel, from a project's canvas to the settings. The screenshots come from a local demo installation (v0.19.0) filled with sample data: the "Acme Studio" organization, its servers and its sites are not real.

## The canvas

Every project opens on a **canvas** of its services for one environment: sites, compose stacks, functions, databases and Redis / Valkey instances. Cards show each service's status, the server it runs on and its volumes; dashed lines show which service references which. Groups such as *Commerce* collect related services.

![A project canvas over the space backdrop: an Automations compose stack, a Commerce group with the Storefront site and its PostgreSQL database, a Marketing site, a Redis instance and a function.](./_images/canvas-backdrop-dark.webp)

The breadcrumbs at the top switch the organization, the project and the environment. <kbd>⌘K</kbd> searches everything. In light mode the backdrop turns into pale ink:

![The same canvas in light mode.](./_images/canvas-backdrop-light.webp)

See [Projects and environments](/docs/guides/projects-and-environments/).

## Create anything from the keyboard

**Create** opens a centered picker. It is one keyboard list at every step: type to filter, move with the arrow keys (Home and End jump), press Enter to go in, and Esc (or Back) to go up one level. Focus stays in the picker and returns to the button when it closes.

![The Create picker: Git repository, Database, Docker image, Empty service, Function and Template.](./_images/create-picker-dark.webp)

Typing narrows the list straight away, so creating a database is "Create, `postg`, Enter":

![The Create picker filtered by "postg": Database first.](./_images/create-picker-search-dark.webp)

From there you pick a repository, an engine, a template or a function starter. A new **function** is created as a draft and opens on its Code tab, so you can edit it before anything runs:

![A draft function's Code tab: the Not deployed yet notice, the editor and the Deploy button.](../guides/_images/function-draft-dark.webp)

Templates are grouped by category. Since v0.19.0 the **Business** category has Odoo and ERPNext:

![The template gallery filtered to Business: ERPNext and Odoo.](../templates/_images/templates-business-dark.webp)

## A service's panel

Click a card and its **panel** slides in over the canvas, which stays in view. A site's tabs are **Deployments**, **Variables**, **Metrics**, **Network**, **HTTP**, **Logs**, **Observability**, **Uptime**, **Processes** and **Settings**. **Deploy** is at the top right.

![The Storefront site's panel on the Deployments tab: a deployment in progress, the active one, a queued one and the history.](./_images/service-panel-dark.webp)

The **⋯** menu holds the less frequent actions: redeploy, roll back, restart processes, [Console](/docs/guides/consoles/), [Network tools](/docs/observability/network-tools/), [Packet capture](/docs/observability/packet-capture/), copy the id and delete.

![The ⋯ menu of a site: Redeploy, Rollback, Restart processes, Console, Network tools, Packet capture, Copy id and Delete.](./_images/service-menu-dark.webp)

A volume chip on a card opens that **volume** over the panel, with its overview, backups and files:

![A shared storage volume opened from its chip: path, usage and the service it is attached to.](../guides/_images/volume-panel-dark.webp)

## Deploy and read the logs

**View logs** on a deployment opens it as a second panel, with its details, build logs, deploy logs per server and step (fetch, prepare, migrate, activate) and the network logs of its release.

![A deployment's Deploy Logs tab: lines grouped by server and step, with a filter and live follow.](./_images/deploy-logs-dark.webp)

The **Logs**, **Metrics**, **HTTP** and **Network** tabs show the site's own logs, resource usage, traffic and connections once the [observability stack](/docs/observability/overview/#enable-the-stack) is enabled. See [Logs](/docs/observability/logs/), [Metrics](/docs/observability/metrics/), [HTTP traffic](/docs/observability/http-traffic/) and [Network connections](/docs/observability/network/).

The **Uptime** tab shows the site's monitors, their uptime over 24 hours to 90 days and the response time split into DNS, connect, TLS and server time:

![A site's Uptime tab: the monitor, uptime percentages, the response-time chart and 90 daily bars.](../observability/_images/uptime-site-tab-dark.webp)

## Databases

A database's panel has **Overview** (connection details and the references other services use), **Databases & users**, **Metrics**, **Logs**, **Insights**, **Backups**, **Network** and **Settings**.

![A PostgreSQL database's Overview tab: engine, server and port, the connection URL and .env lines, and the references for other services.](./_images/db-overview-dark.webp)

**Insights** turns what the engine reports into recommendations, Issues and top queries:

![A PostgreSQL instance's Insights tab: recommendations, an open slow-query Issue and top queries.](../databases/_images/db-insights-dark.webp)

See [Database metrics, logs and insights](/docs/databases/observability/).

## Servers

**Infrastructure → Servers** lists every server. A server's page has **Overview** (usage, the services it runs, capacity, agent and machine check), **Metrics**, **Processes**, **Volumes**, **Firewall**, **Network**, **Private network**, **Security**, **Terminal**, **SSH keys**, **Recipes**, **PHP** and **Settings**.

![A server's Overview: CPU, memory, disk, load and uptime, the services on it and its capacity.](./_images/server-overview-dark.webp)

The **Network** tab shows its listening sockets, whom its workloads talk to, its clients and WireGuard peers, then the eBPF switch, the network tools and packet capture:

![A server's Network tab: listening sockets with their owners, and the talks-to table with named peers and a Block action.](../observability/_images/network-server-tab-dark.webp)

## Observability

**Observability** gathers the organization's **Overview**, **Issues**, **Traces**, **Logs**, **Heartbeats**, **Uptime** and **Alerts**.

![Observability → Overview: requests, error rate, p95 latency, exceptions, jobs and open issues, with charts per hour.](./_images/observability-dark.webp)

Issues come from exceptions, slow routes, missed scheduled tasks, slow queries, security findings and uptime incidents, in one list you can filter, assign and resolve:

![Observability → Issues: a slow query, a slow route, a missed scheduled task and grouped exceptions with their events and users.](./_images/issues-dark.webp)

See [Insights](/docs/observability/insights/) and [Uptime and status pages](/docs/observability/uptime/).

## Network

**Network** has three tabs: **Private networks** (WireGuard networks, firewalls and load balancers), **Blocked IPs** and **Rate limits**.

![Network → Blocked IPs: blocks with their reach, reason, hits and expiry, and each server's protection status.](./_images/blocked-ips-dark.webp)

See [Network protection](/docs/servers/network-protection/).

## Settings

**Settings** covers your account (profile, password, two-factor auth, appearance, API tokens), the organization (general, members, teams, audit log, domains, secrets, compose policy, secret providers, alert rules, recipes, templates) and integrations (source control, cloud providers, Cloudflare, backup storage, builders and more).

![Settings → General in light mode: the organization's name, slug and id, ownership transfer and deletion.](./_images/settings-light.webp)

Some views need a running observability stack or a live agent to show data, so they are not in this tour: the metrics and HTTP charts, the logs, consoles and eBPF charts. Their pages describe them.

## Next steps
