1. Understand the current scope
The public site and guides are open. New registration and customer allocation are closed on the live site. Local development preview can store project and service definitions, but it does not execute code or create real databases or domains. The console steps below apply to that local preview.
2. Define the project boundary
A project brings services for one application together. Use a readable name, unique address and a clear development / production environment choice. A mobile API and its database may belong to one project; keep separate customers apart.
3. Separate application and database
An app service receives HTTP while a database service stores SQL data. Node.js, Laravel, Python or Docker refers to backend code. MySQL / PostgreSQL refers to the data model. Separate responsibilities rather than forcing every need into one process.
4. Prepare environment values
Keys and values are entered separately in the service screen. Values are encrypted; lists show keys and a masked representation. Document the variables your app needs. Never use example values as real passwords or commit secrets to Git.
APP_ENV=development
# Keep secret values such as DATABASE_URL outside the repository.5. Interpret release states correctly
The local provider simulates queues and service lifecycle. Pending or ready does not prove a real server exists; logs identify simulation explicitly. Application URLs, IP addresses and SQL passwords are not offered before live allocation opens.
6. Plan domains and files
A domain record does not establish DNS ownership or create a TLS certificate. Local console records may remain pending. The object storage provider is also unconnected. Plan persistent files, authorization and deletion rules in your application design.
7. Validate before a real release
Test the start command, port, health check and access rules. Clarify database backups and restoration with your provider. Keep passwords and session details out of logs. A functioning screen does not prove the entire operational infrastructure is ready.
8. Choose the next guide
Use the matching product page for runtime preparation. Continue to the private database guide for the boundary between clients and SQL. Status and pricing pages explain the current live-service scope.