Who does what?
| Area | DLEZ provides | You manage |
|---|---|---|
| Flash Deploy | Build/deploy workflow, configuration, logs and history. | Working code, ports/env, testing and app authorization. |
| MySQL / Redis | Service provisioning, Connection, limits and metrics. | Data design, server-side clients, credentials, backup checks and compatibility. |
| VPS | Instance provisioning, lifecycle and console access. | OS/software, updates, firewall, HTTPS, monitoring and backups. |
| Costs | Plan information and Billing. | Usage, balance, billing conditions and unused test resources. |
Protect configuration and data
- Keep passwords in server-side env, not committed .env files or frontend bundles. Hiding secrets in Console does not stop your code from logging them.
- Use private endpoints for server-side calls between products in the same org. External clients use public endpoints; different orgs do not share a private network. Follow service TLS requirements.
- Use minimum permissions where supported. Rotate exposed credentials through the service's supported procedure, then update the app.
- Test API authorization, validation and abuse controls. Separate test data from production.
What to confirm before production
Confirm SLA scope, backup retention, restore procedures, resource limits and support for your selected service and plan. These guides do not replace service terms.
Do not assume autoscaling, high availability, automated backups or zero-downtime deployments unless confirmed for your plan. Choose an operating approach consistent with the downtime and data loss your app can tolerate.