CDN.com.tr Help

Create the first CDN account

Create the account shell from CDN Accounts, buy and assign the package in the panel when required, and prepare the account UUID for DNS, storage, platform, or cdnctl workflows.

Back to Help Center Back to section

Getting started

Create the first CDN account

Create the account shell from CDN Accounts, buy and assign the package in the panel when required, and prepare the account UUID for DNS, storage, platform, or cdnctl workflows.

How this page differs from Getting started

The Getting Started section helps choose the scenario. This page only prepares the shared foundation that all scenarios need: account, package, and account UUID.

I need to choose

Compare source and delivery method

Choose from Pull, Push, and Hosting sources together with Default Endpoint, CNAME, and Full DNS examples.

3 source types 3 delivery methods
Open choice guide
Existing site

Use CDN without moving hosting

Put the existing website behind CDN.com.tr with origin and Host header settings.

Pull CDN CNAME / Full DNS / Default
Open existing site flow
Static files

Publish quickly from the default endpoint

Upload files to CDN.com.tr storage and serve from `xyz.cdn.com.tr`.

Push CDN Default Endpoint
Open Simple Transfer flow
Platform

Run the application on CDN.com.tr

Continue to platform entitlement, deploy/status/logs, and public domain verification.

CDN Hosting/Platforms CNAME / Default / Full DNS
Open platform flow

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Add Your Website
  4. Content Source
  5. Select / buy package
  6. Delivery Method
  7. CDN Accounts package change / account selection

Prerequisites

  • The user is signed in.
  • Package purchase, payment, renewal, and repayment stay in the panel, not API, cdnctl, or AI-agent flows.
  • Terminal or AI-agent work starts only after purchased packages can be listed and the package ID is known.
  • This page prepares the account foundation; source type and delivery method can be changed later from the related screens.

Decision model

What does the account shell provide?

The wizard prepares the customer workspace that later domain, storage, platform, and apply operations attach to.

  • The account UUID scopes later API and cdnctl calls.
  • The selected account appears in the sidebar and account switcher.
  • Capacity and entitlement-gated actions do not start until a package is assigned.

Package boundary

The customer completes payment in the panel; automation consumes already purchased packages.

  • Panel: package choice, cart, payment, invoice data.
  • cdnctl/API: list purchased packages, create accounts, attach packages.
  • AI agents must not request payment-card details or checkout operations.

Choose the next guide

After the first account is ready, continue based on workload type.

  • Pull CDN: put CDN.com.tr in front of an existing origin.
  • Push CDN/Simple Transfer: upload files to CDN.com.tr storage.
  • Hosting/Platforms: run the application on CDN.com.tr.
  • These choices can be changed later from the related product screen; traffic-affecting changes need Apply Changes.

Step-by-step guide

1

Open CDN Accounts

After signing in, `/en/management/cdn` shows existing accounts and the Add Your Website button.

  • Check whether an existing account can be reused.
  • If a new account is needed, start the wizard with Add Your Website.

Expected result: The user can enter the new-account flow from the panel.

cdnctl equivalent 
cdnctl update --check
cdnctl login --email "<email>" --password "<password>"
cdnctl accounts list
2

Choose the content source

The wizard first asks which source type the account should use; that choice determines the later product path.

  • Compare Pull CDN, Push CDN, and CDN Hosting.
  • Confirm that the account-shell notice does not imply a platform deploy yet.
  • Use this guide to choose the model, then continue to the matching case page.

Expected result: The package step follows content source selection.

cdnctl equivalent 
export CDN_SOURCE=pull
# Alternatives: push or hosting
3

Prepare the purchased package

If no package is available, package purchase and payment are completed by the customer in the panel, not delegated to terminal or AI agents.

  • Choose the suitable package from Packages.
  • The user completes payment and invoice data in My Cart.
  • After payment, the available package should appear in the wizard or account screen.

Expected result: A purchased package ID can be listed by automation.

cdnctl equivalent 
# Package purchase is completed in the panel.
cdnctl packages list --owned --format table
export PAID_PACKAGE_ID=<listed_package_id>
4

Create the account with a delivery method

The same source type can be delivered through Default Endpoint, Full DNS Transfer, or Custom Subdomain.

  • Choose Default Endpoint when no custom DNS is required.
  • Choose Full DNS Transfer when the root domain will move to CDN.com.tr nameservers.
  • Choose Custom Subdomain when only a subdomain will CNAME to CDN.com.tr.

Expected result: The account returns to the account list with the selected source and delivery method.

cdnctl equivalent 
cdnctl cdn accounts create --source "$CDN_SOURCE" --delivery default-endpoint --package "$PAID_PACKAGE_ID" --alias first-account-demo
export ACCOUNT_UUID=<account_uuid>
5

Verify account and package attachment

After the account shell exists, it must appear in the account list, be selectable, and expose package change or assignment surfaces.

  • Return to CDN Accounts.
  • Confirm the account appears in the list.
  • Use Change package to attach a purchased package when needed.

Expected result: Later DNS, Pull, Push, Platform, or Apply Changes work is scoped to the same account UUID.

cdnctl equivalent 
cdnctl accounts describe --account "$ACCOUNT_UUID"
cdnctl accounts packages attach --account "$ACCOUNT_UUID" --package "$PAID_PACKAGE_ID"

Verification

  • The account appears in CDN Accounts.
  • The wizard source and delivery choices are understandable.
  • Package purchase stays in the panel.
  • `cdnctl packages list --owned --format table` shows purchased packages.
  • The account UUID can be used in later product guides.

Use cases

A customer is new to CDN.com.tr and needs a customer-visible CDN account before attaching domains, DNS, SSL, Push storage, Pull origins, or platform deploys.

Quick workflow

  1. Open CDN Accounts.
  2. Start the Add Your Website wizard.
  3. Choose the content source and delivery method that create the account shell.
  4. If a package is required, complete purchase and payment in the panel.
  5. Assign the purchased package to the account.
  6. Verify the account UUID and selected account before continuing to the product guide.

Checks

  • Creating an account shell must not require SSH, admin routes, or manual DB work.
  • Package purchase is not an automation job.
  • The cdnctl account creation command is not run before a purchased package ID is known.
  • The account UUID is ready before moving to product-specific pages.