Private Aggregators

Every Tusky user is automatically assigned a private aggregator — a dedicated HTTP endpoint that serves only content from your environments. Unlike public Walrus aggregators that resolve any blob on the network, your private aggregator is scoped exclusively to your account.

How It Works

When you create a Tusky account, a private aggregator is provisioned automatically. No setup required.

Account created

Upon account creation, Tusky provisions an aggregator with a unique subdomain on the mytusky.xyz domain.

Subdomain assigned

Your default aggregator URL follows the pattern https://{subdomain}.mytusky.xyz. You can customize the subdomain at any time.

Content scoped

The aggregator is linked to your account. It only resolves files that you have uploaded — requests for content belonging to other users return a 404.

Default URL

Your aggregator URL is:

https://{subdomain}.mytusky.xyz

For example, if your subdomain is acme-corp, your aggregator URL is https://acme-corp.mytusky.xyz. All standard URL schemes work under this domain.

Security Benefits

Content isolation

Your aggregator will not resolve blobs that belong to other users, even if you know their blob IDs. This prevents unauthorized hotlinking and ensures your aggregator only serves your own content.

Abuse prevention

Since your aggregator only serves your own content, it cannot be used as an open proxy. This eliminates the risk of your aggregator being exploited to serve malicious content uploaded by third parties.

Predictable traffic

All traffic to your aggregator is driven by your own applications and users. This makes it easier to monitor, forecast, and scale your content delivery.

Audit trail

Every request to your aggregator is logged and available through Aggregator Analytics, providing a complete picture of who is accessing your content.

Configuration

You can configure your aggregator through the Tusky dashboard or the SDK.

Change Your Subdomain

Dashboard
SDK
API

Navigate to Settings → Aggregator in the Tusky dashboard and enter your desired subdomain.

const updated = await tusky.aggregator.update({
  subdomain: "my-brand",
});
console.log("New URL:", updated.url);
// https://my-brand.mytusky.xyz

curl -X PATCH https://api.tusky.io/v1/aggregator \
  -H "Authorization: Bearer tsk_live_abc123" \
  -H "Content-Type: application/json" \
  -d '{"subdomain": "my-brand"}'

Subdomain changes take effect immediately. The previous subdomain becomes available for other users after a short cooldown period.

Custom Domain

For a fully branded experience, you can attach your own domain to the aggregator. See Custom Domains for the full setup guide.

What’s Next

Custom Domains

Serve content from your own domain with automatic SSL.

Aggregator Analytics

Monitor requests, bandwidth, and geographic distribution.

SDK: Aggregators

Configure your aggregator programmatically.

Get Started

Getting Started

Core Concepts

Aggregators

Billing

Tools

Architecture

Private Aggregators

How It Works

Default URL

Security Benefits

Configuration

Change Your Subdomain

Custom Domain

What’s Next

Custom Domains

Aggregator Analytics

SDK: Aggregators

Get Started

Getting Started

Core Concepts

Aggregators

Billing

Tools

Architecture

​How It Works

​Default URL

​Security Benefits

​Configuration

​Change Your Subdomain

​Custom Domain

​What’s Next

Custom Domains

Aggregator Analytics

SDK: Aggregators

How It Works

Default URL

Security Benefits

Configuration

Change Your Subdomain

Custom Domain

What’s Next