Installation

Install Renart with the one-line installer:

curl -LsSf getrenart.com/install.sh | sh

This installs the renart CLI/server and its small native-window helper. The web UI and scheduler remain embedded in renart; there is no service to stand up and no account to create.

Public-alpha archives are available for Linux (x86-64 and ARM64), macOS (Intel and Apple silicon), and Windows x86-64. Linux builds require glibc 2.31 or newer. Each release archive includes the matching renart-gui helper, checksums, a software bill of materials, and third-party notices; the installer verifies the downloaded archive against the published checksum.

Start Renart

Renart explains its optional usage counts on first launch. To turn them off before starting, run renart telemetry disable or set RENART_TELEMETRY=off. See Security and privacy for the exact fields and controls.

Start Renart inside a git repository:

renart

This opens the Renart workspace in a native window. On Linux the helper uses GTK 3 and either WebKitGTK 4.1 or 4.0, whichever is available. If the platform webview is unavailable, Renart reports the reason and opens the same UI in your browser instead. To run the browser mode explicitly:

renart web --port 9000 --no-open

You can also point it at a workspace explicitly: renart web path/to/repo.

Renart needs a git repository

Renart is built around git-native workspaces: every edit it makes is a plain file change you can diff and commit. If the directory has no repository yet, the first-run setup can initialize one for you.

First run

If the workspace has no pipelines yet, Renart opens the welcome screen, where you can explore a demo project, connect a database and import its tables, or start from scratch. The quickstart walks through it.

The first time Renart runs DuckDB on a machine, it downloads DuckDB’s database driver (about 70 MB) once. Later local DuckDB work reuses it without network access.

The full set of flags (watch modes, TLS, the scheduler) is in the CLI reference.