Kimura server (The Central Authority)

The Kimura server is the central service that coordinates Kimura SCM. It is the source of truth for:

• repositories and branches,
• revision history and metadata,
• users, groups, and permissions,
• change lists and other workflow state.

Clients connect to the Kimura server to authenticate, query state, and perform operations that update server history.

The Kimura server vs. File Servers

The Kimura server manages coordination and history. File servers handle file content storage and transfer.

This split lets Kimura stay centralized for correctness (one authoritative history and access control), while still scaling file distribution by using multiple file server endpoints.

How Users Experience The Kimura Server

In day-to-day use, you interact with the Kimura server through:

• connecting/disconnecting in the Visual Client,
• seeing repository/workspace state populate after connecting,
• submitting change lists (which updates server history),
• seeing other users’ operations show up (active operations, locks, etc.).

Offline Work And Returning Online (Auto-Reconcile)

You can change files locally while disconnected. When you reconnect, the workspace uses Live reconcile (auto-reconcile) to detect differences and help you bring your workspace back in sync with the server’s latest state.