Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how

Add-ons

Managed add-ons

Use managed add-ons when the platform should create, rotate, and bind infrastructure details instead of asking customers for host, port, or password values.

Back to Platform Help

Managed Redis

When Redis is enabled, the service is created automatically and attached to the platform as environment variables and secrets.

  • Users are not asked for Redis host, port, or password values.
  • Enabling or disabling the service later is applied through a deployment update.
  • The panel shows status messages such as Managed Redis is running.

Managed Database

For platforms such as WordPress, database usernames and passwords are generated by the system.

  • Secret values are not returned in GET responses.
  • Install and reset operations only target the related platform resource.
  • If database information is needed, it can be regenerated or rotated through a panel action.

Object Storage

S3-compatible Object Storage provides bucket and access key management when Ceph RGW is ready.

  • Customer buckets are not created until the Ceph RGW health gate is open.
  • The secret access key is shown only once during create or rotate.
  • After binding, S3 environment variables are added when the app is redeployed.
  • AWS CLI and S3-compatible SDKs can use the endpoint https://s3.cdn.com.tr with the generated access key.

Connecting your app to add-ons

When you enable an add-on, the platform automatically injects its connection details into your app as environment variables (and passwords as Kubernetes Secrets). Read them from your app environment in code — there is no need to copy host, port or password values by hand.

  • Redeploy the app after enabling an add-on so the variables are mounted into the containers.
  • Passwords are never shown in the panel or in API responses; only the variable names are visible. Read the value from the environment, or use the ready-made connection URL (DATABASE_URL / REDIS_URL).
  • Variable prefixes (REDIS, DB, DATABASE, NATS) can be customized per add-on via env_prefix.
  • Use an add-on from another app (e.g. a backup job): set a variable in that app to ${source-app-slug.VAR}, for example DATABASE_URL=${web.DATABASE_URL} or DB_PASSWORD=${web.DB_PASSWORD}. It is resolved securely within your account — the password is never exposed.
Redis:       REDIS_HOST, REDIS_PORT, REDIS_DB, REDIS_URL, REDIS_PASSWORD
MySQL:       DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME, DB_PASSWORD, DB_URL, DATABASE_URL
PostgreSQL:  DATABASE_HOST, DATABASE_PORT, DATABASE_NAME, DATABASE_USER, DATABASE_PASSWORD, DATABASE_URL
NATS:        NATS_HOST, NATS_PORT, NATS_URL

External access

Managed add-ons are reachable only from inside the platform, by design.

  • Redis, MySQL, PostgreSQL and NATS are created as internal cluster services with private hostnames.
  • They can be reached only from your own app containers, through the injected environment variables.
  • There is no public endpoint, so you cannot connect from outside (for example a database client on your computer).