App Platform: deploy web apps from Git and Docker images

First, set the source of your app. After ordering, tell us your GitHub or GitLab repository or container image address on the support page, and our team connects it for you. For repositories, the build method is detected automatically from the language; if there is a Dockerfile, the build follows it, and an image you already built runs straight from its address.

Next, tell us your run settings. Send the port your app listens on, environment variables such as the database connection address, and the start command, and our team adds them. Passwords and API keys go in as encrypted environment variables so they never stay in your code repository. Once set up, the build starts, and when the app is up we send you its default address.

Finally, connect your own domain. Tell us the domain you will use and we give you the record value to add; add that one record in your domain's DNS settings and an HTTPS certificate is issued and renewed automatically. From then on, every push to your repository's default branch builds a new version, and traffic switches over only once it is ready, so customers use the service without interruption even during deploys.

The smallest size, App L, is $25.00 per month with 2 vCPU and 4GB memory. App XL with 4 vCPU and 8GB memory is $45.00, and App 2XL with 8 vCPU and 16GB memory is $85.00. Builds, HTTPS certificates, custom domains and log access are all included in the prices in the table.

Choose the size based on the memory your app uses. App L is enough for Telegram bots and small APIs, and web apps using a framework fit App XL or App 2XL with 4GB. For services with many users or memory-heavy apps like image processing, choose App 3XL. You can change the size later based on usage by requesting it on the support page once your first payment is confirmed.

Payment happens on each billing date. The first month is charged when you order, and the same amount is taken automatically on each billing date to renew. If you run several apps, each has its own billing date, so cancelling only an unused app on the support page stops just that app's fee.

On App Platform, the disk is prepared fresh every time you deploy a new version. So data that must last, such as member data, order history and files uploaded by customers, belongs in managed databases and object storage. With things split this way, your data stays intact no matter how many times you redeploy.

Keep secrets in environment variables from the start. With separate database addresses for development and production, you can deploy the same code to a test app and a production app while each uses its own data. When you change a key, there is no need to edit code: send the new value on the support page and we change only the environment variable and redeploy.

Setting up a health check address makes deploys safer. When a new version starts, the platform checks that address and moves customer traffic to the new version only after a healthy response. A misconfigured version stops before traffic moves, so customers keep using the previous version.

When something goes wrong, start with the runtime logs. Request them on the support page once your first payment is confirmed and we send you the records your app wrote to standard output in time order, so you can quickly find which request caused the error. If memory fills up often and the app restarts, move up one size. Build logs are kept too, so when a deploy fails we also tell you which package install it stopped at.