Join us live on August 26 in San Francisco for TailscaleUpTICKETS ON SALE NOW ->

Aperture dashboard reference

Last validated:

Aperture by Tailscale is currently in beta.

Access the Aperture dashboard at /ui/ on your Aperture hostname (for example, http://<aperture-hostname>/ui/) to review usage data, session logs, and adoption metrics.

This topic is part of the Aperture reference documentation. For how-to guides on observing and exporting usage data, refer to observe and export AI usage.

Dashboard page

If you incorrectly authenticate user devices with tag identities, all LLM sessions from those devices appear to come from the tag identity instead of the individual user. This happens because Tailscale tags do not provide per-user identity. Refer to all sessions appear to come from the same user for more information.

The Dashboard page shows token usage for the current user. It includes the following components:

  • Total tokens by model (bar chart)
  • Recent activity timeline
  • Quick stats: total requests, total tokens, active sessions

Admins can access other users' dashboards by going to /ui/dashboard/:loginName where loginName is the Tailscale login name of the user (for example, alice). For instructions on checking and managing budgets, refer to check and refill budgets.

Logs page

The Logs page shows request history with session grouping. It provides the following views:

  • Sessions list: Shows aggregated metrics per session (total tokens, request count, and duration).
  • Session expansion: Select a session to show its individual requests.
  • Request detail: Select a request to show full capture data, including headers, request body, response body, and tool use details.
  • Filtering: Filter by date range, model, or user.

Session grouping helps you understand the context of conversations. A Claude Code session can show dozens of requests that together represent a single coding task.

Tool Use page

The Tool Use page shows tool invocation patterns across sessions:

  • Tool use histogram over time
  • Tool type breakdown per session
  • Filter by user, model, or specific tool names

Adoption page

The Adoption page shows organization-wide metrics:

  • Active users over time
  • Usage distribution histogram (how usage is spread across users)
  • Top users by token consumption
  • Model popularity breakdown

This page helps platform teams understand LLM adoption patterns and identify users who need support or training. To export this data for external analysis, refer to export usage data to S3.

Models page

The Models page lists all configured models with their provider information:

  • Model ID
  • Provider name and description
  • API compatibility (which endpoints the model supports)

All providers and models configured in the Aperture settings show on the Models page. Users can reference this page to choose which model to use through Aperture when configuring LLM clients. For a list of supported providers and API formats, refer to supported models and providers.

Settings page

The Settings page lets admins edit the Aperture configuration using the Visual editor (default) or the JSON editor.

Audit Logs page

The Audit Logs page is an admin-only page that displays a paginated table of audit events recorded by the Aperture instance.

  • Table columns: time, actor (the login name of the user who performed the action), action (color-coded by type), subject (the login name of the affected user), resource (type and ID), and access method (UI or API).
  • Tracked actions: data access events (captures, metrics, exports, session data), configuration changes, and quota operations (refills, balance changes, pausing).
  • Expandable detail rows: events with detail data display an expand chevron. Configuration change events show a unified diff view with syntax-highlighted additions and deletions. Other events show structured key-value metadata or preformatted text.
  • Filtering: combinable filter pills for six dimensions -- date range (presets or custom picker), actor, action, subject, resource type, and access method. Filtering runs at the database level.
  • Pagination: server-side pagination with a default of 50 events per page.
  • Column visibility: a dropdown to show or hide individual columns.

Non-admin users receive a message indicating that audit logs are available to admins.

Hooks page

The Hooks page displays available partner hooks and custom webhook connections.

  • Category filters: chip buttons to filter hooks by category -- Security, Monitoring, Compliance, Analytics, Developer, or All.
  • Hook cards: each card shows the hook name, description, logo, category badge, and configured or disabled status.
  • Detail overlay: selecting a hook opens a detail view with a full setup guide, deep link buttons, and enable or disable controls. Admins can enable, disable, or activate hooks from this view.

For setup instructions for individual hooks, refer to integrate with external tools.

API page

The API page is an admin-only interactive OpenAPI reference for the Aperture REST API.

  • Interactive documentation: browse endpoint descriptions, request and response schemas, and authentication requirements.
  • Try it: test API requests directly from the browser against the running Aperture instance.
  • Base URL: API requests use the base path /aperture on the Aperture node's tailnet address (for example, http://<aperture-hostname>/aperture).
  • Authentication: Tailscale identity authenticates all requests. No API keys are required.
  • Theme support: the reference viewer respects the dashboard's light and dark theme setting.

Non-admin users do not have access to this page in the navigation.