Discofork
Repository brief

Kong/insomnia

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T16:03:02.783Z
1mo ago

Kong/insomnia

Kong/insomnia is a large, active, open-source cross-platform API client built on Electron. It supports GraphQL, REST, WebSockets, SSE, gRPC, and other HTTP-compatible protocols, with local, Git, and cloud storage options. The repo is active on the develop branch, has high community interest, and recent commits show ongoing release and feature work.

GitHub
Loading tags...
Stars38,235
Forks2,260
Default branchdevelop
Last pushed2026-03-30T14:59:08Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork if your priority is a local-first, cloud-free Insomnia variant and you can accept major staleness. Choose upstream if you need current features, active maintenance, and broad protocol/support parity.

Choose this fork only if avoiding the post-2023 login/account direction matters more than staying current. If you need active maintenance, latest protocol/tooling fixes, or cloud-collaboration parity, upstream is the safer choice.

Choose this fork only if you specifically want the older CLI-centric behavior. For most adopters, upstream is far safer because this fork is years behind and appears to have dropped the modern desktop and collaboration feature set.

Choose this fork only if you want the AI-oriented customizations and are prepared to live with a stale, heavily diverged codebase. If you want broad upstream compatibility, current fixes, and lower maintenance risk, upstream Insomnia is the safer default.

Choose this fork only if you specifically need its older gRPC-oriented behavior or legacy baseline. For most adopters, upstream is the better choice because this fork is substantially stale and far behind current Insomnia development.

Prefer upstream unless you specifically need this exact older snapshot. This fork adds no visible capabilities and is materially behind upstream, so it is a weak adoption choice for anyone wanting current features or fixes.

Choose this fork only if the Git-centered features and local-control behavior are the main goal. If you want an actively maintained API client with the latest upstream fixes, runtime upgrades, and broader feature continuity, upstream Insomnia is the safer default.

Choose this fork only if you need its downstream packaging or customization work and are willing to absorb merge debt. If you want the latest Insomnia behavior, active fixes, and current protocol/workflow support, upstream is the better default.

Choose this fork only if you need its older custom behavior and are prepared to own the maintenance gap. For most adopters, active upstream Insomnia is the safer default because this fork is stale and materially behind.

Choose this fork only if you need a legacy Insomnia snapshot with a few targeted behavioral changes. If you want an actively maintained API client with current features, this fork is a poor fit because it is far behind upstream and likely expensive to keep aligned.