IPFS

Access Controls

Access Controls

Stop unauthorized access to dedicated IPFS gateways with private mode, token authentication, and a straightforward request flow.

Free 5GB storage + custom domain. No credit card required.

Keep private IPFS gateway content private Add token-based access to a dedicated IPFS gateway and keep authenticated delivery fast over HTTPS with built-in edge caching.

Where it fits

Access controls work best anywhere IPFS gateway content should stay private, cache at the edge, and remain limited to the users who should actually have it.

Member-only content

Serve paid or logged-in IPFS content through a dedicated gateway without exposing it publicly by default.

Protected app assets

Gate files, media, or application resources behind authenticated IPFS gateway requests instead of public URLs.

Internal and partner files

Share private IPFS content with teams, customers, or partners while keeping access on your terms.

Private IPFS delivery flows

Fit token-protected IPFS gateway delivery into existing applications without inventing a separate delivery path.

How it works

Three straightforward steps: lock down the gateway, generate a token, and send that token with the HTTPS requests your application makes to your dedicated IPFS gateway while edge caching keeps delivery fast.

1

Make the gateway private

Start with a gateway configured for private access so requests require authorization before content is served.

2

Generate an API token

Open the Authorization modal from the gateway in your dashboard to add, update, or remove tokens.

3

Authenticate each request

Send the token with every request so your application can serve protected IPFS content through the gateway.

Two ways to send the token

Filebase supports both a query string parameter and a request header for dedicated IPFS gateway requests, so you can choose the pattern that fits your application best.

Query parameter

Append the token to the gateway URL when that fits your application flow best.

Example
https://gateway.myfilebase.com/ipfs/QmHash?filebaseGatewayToken=your_token_here

Request header

Pass the token as a header to keep authentication out of the URL itself.

Example
x-filebase-gateway-token: your_token_here

Keep dedicated IPFS gateway delivery private without building a custom gate in front of it.

Create a gateway, generate a token, and start serving protected IPFS content over HTTPS with built-in edge caching.