Centralized Server And File Servers

Kimura SCM is a centralized system:

• The Kimura server is the source of truth for coordination and metadata (users/groups, permissions, repository structure, revisions/history, change lists).
• Clients (Visual Client, file servers) connect to that server to read state and perform operations.

This centralized model makes it easier to enforce consistent access rules and keep one authoritative history.

Where File Servers Fit

Kimura uses file servers to handle file content storage/transfer. This provides a practical way to scale and somewhat decentralize file distribution while keeping the central server as the authority for history and permissions.

Common patterns include:

• a default file server hosted alongside the server (FS-DEFAULT), and/or
• standalone file servers (for additional capacity, redundancy, or closer geographic proximity to users).

From a user perspective, this often shows up as choosing file server endpoints when creating a workspace or in Settings.

Working Offline And Returning Online (Auto-Reconcile)

You can make local changes while disconnected (for example edits, adds, deletes on disk). When you reconnect, the workspace uses Live reconcile (auto-reconcile) to detect what changed and present it in a structured way (Modified/Added/Missing/Not at latest revision).

This helps you safely re-align your workspace with the server’s latest state after being offline, without manually auditing a large tree.