CDN Domains

Understanding Beefree's CDN Infrastructure

A CDN (Content Delivery Network) is a system of distributed servers that deliver web content, ensuring high availability and performance by distributing the service spatially relative to end-users. CDNs reduce load times, minimize latency, and enhance security for digital assets.

Beefree's Segmented CDN Infrastructure

If you rely on Beefree SDK storage, Beefree uses a segmented CDN infrastructure to serve your assets. We allocate distinct second-level domains per subscription tier and media type, and also assign you a dedicated third-level domain based on subscription ID.

This unique setup isolates your content from other SDK customers, mitigating risks from potential malicious or spammy uploads. By preventing one customer's actions from impacting others, Beefree ensures robust security and maintains the integrity and reputation of all digital assets.

How Beefree CDN Infrastructure Works

When you create or manage an SDK application, your subscription plan determines which CDN domains your files use.

Free Plans

For free plans, all assets are served from the domain beefreesdkhosting.net. Each subscription is automatically assigned a third-level domain that uniquely identifies it.

Free plans only support image, video, and PDF MIME types. If you want to learn more about file type limitations, please visit the dedicated page.

Free Plan CDN domain example

https://id32514.beefreesdkhosting.net/path/to/file.png

Paid Plans

For paid plans, we use two domains to serve different types of assets:

• The Media Files CDN Domain sdkmedia.net handles image, video, and audio MIME types

• The Other Files CDN domain sdkhosting.net is used for text (including HTML), office documents, XML, ZIP files, EPUB, PDF, PostScript, and fonts.

New apps created by paid users are by default restricted to uploading image, video, and PDF MIME types. You can enable additional MIME types via the SDK Console—learn how here.

Paid plans' subscriptions are also automatically assigned a third-level domain.

Paid plan Media Files domain example:

https://id76302.sdkmedia.net/path/to/image.png

Paid plan Other Files domain example:

https://id76302.sdkhosting.net/path/to/archive.zip

Customize your CDN Domain

If you are a Paid User, you may request a one-time customization of your third-level domain, which allows aligning the CDN URL more closely with your brand identity. This can be requested in the SDK console, as seen in the screenshot below.

For Enterprise plans, you may also request to connect your own domain. Please contact your CSM for dedicated assistance.

---

CDN Migration

Previously, all media for both free and paid plans were served via a single shared domain: d15k2d11r6t6rl.cloudfront.net. To provide the enhanced security and segmentation described above, Beefree migrated to the current configuration in early 2026.

This transition followed the timeline below:

• 15 January 2026 for SDK Free Plans

• Progressive rollout from 19 February 2026 for SDK Paid Plans. You'll be notified about when your application is scheduled to be migrated.

Impact on Media Assets and Automation

All files (images, videos, etc.) that your end users previously uploaded will continue to be visible and work as intended under the new, segmented CDN configuration.

More in detail, you can now expect different behavior depending on when assets enter a message.

• Emails sent before the migration: Existing emails continue to serve images and media assets from the previous CDN domain.

• Existing File Manager assets: When you insert an existing asset into a new message, the system rewrites the URL to use the current CDN domain.

• New uploads: Newly uploaded files always use your segmented CDN domain.

If your team performs post-processing on image URLs (for example, rewriting or hashing), you may need to adjust your setup to account for the new CDN domain pattern.

Opting Out

While we strongly recommend the segmented infrastructure for security and reputation management, we understand that certain technical workflows may require more time to adapt. If you need to remain on the legacy CDN domain configuration, you have the option to opt out of this migration. Please reach out to our support team to discuss your requirements.