Hosting built on Lore
Built on Lore, Epic Games' open-source (MIT) VCS, for code and large binary assets.
LoreBucket
A collaboration platform built for large-asset teams
Built on Epic Games' Lore version-control core, with a BitBucket-like hosting and collaboration experience — natively designed for large files and game asset pipelines.
Highlights
Core features
Binary-first, large files
Chunked storage with fragment-level dedup — as efficient on multi-GB binaries as on text.
Content-addressed, verifiable history
BLAKE3 content addressing and a Merkle-tree hash chain — tamper-evident, byte-verifiable.
Sparse checkout & lazy fetch
Sparse workspaces with on-demand hydration — no need to download everything.
Lightweight branches
Branches are lightweight references; create, switch and sync with near-zero overhead.
Pull / merge reviews
Merge requests and code / asset review collaboration via the web UI.
File locking
File locks for unmergeable binary content to prevent concurrent conflicts.
Permissions & multi-tenancy
Partition-based access boundaries with per-directory authorization.
Full-surface API & SDKs
SDKs for C/C++, C#, Rust, Go, Python and JavaScript — easy CI/CD integration.
Specifications
| VCS core | Built on Epic Games' open-source Lore (MIT) |
|---|---|
| Storage model | Content-addressed immutable store (BLAKE3) + Merkle tree |
| Large files | Chunked storage with fragment-level dedup, binary-first |
| Workspace | Sparse checkout + on-demand hydration + local cache |
| History integrity | Immutable hash-chained revision graph, end-to-end push validation |
| Collaboration | Branch / merge / review, file locking |
| Transport & availability | Centralized source-of-truth, offline + resumable transfer |
| Access control | Partition-based multi-tenant isolation, per-directory authz |
| Interfaces | C API + SDKs for C/C++, C#, Rust, Go, Python, JavaScript |
| Advanced | Sub-repository links, Layers (overlays) |
Media
Interface preview
Under the hood: Lore
LoreBucket’s version-control core is built on Lore — a next-generation, MIT-licensed open-source version control system maintained by Epic Games, designed for workloads that combine code with large binary assets. Its architecture includes:
- Content-addressed immutable storage: all content is stored by BLAKE3 hash in an immutable data store, while mutable state such as branch pointers lives in a separate key-value store;
- Repository as a Merkle tree: revision state is organized as a hash chain, forming a verifiable, tamper-evident source of truth;
- Chunking and fragment-level deduplication: large files are stored as reusable, indexed chunks — equally effective on multi-GB binaries and on text;
- Sparse and on-demand hydration: workspaces fetch data only when needed, staying lightweight;
- Centralized with offline capability: a service-of-record model with offline work and resumable transfer, validated end-to-end by the server on push;
- Multi-tenant isolation: partitions act as access boundaries, with native multi-tenancy and per-directory access control;
- API-first: a C library as the primary interface, with SDKs for C/C++, C#, Rust, Go, Python and JavaScript.
How it differs from traditional Git hosting
- multi-GB binaries are handled as first-class content, not via add-ons like Git LFS;
- fragment-level dedup is as effective on large binaries as on text, unbounded by pack-delta heuristics;
- sparse checkout + lazy fetch work at any granularity — no full clone required;
- built-in file locking solves concurrent edits of unmergeable assets;
- multi-tenant isolation and verifiable history are built into the architecture.
Who it’s for
LoreBucket suits teams that need version control and collaboration for large files and assets:
- game studios and publishing teams;
- digital-twin and large-scene R&D teams;
- any R&D team needing large-file version control.
Technical details reference lore.org and the Lore system design doc. Lore is maintained by Epic Games and open-sourced under the MIT license. “Epic Games”, “Lore” and related names and marks are the property of their respective owners; references here are for technical attribution only and do not imply any endorsement, sponsorship, or affiliation. Features and specifications are subject to the actual product release.