Deployment and billing

This page explains how to deploy a LightApp application, manage services day to day, and how LightApp billing works.

#Before you deploy

• LightApp is prepaid, and charges come out of your account balance. Before you deploy, check your balance under 财务管理 → 账户余额 (Billing → Balance) (/billing/balance).
• Choose the app you want. Some apps in the catalogue may not have a plan on sale yet, and those cannot be deployed.

#Deploying from a template

1. Open the Service Marketplace catalogue (/lightapp/create). You can also reach it from the purchase link on the LightApp card on the console home page.
2. The tabs at the top filter apps by category. All Applications shows everything. Apps tagged Stack run as several containers.
3. Click an app card or Deploy to open the deployment panel:
   • Service Name: pre-filled as "app name-timestamp". You can change it.
   • Plan: the resource plan. Each option shows the plan name, price and billing mode. If there is only one plan, it is selected for you. If you see "No plan available", the app cannot be deployed yet.
   • Environment Configuration: settings defined by the template, such as an admin password or port. Fill them in as prompted.
   • Docker Compose (Read-only): for Stack apps, the compose file is shown here for reference only.
4. Click Deploy Application. You are taken back to My Services, where the status updates as the deployment progresses.

Deploy New Service in My Services opens the unified order wizard (/provision/lightapp). Its steps are 选地区 (Region) → 选套餐 (Plan) → 配置 (Configure, where you enter an app name) → 确认 (Confirm), followed by checkout through the cart. The wizard only lists regions and plans that currently have capacity.

#Managing services

The top of My Services (/lightapp/services) shows your total number of services and how many are Running, Stopped or in Error. The list shows each service's name, type, status, resources and creation time.

Each service's Actions menu offers:

• Start / Stop / Restart: start, stop or restart the service. For Stack apps, the action applies to every container in the stack.
• View Details: open the service detail page.

The service detail page (/lightapp/services/<ID>) has these sections:

• Monitoring: CPU, memory, network and disk I/O usage
• Logs: container logs
• Containers: the status of each container in a Stack app, with per-container logs
• Configuration / Settings: the template, image, resource limits, ports and environment variables used by the service

#How billing works

LightApp charges your account balance every hour. Each charge appears in the transaction history under 财务管理 → 账户余额 (Billing → Balance). The rules depend on the plan's billing mode.

#Monthly plans (monthly / fixed)

• At deployment: the first month's fee is deducted from your balance right away.
• After the first month: you are charged hourly. The hourly rate is the plan's monthly price ÷ 720, based on a 30-day month.
• Amounts smaller than one cent carry over to the next charge, so rounding never overcharges or undercharges you.

#Pay-as-you-go plans (payg)

If a plan's billing mode is payg, you are charged hourly for what you actually use:

Pay-as-you-go plans are not charged up front. To deploy one, your balance must be at least a minimum amount: 1, or the amount shown on the plan if that is higher. Unit prices are published in the console and on the product page.

#Stopped services are still billed

A Stopped service still holds its plan's resources. Monthly plans keep being charged as normal, and pay-as-you-go plans still incur charges such as disk. If you no longer need a service, contact support to cancel it and stop billing.

#Low balance and suspension

• If your balance cannot cover a billing period, the service is stopped automatically and its status changes to suspended.
• If your plan includes a traffic allowance, the service is also suspended when you go over it.
• You cannot restart a suspended service yourself. If you try, you will see "Service is suspended. Please contact support." Top up your balance first, then contact support to restore the service.