MZSoft Studio
About the studio
A small studio with a large shelf
MZSoft Studio builds focused software for Apple platforms and the browser. Twenty-three products so far — photo and media tools, productivity utilities, navigation instruments, developer tooling — each one written around the same constraint: your data stays on your device.
What we build
4 areasCapture, repair, colorize, and clean up — the heaviest models we ship, all running locally.
12 products →Translation, transcription, PDF surgery, language practice. Small tools that remove a daily chore.
8 products →Coordinates, speed, routes, disk space. Precise readings for people who depend on them.
6 products →What we built for ourselves and decided to ship — screenshot tooling and a server console.
2 products →How we work
4 principlesPrivacy by architecture
Processing happens on the device. No accounts, no analytics SDKs, no silent uploads. That is a design constraint we accept up front, not a policy page we write afterwards.
One job, done completely
Each app covers a single intent end to end. We would rather ship a second app than bolt a second purpose onto the first.
Owned, not rented
Where the work allows it, you buy the app once. Subscriptions only exist where there is a real recurring cost behind them.
Short cycles, real support
Releases land in weeks, not quarters. Support mail reaches the person who wrote the code, and typically gets an answer within a business day.
Founder
Yongliang Wang
Founder & sole engineer · Berlin, Germany
MZSoft Studio is one person. The backend, the apps, the on-device model plumbing, the release pipeline and the support inbox all land on the same desk — which is exactly why the products stay narrow and the privacy claims stay true. There is no data team here that would benefit from collecting your photos.
The other side of that résumé is fifteen years of platform engineering: Golang services, Kubernetes, multi-cloud infrastructure and monitoring at the scale of ten thousand nodes, most recently as a Senior Platform Engineer on a cloud security platform. The studio is where that infrastructure discipline meets a product surface people actually touch.
Open source
github.com/fdddfTools that came out of building the products, released because someone else was going to hit the same wall.
XCStrings translation toolkit — CLI plus web and desktop GUI, running concurrent translations through Google, DeepL, Baidu and OpenAI.
View on GitHub →A flexible proxy server for OpenAI-compatible APIs, with a Vue admin interface for keys, routing and quotas.
View on GitHub →The two-step rating prompt and in-app feedback form used across our iOS apps, with a Cloudflare Worker collector behind it.
View on GitHub →One command to pull AI models down to a machine — the piece that kept getting rewritten until it became a tool.
View on GitHub →sherpa-onnx packaged as an xcframework over SPM, so on-device speech models drop into an Xcode project cleanly.
View on GitHub →Self-hosted SPM distribution of the ONNX Runtime ObjC bindings, built so Xcode Cloud can resolve them without a mirror outage.
View on GitHub →Talk to the studio
Support questions, bulk licensing, partnerships — the same inbox, answered by the person who built it.