halvor.
VERSION CONTROL FOR CODE AND LARGE ASSETS

Manage large assets.
Keep your team moving.

Keep source code, 3D models, textures and audio in one versioned project. Lore lets contributors work with the files they need and reuses matching content across revisions. Halvor is building the managed hosting and collaboration hub around it.

Code + assets in one historyReview the complete changeNo server admin

For teams building with code and large assets · Pilot access coming

What changes with Lore? ↓
team / projectONE LORE PROJECT
RepositoryIssuesReviewsReleases
Code and assets. One project history.Track related files together. Review the complete change.
  • Source / Controller.cppCODE
  • Scenes / Environment.sceneLEVEL
  • Models / Assembly.fbxMODEL
  • Textures / Surface.pngTEXTURE
  • Audio / Environment.wavAUDIO
JD
Jamie · Artist

Model and textures updated in this revision.

AK
Alex · Developer

Related code updated. Ready for team review.

● Review requestedCode + assets · one revision

Workflow illustration · not a product screenshot

Code and large assets, versioned together. Hosting and collaboration, managed by Halvor.Independent project. Not an official Epic Games service.
WHY YOUR TEAM NEEDS IT

Large assets are part of the project. Treat them that way.

When code, scenes, models and sound change together, your team needs to know which versions belong together. That matters whether you’re making a game, an animation, a simulation or a design.

01 / TRACK THE COMPLETE PROJECT

Keep related versions together.

Record code and binary assets in the same history, so contributors can find the files that belong to a revision.

02 / GET THE FILES YOU NEED

Choose your working set.

Use Lore’s sparse views to work with selected folders instead of downloading every file in the repository.

03 / REUSE UNCHANGED CONTENT

Store matching content once.

Lore splits files into reusable chunks. Revisions can share matching chunks; the savings depend on the files and how your tools export them.

THE POWER OF LORE

Version control built for code and large assets.

Lore is Epic Games’ open-source version control system. It combines code and binary assets in one workflow, with sparse working sets and content reuse built into its design.

One workflow for different file types.

Stage, commit and share source files and large assets as part of the same project.

Local commits and branches.

Record changes locally and use branches to separate work before sharing it with the team.

An open-source foundation.

Lore is MIT-licensed. Halvor’s proposed paid service is the hosting and team workspace around it.

Read Lore’s system design ↗Explore Lore’s concepts ↗

WHY USE LORE THROUGH HALVOR?

Use Lore. Build together. Leave the hosting to us.

Lore provides version control. Halvor is building the place your team uses it: managed repositories with issues, reviews and releases in a shared browser workspace.

Spend less time running a server.

Managed setup, upgrades and recovery are the service we’re building, so your team can focus on its project.

Keep discussion with the work.

Connect issues, reviews and releases to the repository, rather than piecing the context together from scattered messages.

Know what you’re paying for.

Pilot pricing, storage, transfer and support allowances will be agreed before participation. No unlimited-use promises.

What is available today?

Halvor’s hosted hub is in development; public pilot access is not open yet. Lore is pre-stable 0.x, with advisory locks. Evaluate it on a contained project before considering a production migration.

Lore’s current capabilities and limitations ↗

Try managed Lore with your team.

Join the pilot waitlist to evaluate a real project with a teammate: version your files, share a change and test the hosted workflow.

Join the pilot waitlist ↗Access, allowances and pricing will be confirmed before participation. Public hosting is not open yet.
New to Lore?

Start with the concepts and a disposable local practice project.

Learn Lore →