Find your way around

Your dashboard is the front door. It's built around one idea: the things that need you get the space, and the things that are fine stay out of your way.

The dashboard

When you open strackt, you land on your team's dashboard. It splits your applications into two groups:

• Needs attention — apps with something to act on get a full card explaining the one thing that matters: a deploy that failed, deploys that are paused, a server that's offline, or storage filling up. Each card gives you the single action to take.
• Running clean — healthy apps collapse to a quiet one-line row: a status dot, the name, and the environment. Nothing's wrong, so they don't ask for your time.

A line at the top sums it up — how many need attention, how many are running clean.

Opening an application

Click any application to open it. The application page leads with a plain-language sentence about how the environment is doing, and a Deploy action you can run right there (it asks you to confirm first). While a deployment runs, the page shows live progress and updates on its own — you can even move to another page and the progress follows you.

Below that, details are tucked into cards you expand only when you want them — the services it uses, what it's running, its public address, and its protection settings.

Across the top of an application you'll find four views:

• Summary — the status-and-deploy page you start on.
• Logs — the history of everything strackt did to this environment. See Read an environment's logs.
• Activity — its deploy history.
• Settings — everything you can change about the environment. See Environment settings.

If an application has more than one environment — production, staging, a preview — the switcher at the top moves between them, and every view stays scoped to the one you've picked.

Servers and services

Opening a server shows a read-only status page: how it's doing, the applications and services it hosts (each linking back to the app), its connection details, and its vitals once they've loaded. It's a place to see a server's state, not to manage it.

Opening a service — a database or cache — works the same way: its status, the applications using it, and where it lives. Connection details and passwords are never shown here; strackt keeps those safe and wires them into your apps for you.

These status views reflect the moment the page loaded. Reload to pick up the latest.

Account and team settings

The Settings area (separate from an environment's settings) covers your account and your team:

• Profile — your name and email.
• Security — your password, signing out other sessions, two-factor authentication, and passkeys. Recovery codes are shown once when you set them up — save them then.
• Team and Members — rename the team, invite people, change roles, and remove members.
• API tokens — create tokens for the CLI and API. A new token's value is shown once, at creation — copy it then.
• Appearance — light, dark, or match your system. This preference is remembered per browser.