# INCY Desktop and Mobile Downloads, Features, and Release Limits

> INCY is a cross-platform proxy client built on Xray-core, with releases for mobile, TV, Windows, macOS, and Linux. Its subscription, routing, DNS, and kill-switch features are substantial, but the desktop client remains explicitly pre-alpha.

**INCY-DEV/incy-platforms** — INCY downloads and release info

- Repository: https://github.com/INCY-DEV/incy-platforms
- Stars: 1,540 · Forks: 66
- Language: Python
- License: not declared
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/incy-dev-incy-platforms

## What INCY Solves and Which Platforms It Targets

INCY addresses the problem of controlling Xray-compatible proxy connections from more than one device category. The README describes it as a cross-platform proxy client built on Xray-core, with mobile and TV applications plus desktop packages for Windows, macOS, and Linux. The protocol list includes `VLESS (Reality)`, `VMess`, `Trojan`, `Shadowsocks`, `Hysteria2`, `SOCKS5`, and `WireGuard`. That breadth makes the client relevant to users who already have servers or subscriptions using those protocols, rather than to people looking for a managed VPN subscription. The README explicitly says that INCY does not provide VPN services.

The repository is primarily a distribution and release hub. Its top-level files include `RELEASE.json`, `RELEASING.md`, `obtainium.json`, scripts, and tests, while the application itself is distributed through the linked stores and GitHub releases. The README does not document a Python package, a command-line interface, or a server deployment procedure. Therefore, the repository's Python classification should not be interpreted as a documented Python installation path. Based on the repository layout, users normally consume packaged applications rather than install a library from source.

There is an important product-status distinction. Mobile and TV builds are offered through the App Store and Google Play, and Android users can also obtain a signed APK. The desktop client has a warning that labels it pre-alpha. The same warning says it is usable day to day, but it also warns of rough edges and breaking changes between releases.

## INCY Subscription, Routing, and Xray Data Flow

The documented configuration model has three layers. First, users can add subscriptions by URL, QR code, or share link, with automatic refresh. Second, routing profiles can split traffic by domain or IP into proxy, direct, or blocked paths. Remote and domestic DNS settings are separate, which gives users explicit control over how name resolution is handled for different traffic groups. Third, INCY supports importing raw Xray JSON, including observatory, balancers, and custom geo files.

That structure gives INCY a different starting point from a minimal client that only toggles a single server. A subscription can act as the main source of server definitions, while a routing profile controls how matching traffic is treated. Raw JSON import remains available for users who need Xray-specific objects that the subscription UI may not expose. The README does not describe the internal parser, refresh interval, conflict precedence between subscription and imported JSON, or the exact rule used to combine multiple routing sources. Those are implementation details a technical adopter would need to confirm in the linked documentation.

The feature table also documents TLS fragmentation. Its stated purpose is to fragment the ClientHello past DPI, with configurable packet type, length, and interval. This is a targeted traffic-control mechanism, not a general-purpose guarantee that every network will behave in a particular way. The kill switch provides a separate continuity control: the README says it cuts traffic if the tunnel drops so traffic does not escape through the gap. Per-app proxy support is listed for Android desktop clients, while the Mobile & TV column does not list that feature as available across the entire mobile set.

## INCY Downloads for Windows, macOS, Linux, Android, and TV

The README separates mobile and TV distribution from desktop distribution. iOS, Apple TV, and macOS mobile users are directed to the App Store. Android and Android TV users are directed to Google Play. Android users who prefer sideloading are given a direct APK link for `android-v3.7.0`, described as a signed APK with a checksum in the release process notes.

Desktop downloads are published as GitHub release assets. For Windows, both x64 and ARM64 are listed, each with a setup executable and a portable ZIP. macOS packages are architecture-specific: Apple Silicon receives an ARM64 DMG, while Intel receives an Intel DMG. Linux x64 and ARM64 builds provide DEB, RPM, Arch package, and portable ZIP options. The release table does not list a Linux package for other architectures.

The current desktop assets shown in the README belong to `desktop-v3.8.10`. The release list also records Android `android-v3.7.0` and desktop `desktop-v3.8.8` as recent releases. Android and desktop version numbers are independent. The README states that Android releases use the `android-vX.Y.Z` tag format with titles such as `Android vX.Y.Z`, while desktop releases use `desktop-vX.Y.Z`. This distinction matters for update automation because GitHub's global latest release can be a desktop build even when an Android update is available.

## Obtainium Configuration for INCY Android Updates

INCY documents an Obtainium configuration rather than a manual shell installation procedure. The repository includes an `obtainium.json` file and an import link. The documented settings identify `https://github.com/INCY-DEV/incy-platforms` as the source, filter release titles with `^Android v[0-9]+\.[0-9]+\.[0-9]+$`, and filter APK names with `^[Ii]ncy\.apk$`. Version extraction uses `[0-9]+\.[0-9]+\.[0-9]+`.

The configuration also says to turn `Verify Latest Tag` off because GitHub's global latest release may be a desktop release. `Fallback to older releases` should be on, according to the README. Those settings are not cosmetic. Without the title filter, an update client could treat a desktop release as the relevant Android update. Without the older-release fallback, a mixed release or a temporarily unsuitable latest tag could prevent the updater from finding the signed Android APK.

The README says new Android releases contain only the signed APK and its checksum, while older mixed releases remain available for existing direct links. This is a packaging transition rather than a documented break in the application configuration. It does mean that users who depend on hard-coded GitHub release URLs should check whether the asset path still matches the latest release format.

## INCY Privacy, Telemetry, and Support Boundaries

The privacy statement says that servers, keys, and subscriptions never leave the user's device. It also distinguishes mobile and desktop crash reporting. Mobile builds include Firebase Crashlytics for crash reports. The desktop client sends no telemetry at all, according to the README. Those statements describe the project's stated data behavior, but they do not replace reviewing the linked application documentation or understanding the external services involved in account installation, crash processing, subscription sources, or network traffic.

Support is routed through `feedback.incy.cc`. The README says that reports sent through chat, direct messages, or GitHub issues will be lost. It asks users to include the app version, platform, expected behavior, and, for tunnel problems, logs from Settings. Questions and general discussion are directed to `@incy_public`. This workflow is important for adoption because the repository is not presented as the primary issue tracker. A bug report filed as a GitHub issue may not enter the project's stated support process.

The documentation also states that INCY collects nothing and sells nothing, and it lists donation channels. That is a project statement rather than an independently verified audit. The repository does not provide a license identifier, so redistribution, modification, packaging, and commercial-use questions cannot be answered from its license metadata. The legal section is truncated after stating that users are responsible, so the full legal terms are not available here.

## INCY Maintenance Signals and Upgrade Cost

The repository is not archived, and the last push was on 2026-10-14. The recent release history includes desktop `desktop-v3.8.10` on 2026-10-14, Android `android-v3.7.0` on 2026-10-06, and desktop `desktop-v3.8.8` on 2026-09-22. Those dates indicate recent publishing activity, but the README still labels the desktop client pre-alpha. Recent release frequency therefore does not remove the project's own warning about rough edges and breaking changes.

Upgrade cost is higher for desktop users who depend on stable behavior across releases. A new desktop version can change behavior between releases, and the repository does not document a rollback procedure. Mobile users may face a more conventional store-based update path, but the Obtainium instructions show that update automation must account for independent Android and desktop tags. The Android release format also has a transition from mixed releases to releases containing only the signed APK and checksum.

The repository's license is unknown. This is a direct constraint for engineering organizations that need to review source rights, distribute modified builds, or include the client in another product. The absence of a confirmed license in the available repository information should be resolved before adoption; the README's free and donation statements do not establish the permissions needed for redistribution or commercial integration.

## INCY's Pre-Alpha Limits and a Different Update Approach

The clearest limitation is the desktop maturity statement. INCY provides installers and portable archives across several desktop architectures, but it labels the desktop client pre-alpha and warns that breaking changes may occur between releases. Users who need predictable upgrade behavior should treat each desktop release as something to validate before replacing a working installation. The README does not provide migration notes, compatibility guarantees, or a rollback command.

A different update approach is manual APK installation from the direct GitHub link instead of Obtainium. The manual route gives the user a specific `Incy.apk` asset and a checksum, but it does not automate release selection or version detection. Obtainium configures filtering, version extraction, tag handling, and fallback behavior, which is more appropriate when Android and desktop releases share one repository. The trade-off is that Obtainium depends on a separate application and on the configuration remaining aligned with INCY's release format.

INCY is also not the right tool for someone who wants a provider-managed VPN service. It works with configured servers, subscriptions, and raw Xray JSON. Users who need a turnkey service, bundled server access, or a provider account should look elsewhere. Users who already operate compatible endpoints and need local routing and DNS decisions have a clearer reason to evaluate it.

## Conclusion

INCY is suitable for users who want one Xray-oriented client across supported desktop and mobile systems, especially those who need subscriptions, domain or IP routing, custom DNS, and a kill switch. It is a poor fit for users who require a stable desktop release with predictable upgrade behavior, or for anyone who cannot accept the possibility of breaking changes between pre-alpha builds. Before adoption, check the README for your exact operating system and architecture, read the desktop warning, inspect the stated protocol requirements, and confirm how the repository's unknown license status affects your intended use. The first factual checkpoint is the package format available for your platform: App Store or Google Play for mobile, or an installer, DMG, DEB, RPM, Arch package, or portable archive for desktop.

## FAQ

### How do I download INCY for desktop?

The README links Windows setup and portable ZIP files, macOS DMG files for Apple Silicon and Intel, and Linux DEB, RPM, Arch, and portable ZIP packages. Desktop assets shown in the README are published under the `desktop-v3.8.10` GitHub release.

### Can I update INCY on Android with Obtainium?

Yes. The README provides an Obtainium import link and an `obtainium.json` file. It specifies filtering for Android release titles and `Incy.apk`, disabling `Verify Latest Tag`, and enabling `Fallback to older releases`.

### Is INCY suitable for production use?

The README explicitly labels the desktop client pre-alpha, while saying it is usable day to day and warning of rough edges and breaking changes between releases. The documentation does not provide a stability guarantee.

### Does INCY send telemetry?

The README says mobile builds include Firebase Crashlytics for crash reports, while the desktop client sends no telemetry at all. It also states that servers, keys, and subscriptions never leave the user's device.

## Sources

- [INCY-DEV/incy-platforms on GitHub](https://github.com/INCY-DEV/incy-platforms)
- [Issues](https://github.com/INCY-DEV/incy-platforms/issues)
- [README](https://github.com/INCY-DEV/incy-platforms/blob/main/README.md)
- [Releases](https://github.com/INCY-DEV/incy-platforms/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/incy-dev-incy-platforms