Before opening your app

Before going public

1. Use a clearly named project and separate test data from production.
2. Configure and protect all required secrets; never expose database credentials in frontend code or logs.
3. Confirm build/start commands and the public listening port.
4. Keep internal products in the same org and apply their private endpoints in server-side env. Test database/cache connections.
5. Verify custom DNS and HTTPS; confirm a usable backup and recovery procedure.

• Public and private networking
• Security and responsibilities
• Backup and recovery
• Domains

After the first release

1. Review build logs for skipped or failing steps.
2. Inspect runtime logs for startup errors or repeated failures.
3. Test login, main forms, API actions and data connections through the public URL.
4. Record the stable release and check schema compatibility before relying on rollback.

As traffic grows

Monitor CPU/RAM, query/command usage, bandwidth and Billing. Optimize frequent queries and cache reads before only increasing capacity. Upgrade when legitimate load consistently approaches limits. Investigate costs by resource when usage changes unexpectedly.