Runs where you run it
A workstation, a NAS or a server in the studio closet. Files land on your own disk — or your own S3 / MinIO bucket.
Self-hosted · 3D & game assets · 100% Rust
Your assets stay
in your hangar.
Hangar is a self-hosted digital asset manager for 3D and game content. Version models, textures and audio like code, preview every change in the browser, and keep your unreleased work on hardware you control.
● No cloud account · No telemetry · Runs on your own network
Why Hangar exists
Your unreleased work shouldn't live on someone else's servers.
Characters, vehicles and whole worlds that haven't shipped yet are a studio's most valuable — and most sensitive — data. Cloud asset platforms ask you to hand over a copy of all of it, under terms you don't write. Hangar was built to keep that workflow in-house: the same comfort, none of the exposure.
Nothing phones home
Just the Hangar server and PostgreSQL. No external accounts, no SaaS dependency, no telemetry, no third-party calls.
Access on your terms
Projects with roles. People outside a project can't even tell an asset exists. Editor plugins use revocable tokens.
Processed locally
Conversion, LODs and thumbnails run on your machine. The 3D viewer renders in the browser from bytes your server already holds.
Your IP, your hardware, your rules. Hangar gives you a modern asset pipeline without making your art someone else's data.
What it does
A real asset pipeline, not a file share.
Drop in an FBX, a folder of textures or a whole package. Hangar versions it, converts it and gives your team a browser preview within seconds.
01 · Versioning
Versioned like code
Every asset has an immutable history over a content-addressed blob store. Fix a hull mesh and only the new FBX is uploaded — the 4K textures keep pointing at the same blobs.
- Snapshots
v1 → v2 → v3with parents — branch from any version - Files hashed with BLAKE3 in the browser; only missing blobs are sent
- Diff, pull and roll back from the web or the CLI
02 · Pipeline
Automatic LODs and web previews
Each new version is processed in the background: FBX, glTF and OBJ become web-ready GLBs, one per level of detail. Authored _LOD1 meshes are kept; missing ones are generated.
- Broken FBX texture paths resolved, PBR slots detected automatically
- Texture variants (
Desert/,T_Body_Woodland_D) become switchable skins - Thumbnails, stats and animation clips extracted per version
- Optional headless Blender for
.blend,.dae,.3dsand friends
03 · Viewer & materials
A real 3D engine in your browser
The viewer is Bevy compiled to WebAssembly. Orbit, switch LODs for an A/B compare, play animations frame by frame, and tune materials with a live preview before committing a new version.
- Per-material slot overrides: base color, normal, ORM, specular, opacity…
- Shared texture sets linked across assets
- Skeletal and node animation, previewed on reference skeletons
Send to Unreal
Pair the Unreal Engine editor plugin once, then push any version straight into your project with one click.
Command-line client
hangar push a folder as a new version, pull, diff, status. Fits right into build scripts.
Batch import
Turn every subfolder of a purchased package into its own asset, cloned from a template. Resumable.
Under the hood
Written entirely in Rust.
From the database to the pixels. One language across the server, the processing pipeline, the CLI and the browser — for performance where it counts and correctness everywhere.
hangar-serverREST API, auth, storage, job workers · summer-rs, axum, SeaORM, OpenDALnative
hangar-pipelineImport, LODs, GLB writer, thumbnails · ufbx, gltf, meshopt, imagenative
hangar-webThe whole UI · Leptoswasm
viewer3D viewer · Bevy on WebGL2wasm
hangar-clipush / pull / diff from the terminalnative
hangar-coreShared API types and the preview contractnative + wasm
// 01 Performance
Mesh simplification, texture processing and hashing run at native speed. In the browser, WebAssembly drives a GPU renderer and hashes multi-gigabyte uploads without a plugin.
// 02 Correctness
The same types are compiled into the server and the browser, so the contract between them is checked by the compiler, not by hope. Memory safety without a garbage collector.
// 03 Integrity
Blobs are content-addressed and immutable. Uploads are re-hashed on arrival and rejected on mismatch, so what you stored is exactly what you get back.
Get started
Up and running in minutes.
Grab a prebuilt release, or build from source. All you need besides Hangar is PostgreSQL.
Build from source
# database (PostgreSQL via Docker) $ docker compose up -d # web UI → crates/hangar-web/dist $ cd crates/hangar-web && trunk build --release && cd ../.. # server — open http://localhost:8100 $ cargo run -p hangar-server --release
The first user to sign up becomes the administrator.
Push from the terminal
$ hangar login --server http://hangar.local:8100 --user ana # a folder becomes a new version — only changed files upload $ hangar push <asset-id> ./Abrams -m "Fix hull normals" --wait $ hangar versions <asset-id>
Requires Rust stable with the wasm32-unknown-unknown target and Trunk to build the UI.
Bring your assets home.
Download Hangar, point it at a disk you own, and give your team a versioned, previewable asset library that never leaves your network.