Kaption is becoming source-available

Kaption captures a user-selected region of the screen, runs OCR locally, matches the text against a dialogue database, and draws translated subtitles in a separate overlay. That is safe by design, but it is still reasonable for users to ask for proof.

Making the desktop client source available gives that proof a place to live. Anyone can inspect the capture path, OCR code, update checks, crash reporting integration, licence calls, and local configuration handling instead of trusting a black box.

The useful audit is not just "is the code online?" It is whether the public code explains the behavior users care about before running an installer.

Start with the desktop project and the service folders. The code shows how Kaption keeps itself outside the game process and why the app behaves like OCR plus a desktop overlay, not like a mod.

Source availability is scoped to the desktop client. It does not mean every operated service behind Kaption is public.

The official API, production release pipeline, deployment secrets, and proprietary translation packs are operated separately by Kaption. That boundary matters: users can audit the client behavior, while security reports about the hosted service still go through the security policy.

You do not need to understand every C# class to get value from the repository. Read the README first, then look for the folders that match the question you have.

If your question is "does it touch the game?", inspect capture, rendering, and network code. If your question is "what leaves my PC?", inspect the API client, crash reporting, and update service paths.

The public client code is offered under AGPL-3.0, with a commercial licence option for closed-source or commercial products that cannot comply with AGPL terms.

If you publish a fork, keep the source available under the required licence terms and use a different name and icon. That protects users from confusing unofficial builds with the official Kaption installer.