Version control and collaboration that keep production work visible and coordinated.

Keep authoritative history of source code, digital assets, and large binary files across repositories. Sync to the latest revision or retrieve a specific one, track file operations such as add, edit, delete, move, rename, and lock, and review pending work against newer revisions before applying it. Locks and visibility into active file operations help teams coordinate changes to binary assets that are difficult to merge.

See local and team activity in one workspace tree. Sync workspaces and get files from the latest revisions, then quickly find files that might need attention: files that are modified in the workspace, missing from the workspace, missing from the repository, or not at the latest revision.

Group related edits in named change lists for review, combine work from several repositories in one change list, or work with independent change lists in parallel. Save change-list revisions as local checkpoints before you are ready to submit, resolve pending edits against newer revisions, and apply the reviewed result. Active-operation and lock visibility helps you spot conflicts early.

Create local stashes as personal save points when switching tasks, use server stashes to hand work to another workspace, and share in-progress stashes with owner and viewer controls. Use stashes in CI/CD without losing pending work or context.

Map a workspace to the repositories and branches it needs, route history, sync, file checks, and submit to the right target, and apply server-side maps so the team shares one structure. Build workspaces from repositories with clear purposes and paths.

Set user and group permissions at repository, folder, or file level to control access and help prevent unwanted submission errors. Use locks and visibility into active file operations for busy files.

Kimura Server can run separately from the file servers that store and deliver large files. Add file servers as projects grow to increase transfer capacity and redundancy, while Kimura Server keeps history, permissions, and workflow state consistent.

Use TLS with server-certificate checks and optional client certificates, connect through OIDC/SSO with your identity provider, and route file-server access through Kimura server.

Use the same Visual Client and Visual Server applications for daily work and administration on macOS, Linux, and Windows. Use KSCM CLI for CI/CD and MCP automation, or connect an Unreal project to Kimura directly in the Unreal editor through the Unreal Engine plugin.

KSCM MCP keeps a workspace loaded between tool calls, while the CLI supports automation and coding agents. AI agents can inspect state, sync files, and use change lists or stashes, with Kimura signaling showing ownership, locks, active operations, and current state. Permissions, history, and attachments on change lists or stashes keep AI-agent work reviewable and controlled.