Dedicated Gateways

Bio-AI DIDs sequencer provides dedicated IPFS gateways for reliable, fast access to your content. Custom domains, SSL, and private gateways are available to enhance your user experience.

What are IPFS Gateways?

IPFS gateways are HTTP servers that bridge the gap between traditional web browsers and the IPFS network. They allow anyone to access IPFS content without running an IPFS node or using specialized software.

Why Use Dedicated Gateways? While public gateways exist, they often have rate limits, slower performance, and no guarantees of availability. Dedicated gateways provide reliable, fast access to your content with customization options.

Bio-AI DIDs sequencer Dedicated Gateways

Gateway Features

High Performance: Optimized for speed with global edge caching
High Availability: 99.9% uptime SLA with redundant infrastructure
Custom Domains: Use your own domain for a branded experience
SSL Support: Automatic SSL certificate management
Access Controls: Public or private access with authentication
Usage Analytics: Track requests, bandwidth, and geographic distribution

Gateway URLs

Gateway Type	URL Format	Example
Default	`https://gateway.ekayana.com/ipfs/{CID}`	`https://gateway.ekayana.com/ipfs/QmExampleCID123`
Subdomain	`https://{CID}.ipfs.gateway.ekayana.com`	`https://QmExampleCID123.ipfs.gateway.ekayana.com`
Custom Domain	`https://{your-domain}/ipfs/{CID}`	`https://assets.example.com/ipfs/QmExampleCID123`

Setting Up a Custom Domain

Add your domain in the Ekayana dashboard
Configure DNS records as instructed (typically a CNAME record)
Verify ownership through the provided methods
Wait for SSL provisioning (usually 5-10 minutes)

Example DNS configuration:

Type: CNAME
Host: gateway.example.com
Value: custom-gw.ekayana.com
TTL: 3600

Private Gateways

For content that requires access control, you can set up private gateways:

Authentication Methods

Session token: an ML-DSA-87 bearer token identifying the account (see Authentication)
UCAN capability: a scoped, revocable grant over one CID, presented in the X-UCAN-Token header (see Sharing & Delegation)
IP allowlisting: restrict access to specific ranges

The platform issues no API keys. Both credentials above expire and the capability form is revocable, so a leaked credential has a bounded blast radius. See Sharing & Delegation for the reasoning.

Example: Accessing Private Content

javascript

// Owner access - the session token alone is sufficient.
const response = await fetch(
  'https://api.ekayana.com/api/download/QmExampleCID123',
  { headers: { Authorization: `Bearer ${token}` } }
);

const data = await response.blob();

To read content someone shared with you, add the capability alongside your session token:

javascript

const response = await fetch(
  'https://api.ekayana.com/api/download/QmExampleCID123',
  {
    headers: {
      Authorization: `Bearer ${token}`,
      'X-UCAN-Token': ucanToken,
    },
  }
);

Gateway Performance Optimization

Use subdomain gateways for the best browser compatibility
Enable edge caching for frequently accessed content
Consider content chunking for large files to improve partial loading
Compress assets before uploading when possible

Post-Quantum Security Content Pinning