Create your first property
Creating a property takes two fields and a single click. This page walks through the Add form, the validation rules, and exactly what Paradarum does once you submit.
Open the Add form
In your dashboard, click Create New Property. The form has only two fields.
Property Name
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.
| Rule | Detail |
|---|---|
| Allowed characters | Lowercase letters a-z, digits 0-9, and hyphens -. |
| Minimum length | 3 characters. |
| Validation pattern | ^[a-z0-9]([a-z0-9-]*[a-z0-9])?$ |
| Result | Becomes 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 form shows the resulting CNAME (your-property.prdrm.net) so you can confirm it before submitting.
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.
Origin Name
The Origin Name 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.
Submit
Click Create Property. The panel sends a POST to the API with the property name and a single origin. On success it returns you to the property list and shows "Property created successfully".
{
"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 } }
What happens on submit
Behind the scenes, the create flow runs several steps automatically:
The property is created in Pending and promoted to Active (status: 0) 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."
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
:::tip Get serving quickly
- Point your domain with a CNAME — connect your real domain to the new property.
- Configure allowed origins — lock down which origins the property accepts.
- Apply a CMS preset — bulk-create sensible cache and header rules for WordPress, PrestaShop, and more. :::