Skip to main content

Create your first property

Creating a property is a guided wizard with five steps: Name → Origin → Site type → Domain (optional) → DNS. The first three create and activate the property; the last two connect your own domain and can be skipped — the site serves on its *.prdrm.net system hostname either way. This page walks through each step, the validation rules, and exactly what Paradarum does on submit.

Step 1 — Property Name​

In your dashboard, click Create New Property to start the wizard.

The name becomes the immutable left-hand label of your system hostname, your-property.prdrm.net, so choose it carefully — it is globally unique and cannot be changed later.

RuleDetail
Allowed charactersLowercase letters a-z, digits 0-9, and hyphens -.
Minimum length3 characters.
Validation pattern^[a-z0-9]([a-z0-9-]*[a-z0-9])?$
ResultBecomes the immutable hostname your-property.prdrm.net.

As you type, the field is sanitized live: anything outside [a-z0-9-] is stripped and the text is forced to lowercase. The wizard shows the resulting hostname (your-property.prdrm.net) so you can confirm it before continuing.

tip

A property may not begin or end with a hyphen — that is what the [a-z0-9]...[a-z0-9] anchors in the pattern enforce. Pick a short, memorable name; it is what your custom domains will ultimately point at.

Step 2 — Origin​

The origin is the hostname of your origin server — the place Paradarum fetches content from when it isn't cached (for example origin.example.com). It is required and validated against a hostname regex.

New properties default the upstream Host header to Auto: the CDN sends your custom hostname to the origin, so a shared hosting picks the right virtual host even when visitors arrive via your-property.prdrm.net. Details in Origin server and Host header.

Step 3 — Site type​

Choose what this property serves. The options are the same catalog as Quick Setup / CMS presets — WordPress, PrestaShop, Drupal, Magento 2, Next.js and more — plus Custom for anything else. The wizard seeds the cache and header rules of the platform you pick, exactly as applying that preset would.

The site type is your choice

Paradarum never auto-detects or guesses your CMS — the wizard always asks. If you are unsure, pick Custom: you start with only the defaults and can apply any preset later from the property's Quick Setup card.

Whatever you pick, the property is also seeded with the Default — cache static assets rule: common static extensions cached for 7 days, ordered last so preset rules and rules you create yourself always take precedence.

Completing this step creates the property. It is live at https://your-property.prdrm.net from here on — the remaining steps only attach your own domain.

Step 4 — Domain (optional)​

Enter the domain you want to serve (for example www.example.com), or click Skip.

  • Skip finishes the wizard. Nothing is lost: the site keeps serving on the system hostname, and you can add a domain any time from the Hostnames tab (Add a custom hostname).
  • Entering a domain adds it to the property as a hostname (in PendingValidation until DNS points at the CDN) and moves you to the guided DNS step.

Step 5 — Guided DNS​

The wizard shows the exact CNAME record to create at your DNS provider, with a copy button on the target:

Type:      CNAME
Name:      www.example.com          (your domain)
Points to: your-property.prdrm.net  (your system hostname)  [copy]

Create the record — Connect your domain has click-by-click steps for Cloudflare, OVH, IONOS, GoDaddy and cPanel — and keep the wizard open. The panel polls your DNS automatically every few seconds: when the record becomes visible, the hostname flips to Active and the Let's Encrypt certificate is requested, with no manual retry.

If DNS propagation takes longer than you want to wait, finish the wizard; the hostname stays pending and you can complete verification later via Hostnames → Retry (Verify DNS and retry SSL).

What happens on submit​

Behind the scenes, completing the create steps runs several actions automatically:

The panel sends a POST to the API with the property name and a single origin:

{
  "name": "my-site",
  "origins": [{ "host": "origin.example.com" }]
}

A successful response is HTTP 201:

{ "message": "Property created successfully.", "succeeded": true, "data": { "id": 42, "name": "my-site", "status": 0 } }

The property is created in Pending and promoted to Active by the same flow. The system hostname is provisioned and a Let's Encrypt certificate is requested for it — no manual SSL step is needed.

Common error: name already taken​

Because names are globally unique on the .prdrm.net suffix, creation fails if your-property.prdrm.net is already owned by another property:

400 Bad Request
"Hostname already exists."
warning

If you see "Hostname already exists.", choose a different property name. The suffix prdrm.net is shared across all accounts, so the left-hand label must be unique everywhere — not just within your account.

Next steps​

Get serving quickly