What is a property?
A property is the core CDN configuration object in Paradarum. It represents one site or origin under your account and bundles everything Paradarum needs to accept traffic on your behalf, cache it, secure it, and forward it to your origin server.
One property = one site/origin
When you create a property you give it a name and an origin. From that point forward the property is the single place where all CDN behavior for that site lives. Each property is scoped to your account, so configuration and statistics never leak between accounts.
Every property has exactly one auto-generated system hostname in the form your-property.prdrm.net. The name you choose becomes the immutable left-hand label of that hostname, so it is globally unique on the .prdrm.net suffix.
:::info Automatic SSL on create
Creating a property provisions its your-property.prdrm.net hostname, activates the property, and enqueues an ACME (Let's Encrypt) certificate request automatically. You do not request certificates by hand for the system hostname. See SSL certificates.
:::
What a property contains
A property is a container for several related pieces of configuration:
| Component | What it holds |
|---|---|
| Origins | One or more origin servers Paradarum fetches from, plus an optional Host header override. See origin and host header. |
| Hostnames | The auto-created your-property.prdrm.net plus any custom domains you add. See custom hostnames. |
| Rules | Cache and header rules that match requests and change behavior. See how rules work. |
| WAF | Web Application Firewall settings for the property. |
| General settings | A property-wide JSON blob covering HSTS, clickjacking and MIME protections, Always Online, query-string handling, browser caching TTL, image optimization, and Origin Shield. See caching and query strings. |
:::note General settings are managed separately
General settings live in their own record, read and written through dedicated GET/PUT .../general-settings endpoints — not through the property record itself. The API stores them as a single snake_case JSON blob and does not merge partial updates, so the panel always sends the full object.
:::
Lifecycle and status
Every property has a PropertyStatus. New properties are created in Pending and the create flow promotes them to Active.
| Status | Value | Meaning |
|---|---|---|
Active | 0 | Serving traffic; configuration is editable. |
Disabled | 1 | Turned off; all configuration changes are rejected. |
Pending | 2 | Provisioning; the create flow moves it to Active. |
Suspended | 3 | Suspended; all configuration changes are rejected. |
The status field is controlled by the server — the panel cannot set it directly.
:::warning Disabled and suspended properties reject all changes
Any mutation against a Disabled or Suspended property — updating general settings, deleting the property, or purging cache — returns HTTP 403. A common disabled reason is TrafficOverage (quota exceeded with a negative balance); the account must be recharged before the property can be re-enabled.
:::
Managed (live-stream-backed) properties
Some properties are managed — they are the backing object of a live stream rather than a property you created directly. Managed properties are read-only in the panel. The Origin, Host Header, Image Optimization, and Quick Setup controls are hidden, and a "Managed by Live" banner links to the live-stream configuration instead. For live workflows, see live overview.