LoginSign Up
← Back to all sparks
H

Hoppscotch

INFRA · APIS
Velocity5.0

Open-source API development and testing platform

hoppscotch.io ↗

A browser API client rebuilding itself as self-hosted infrastructure — while its cloud loses collections.

api-clientself-hosteddesktop-apppostman-parityreliabilityenterprise
◆Current state
Hoppscotch ships on a roughly two-week train, and the substance has moved off the web app onto the desktop client and self-hosted deployments: cookie persistence, connection timeouts, arbitrary non-root container UIDs, SMTP OAuth2, configurable proxy URLs. The last three releases have been dominated by a personal-workspace data-loss incident that forced a cloud rollback, deferred a Cloud Desktop release, and was only resolved in 2026.7.0. Enterprise-only patches now appear in the same feed as community ones.
◆Where it's heading
The centre of gravity is shifting from the free browser tool toward a deployable product with an operations surface — the changes that matter are about running Hoppscotch, not about calling APIs with it. Feature work is Postman-parity catch-up (collection-level scripts, OpenAPI 3.1 export, API doc versioning) rather than anything that redefines the client. Meanwhile the reliability debt is visible in public: three consecutive releases carried an incident banner.
◆Prediction
Expect the next releases to keep hardening self-hosted and Desktop paths and to restore the deferred Cloud Desktop track, with continued Postman-parity feature fills rather than a new capability class.

◆Recent moves

  1. 5d ago

    Collection data-loss fixed; empty env vars fall back to initial values

    Closes the personal-workspace data-loss issue that had been flagged across the previous two releases and forced a cloud rollback. The rest is operational polish on the paths Hoppscotch has been investing in — configurable Desktop connection timeouts and a fallback to initial values for empty environment variables.

    View source ↗
  2. 20d ago

    Self-hosted-only patch: non-root container UIDs, Desktop login loop fixed

    A self-hosted-only patch that skipped cloud entirely while the data-loss issue was open — a clear signal of where the deployment split now sits. Arbitrary non-root container UIDs and response-cookie capture for Agent-routed requests are exactly the operator-facing concerns driving this phase of work.

    View source ↗
  3. 1mo ago

    Desktop cookie persistence and OAuth2 ID token support

    Cookie persistence on Desktop and ID token support across OAuth2 flows continue the pattern of the Desktop client absorbing capability the browser version cannot offer. This is also the release where the personal-workspace incident surfaced publicly and the cloud deployment was rolled back.

    View source ↗
  4. 2mo ago

    OpenAPI 3.1 collection export and admin-configurable proxy URLs

    OpenAPI 3.1 export closes an interoperability gap competitors already cover, while environment- and dashboard-configurable proxy URLs are aimed squarely at self-hosted operators. Both fit the parity-plus-deployability pattern rather than extending what the client can do.

    View source ↗
  5. 2mo ago

    Patch: script import regression and macOS blank screen

    A two-fix patch cleaning up a regression in the experimental scripting sandbox and a Desktop blank screen on older macOS. Housekeeping between feature trains.

    View source ↗
  6. 3mo ago

    Collection-level pre-request and test scripts

    Scripts move up from the request to the collection level, letting shared setup and assertions live in one place — the most substantive client-side feature in this window and another Postman-parity fill. Paired with SMTP OAuth2 for self-hosted mail, it shows the two tracks running in parallel.

    View source ↗