inbrowser.link

What it is

inbrowser.link presents itself as an “IPFS Service Worker Gateway”: a static HTML page that bootstraps a verifiable IPFS gateway in the browser. The page emphasizes that it fetches each block from peers and verifies it against its CID, so its core value proposition is not the speed or convenience of a traditional hosted gateway, but browser-side content verifiability.

Core features and technical aspects

In terms of functionality and use cases, it is suited to scenarios where users want to reduce their trust dependence on centralized IPFS gateways. Its Service Worker model means the gateway logic runs in the browser environment, theoretically offering an experience closer to endpoint-side verification when accessing IPFS content. As for languages and frameworks, the page only explicitly mentions a static HTML page and Service Worker; it does not provide details on implementation language, framework, browser compatibility, or dependencies. API/SDK support and integration ecosystem are also not disclosed; the only clear point is its relationship with IPFS peers and CID-based verification.

Pricing, open source, and deployment

The captured content does not provide pricing information, nor does it mention payment methods, free quotas, or commercial plans. Its open-source or closed-source status is likewise unknown. For self-hosting, while the “static HTML page” description suggests the deployment model may be lightweight, there is no explicit text confirming whether self-hosting is allowed, how to deploy it, or whether there are license restrictions.

Pros and cons

Its strength is a clear positioning: verifying each block by CID and highlighting the trust properties of IPFS content addressing. The combination of a static page and browser-based gateway is also relatively lightweight. The drawbacks are equally clear: documentation is extremely limited, with no installation steps, examples, limitations, performance notes, security boundaries, or maintenance status. In poor network conditions or when peers are unreachable, the experience may be unstable.

Who it is for and access from China

It is best suited to developers familiar with IPFS, decentralized application experimenters, security researchers, and users who want to verify IPFS content rather than fully trust public gateways. The page does not provide enough information to judge accessibility from China. IPFS peer connections themselves may be affected by network conditions, so it is advisable to prepare alternatives such as public gateways, Brave’s built-in IPFS support, Helia/js-ipfs, or Kubo.