Uploading your own certificate - Basaltic

Bringing your own certificate

Store material you already hold. There is no challenge and no wait — the certificate is active immediately.

Console
API

On Create Certificate, switch the source to Provide your own certificate, then paste the Certificate (PEM-encoded), the Private Key, and optionally the Certificate Chain.

Set source: "uploaded". The response is 201 with the certificate already active.

{
  "name": "prod-frontend",
  "domains": ["example.com", "www.example.com"],
  "key_algorithm": "ecdsa-p256"
}

{
  "name": "prod-frontend",
  "domains": ["example.com"],
  "source": "uploaded",
  "certificate_pem": "-----BEGIN CERTIFICATE-----\n...",
  "chain_pem": "-----BEGIN CERTIFICATE-----\n...",
  "private_key_pem": "-----BEGIN PRIVATE KEY-----\n..."
}

certificate_pem and private_key_pem are both required when uploading; chain_pem is optional.

Uploaded certificates are never renewed. Renewal only covers what the platform issued, because only then does it hold the authority relationship needed to reissue. Track the expiry of an uploaded certificate yourself and upload a replacement before expires_at.