CraftSuiteHubPhotoCraft Rust, desktop, CLI and WebAssembly explained
Understand the shared engine and the different execution environments; our browser build is pinned to v0.7.0.
Why does a Rust application run in a browser?
Rust is a programming language; WebAssembly is a compilation target browsers can execute. The PhotoCraft repository describes a Rust image editor with native, CLI and browser interfaces. Sharing an engine does not guarantee that every interface exposes the same commands or works in the same environment.
| Interface | Where it executes | What to validate |
|---|---|---|
| Native desktop | Operating system | Installation, graphics device and file compatibility |
| WebAssembly | Browser | Engine loading, memory, file access and export |
| Command-line tool | Local process or managed server | Supported commands, arguments and resulting files |
| Cloud Agent service | Hosted infrastructure | Isolation, authorization, billing and durable delivery |
Our pinned browser build
CraftSuiteHub's manual workspace uses the official v0.7.0 web release, pinned in our engine manifest. We check the web artifact before building the site. This is a version choice for reproducibility, not a claim that the workspace follows every upstream change immediately.
Our observed browser test imported a PNG, applied a brush change, downloaded a PNG and reopened it. Separately, local CLI trials produced contain/crop resize samples and project files. Those are different tests. Native CLI commands are not available simply by sending messages to the browser iframe.
Local computation and privacy
In the current manual workspace, selecting a local file supplies it to the embedded browser editor. Our site does not send selected image bytes to a cloud image-processing endpoint. Loading the site still involves network requests for the application and engine assets, and public-page analytics may record visits after consent. “Runs in a browser” alone does not prove that every website keeps files local.
To investigate another editor, inspect network destinations and request payloads with a non-sensitive sample. Reloading a downloaded output checks delivery; testing offline may provide supporting evidence but is not a complete privacy audit. Consult our privacy page for the current implementation.
Why we keep cloud Agent actions unavailable
A hosted command runner needs isolation, access control, resource limits and a durable job lifecycle. A successful local resize does not prove these properties. We therefore do not sell Agent credits or offer cloud batch processing.
Start with manual PNG editing, or use the official Windows download guide if you need a desktop application.
Last checked: October 13, 2026. Official product claims and our observed tests are identified separately.