Keep operational history under control

Set separate retention limits for audit events and completed command results. Cleanup runs on the server, with progress and storage totals visible in Settings.

How it works

  1. Bound operational history

    Keep audit and access events by age and record count. Automatic cleanup runs on the server even when every console is disconnected.

  2. Keep command results separately

    Infrastructure results use indexed JSONL journals. Age and size limits preserve files referenced by current work.

Read the documentation

Try the interface

INTERACTIVE DEMO

Explore the sample projects, accounts, files and access requests. Live sessions and file transfers are available in your own console.

Watch the workflow

SettingsREAL UI

Loading the recorded terminal…

Walkthrough paused
YOUR AGENTS. YOUR INFRASTRUCTURE.

Put your server to work.

Give your agents persistent remote workspaces. Start with one repository and server, then add projects, developers and resources from the same console.