VERSION CONTROL FOR UNREAL ENGINE

Perforce-grade workflows. Rebuilt around your assets.

Exclusive checkout, atomic changelists and complete history, with adaptive binary storage, resilient operations and a desktop app made for Unreal teams.

Self-hosted Asset-aware history Guided Perforce migration

layers Atomic changelists
lock Exclusive asset locks
inventory_2 Immutable revisions
restart_alt Resumable operations
Why Kenavo

Three pillars. One Unreal-first stack.

Safe binary workflows without the operational weight of a legacy version control stack.

fingerprint

History that follows the asset.

Rename or reorganize Unreal content without turning one asset into an unrelated delete and add. Kenavo keeps identity, history and move context together.

compress

Store what changed, not another full copy.

Kenavo automatically chooses between a compressed full blob and a verified parent delta for each eligible version. No manual storage mode to tune.

sync

Built to recover, not restart.

Durable checkpoints, idempotent operations and explicit recovery states keep interrupted work visible and resumable.

Daily workflow

Checkout. Changelist. Submit. History.

The reason to adopt Kenavo is the everyday loop. Migration only lowers the risk of switching.

01

Exclusive checkout

Lease the asset before you edit. Content Browser shows who holds the lock.

02

Atomic changelists

Submit everything or nothing. Revisions are immutable once accepted.

03

Readable history

Search paths, filter by operation, see move summaries before opening thousands of files.

04

Editor + Desktop

Same agent truth in Unreal and Kenavo Desktop: status, locks, submit, sync.

Unreal-native

Useful history by default.

Kenavo starts with Unreal-aware ignore and binary policies. Generated BuiltData can keep only its current version while source assets retain their complete history.

Stable asset identity

Moves keep a durable AssetId. Old path → new path shows in history, even when binary content also changed.

Safe defaults, still visible

Rules for DerivedDataCache, Intermediate and Saved. BuiltData can be HEAD-only. Policies stay editable at create and migration time.

OFPA-aware changelists

Moving a map moves open __ExternalActors__ / __ExternalObjects__ paths with it.

Understand the change at a glance

Filter Moved, Added, Deleted, Modified. Large revisions stay searchable with a readable summary, not a wall of paths.

Move tracking

Moves stay moves, even when content changes too.

Reorganize Content Browser folders without shredding history into deletes and adds. Kenavo tracks identity across renames and keeps old path → new path readable in every revision.

drive_file_move

True move representation

A rename is recorded as a move, not an unrelated delete + add. Filter by Moved, search current or previous paths, and open history that still points at the same asset.

fingerprint

Identity survives content edits

Move and edit in the same changelist: the durable AssetId stays intact while adaptive storage still chooses full blob or parent delta for what actually changed.

manage_search

Readable large changelists

See a revision summary at a glance (moved, added, deleted, modified) before opening thousands of files. Virtualized lists keep big reorganizations usable.

history_edu

Migration that recovers moves

When Perforce recorded a delete + add, Kenavo can conservatively reconstruct moves so imported history keeps continuity instead of broken identities.

History line
Content/Legacy/Harbor_P.umap arrow_forward Content/Maps/Harbor_P.umap Moved · same AssetId
Perforce migration

Leave Perforce, not your history.

Migrate changelists, authors, dates, descriptions and asset history through a guided desktop workflow. Pause safely, survive a server restart and resume from the last durable checkpoint.

  • check Analyze and estimate before you move
  • check Waiting for Perforce / Authentication required, then continue
  • check Origin options locked and reused on resume
  • check Final report with storage, ParentDelta, moves and verification
Migration states
Analyzing depot Complete
Waiting for Perforce
Resume from checkpoint Next
Verify final state Pending

An interruption is not a failed migration. Kenavo waits, reauths when needed, then continues.

Choose deliberately

Kenavo or Perforce?

An honest matrix, not a caricature. Kenavo is a modern alternative for small and mid-size Unreal studios, not a claim to beat Helix on every topology.

Need Kenavo Perforce Helix Core
Large binary assets Native, with deduplication and adaptive storage Native, proven revision storage
Identity after moves Stable AssetId and move-oriented history Primarily path-based with move metadata
Atomic changelists Yes Yes
Exclusive locks Yes, asset-oriented Yes, mature and widely integrated
Leaving Perforce mid-migration Pause, reconnect, and resume from a durable checkpoint You are migrating away from Helix; Kenavo is the destination
Desktop experience Modern UI centered on project and history P4V: rich and mature
Deployment Simple central server, self-hosted Advanced administration and topologies
Choose Kenavo if
  • · You want Unreal checkout, changelists, and asset history without Helix ops
  • · You care about move tracking, adaptive storage, and resumable recovery
  • · You prefer Host PC today and Kenavo Cloud when you outgrow it
Stay on Perforce if
  • · You already depend on Helix enterprise admin and tooling
  • · Your studio needs the broad Perforce ecosystem as a hard requirement
  • · You are not looking for an Unreal-first alternative yet

See what your Perforce history becomes before you move.

Analyze the depot, estimate the migration and keep the original settings in a durable plan. If the server disappears, Kenavo waits. If authentication expires, it asks for the password. Then it resumes from the last verified checkpoint.

Ship worlds, not merge conflicts.

Download Kenavo and keep the safe binary workflows your studio relies on, with history that follows the asset.