No cloud inference
Your face, camera, and call frames are processed on your own Windows machine.
Local identity system / Windows
One photo becomes a protected camera persona for Zoom, Meet, Telegram, Discord, and anywhere else that accepts a webcam. Everything happens on your GPU.
00 / WHY HUANTU
Face-swap tools make you manage models, terminals, drivers, and fragile routing. Huantu turns that machinery into one protected action: select a persona, verify the caller view, and enter the call.
01 / LOCAL PIPELINE
The physical camera stays behind Huantu’s final identity boundary. Calling apps see only transformed frames, a short approved hold, or black.
Your face, camera, and call frames are processed on your own Windows machine.
No Python environments, CUDA toolkits, OBS scenes, or manual camera plumbing.
If transformed output becomes unsafe, Huantu closes the route instead of exposing you.
02 / IDENTITY LIBRARY
One card holds the chosen face, consent record, quality settings, and eventually the voice profile. Switching identity becomes one transaction.
03 / FAIL-CLOSED
Tracking loss, engine failure, restart, or panic never routes the physical camera through to the call. The boundary changes directly from transformed output to black.
04 / THE INSTALL MIRACLE
Huantu detects the machine, prepares the local runtime, installs its camera, and surfaces problems in plain language. You operate identities—not infrastructure.
05 / ONE CAMERA, EVERYWHERE
If an app can select a webcam, it can select Huantu Camera.
PRIVATE BETA / WINDOWS
Huantu’s protected face system is working now. Voice identity is in development. Join the first group testing real calls and new identity engines.
Request private beta Face available now · Voice coming next