One workspace for the whole team. Synced through a git repo you own.

Publish a workspace to a repo on your own git host. Teammates connect with the URL, and shared queries, dashboards, and memory sync from there on. A live dashboard on their machine, not a screenshot in Slack.

acme / Sharing
Workspace files Synced · 2 min ago
churn.sql Shared
revenue.html Shared
context-billing.md Shared
scratch.sql Private

git@github.com:acme/data-workspace.git

Activity

Added revenue.html

anna · 2h ago

Updated churn.sql, memory

you · yesterday

Shared production datasource

you · 2 days ago

Pulled anna's changes

Sync runs itself. Commit, pull, push, in the background.

Valv commits after your changes, pulls every few minutes and on focus, and writes commit messages a human can read. Nobody on your team runs a git command.

Recent commits

Added revenue.html anna · 2h ago
Updated churn.sql, memory you · yesterday
Shared production datasource you · 2 days ago

Conflicts never block. And never lose work.

When two people edit the same file, your teammate's version wins at the original path and yours stays next to it as a conflict copy. Memory files merge as a union instead. No prompts, no lost edits.

Both edited churn.sql

churn.sql anna's version
churn (conflict).sql your version, kept
Sync continued, nothing lost

Secrets stay on your machine. Chats too.

Datasource configs sync without their secrets. Teammates get the host and database, passwords stay in each person's OS keychain. Your conversations never enter the repo at all.

production · db.internal:5432 Synced
password Keychain only
your chats Never synced

Bring your team along.