Dashboard and UI Guide

This page orients you around the main UI surfaces. For detailed workflows, follow the links to the dedicated docs.

Main surfaces

After launch, the app opens Data Explorer. No account or sign-in is required to start — the IDE (Explorer, SQL, connections) is always free. An account is only needed when you run your first stream.

The left sidebar gives access to:

Data Explorer — browse and query connected sources
Streams — create and manage Load/CDC streams
AI Chat — ask about your databases, files, and streams in plain language (AI Chat)
Logs — execution logs for streams and explorer operations
Account — subscription, API key, and install ID

Data Explorer

Data Explorer is the default view after launch. From any connection you can:

browse databases, files, and S3 paths
inspect table structure and metadata
view and edit data
run SQL queries
generate ER diagrams

Data Explorer uses a two-pane layout where both panes are fully equal — like split editors in VS Code. For details, see Data Explorer and SQL Console.

Connections are managed directly in the Data Explorer sidebar. Click + New Connection at the top to add one. Hover over any connection to reveal a mini-toolbar with Edit (pencil), Clone (copy), and Delete (trash) actions.

The sidebar lists all configured connections — databases, local files, and S3-compatible storage — with their tree of schemas, tables, and objects. For setup details, see Connection Management.

Hover over supported tables, views, files, and file-backed table folders to reveal quick actions for opening in either pane or opening in SQL Console.

Logs

The Logs view shows execution logs shared across Data Explorer and Streams. Use it to inspect query results, stream progress, errors, and diagnostics.

Streams

Streams is organized around two things: a saved stream config and the runs created from it. Select a config to inspect or edit its source, target, and behavior. Expand its chevron to work with that config's run history.

Find a previous run

Expand a config in the left rail.
Use All, Finished, Stopped, and Failed to narrow that config's history.
Select a timestamped run to open its details. Each item shows its completion time, duration, and status dot.

Read a completed Load run

The Monitor tab gives the run-level result: Load Progress, Rows Saved, completed Chunks, data size, Reader and Writer rates, and table-level status. From the header, open Logs or use the context-appropriate primary action. A completed run may offer Run Again; a run whose saved state needs clearing shows Reset.

Inspect an interrupted run

A stopped Load run keeps the progress recorded at the stop point. If its saved state is still compatible, the config action is Resume Load. If the target or saved state can no longer be resumed, the run explains why and offers Reset to clear the saved state before a fresh run.

Compare a finished run

Use Compare to review schema results and source-versus-target data for the selected run. This is a run detail, so it remains available while you review the earlier execution.

Create and start a stream

Select source and target — pick existing connections or create new ones inline.
Configure — choose Load or CDC, select tables/schemas/files, define scope.
Start — create a new run, then select it from the config's history to monitor or compare it.

For configuration details, see Stream Configuration Guide. For run statuses and recovery actions, see Stream States and Lifecycle.

Account

The Account page shows:

Account — signed-in email
Subscription — current plan and billing link
API Credentials — API key and install ID used to authenticate API requests

For licensing details, see Licensing & Seats.