Wavesteam Managed Operations and Server Plans
Compare four managed-operation tiers with customer-owned cloud, including annual fees, MAU thresholds, metered resources, and measurable SLA boundaries.
Which plan should a newly launched service choose?
For an ordinary service with no more than 30,000 monthly active users, no dedicated operations team, and no multi-node availability requirement, start with the Standard plan and Wavesteam-managed infrastructure. Use the client's own cloud account when the client has an internal IT team or a firm data-residency requirement. If downtime directly stops transactions or physical operations, size a higher plan from real peak load, recovery objectives, and dependency risks.
Every plan includes immediate intervention for a major production outage. The differences are supported scale, infrastructure capability, and availability design—not whether Wavesteam responds.
Service plans
| Plan | Intended use | Included MAU | Managed infrastructure | Annual maintenance | Availability objective |
|---|---|---|---|---|---|
| Standard | New or stable small services | Up to 30,000 | CNY 6,600/year | 10% of initial delivery fee | 99.00% |
| Professional | A growing operating system | Up to 80,000 | CNY 16,000/year | 15% of initial delivery fee | 99.50% |
| Flagship | Larger services where interruption materially affects operations | Up to 150,000 | CNY 36,000/year | 20% of initial delivery fee | 99.90% |
| Custom | Very large scale, special compliance, or dedicated architecture | Assessed separately | Assessed separately | Assessed separately | Up to 99.99% by design |
MAU sets the fixed service boundary; it does not mean every application consumes the same resources. SMS, email, CDN, object storage, AI, video, maps, and other metered services are integrated and operated within scope, while actual supplier usage is billed separately.
Included in every plan
- automated monitoring around the clock;
- immediate response to a major production incident;
- monitoring for applications, servers, databases, and caches;
- routine log collection and troubleshooting;
- automated deployments and release support;
- daily data backups;
- domain and TLS certificate expiry reminders;
- routine security, capacity, and subscription checks.
A major incident includes broad production unavailability, widespread failure of a core function, a fully blocked payment or order flow, or an evident data-loss or security risk. Routine questions and planned releases follow the agreed service window.
Managed capability, not server resale
The managed infrastructure fee buys an operating capability for the agreed workload. Wavesteam selects and adjusts compute, database, cache, monitoring, deployment, and backup resources without tying the service permanently to one advertised CPU or memory specification. A material architecture change is discussed before it affects scope or fees.
MAU and upgrade rules
MAU means distinct users who sign in or complete a valid business action in a calendar month. Repeated activity by the same user counts once. A single month up to 10% above the allowance does not trigger an upgrade. An upgrade review begins when usage exceeds that tolerance for two consecutive months or for three months in a year. We confirm the cause, forecast, and next plan before changing the commercial arrangement.
Metered resources
Storage and CDN are billed by capacity, requests, and transfer; messaging by volume and destination; AI by tokens, images, or audio; media by storage, processing, and delivery; maps and other APIs by the provider's bill. Temporary campaign capacity is estimated separately and removed after the agreed window.
Price stability and client-owned cloud
The annual maintenance percentage is based on the first production release. Small later work does not automatically compound the base. A major expansion in users, systems, risk, service hours, or architecture is reviewed for the next term.
Clients may use their own cloud account and keep billing and ownership directly. Wavesteam can also plan a later migration from managed infrastructure; effort and maintenance window depend on the current architecture, data volume, and destination environment.
SLA percentages are service objectives, not a promise that every external dependency will remain available. The agreement should define measurement, exclusions, maintenance windows, incident communication, and any remedy.
This article describes general service plans. The signed contract, quotation, and SLA schedule govern the specific scope, resources, fees, service levels, and responsibilities.