Estimating Production Costs
Last updated:2026-01-30 17:09:51
Before application listing, the application provider needs to conduct access technology and cost assessment.
Access Standards
To ensure service SLA and software entitlement requirements, all applications listed on the Marketplace platform must have no dependencies on external resources, meaning that when customers use applications published on the Marketplace, all computing, storage, and so on, only occur within Tencent Cloud.
Marketplace provides users with: dedicated computing and storage units for each customer, enabling private deployment of software on the public cloud.
Software Self-Check
What was the previous delivery type of your software?
SaaS delivery: The Marketplace edition is a customer-specific instance, no longer requiring tenant logic handling; tenant logic must be removed or processed in single-tenant mode.
Private deployment: The main workload is adapting to Tencent Cloud's runtime environment.
Software delivered as source code: It needs to be built into a runnable mirror on Tencent Cloud for listing.
What middleware does your software depend on?
Confirm the middleware that the software currently depends on. Commonly used middleware for software includes database MySQL, Redis, Cloud Object Storage, Message Queue, Cloud Log Service, etc.
Confirm whether there is a cloud native version corresponding to the required middleware.
If there is a corresponding cloud native version, we recommend that software select cloud native middleware, such as Cloud Database CDB. This way can help customers obtain the reliability and agility brought by Tencent Cloud Native services, thereby improving the competitiveness of the software.
If there is no corresponding cloud native version, the developer can use self-built middleware, such as the ETCD database self-built based on CVM.
If the software previously used self-built middleware and plans to be adjusted to use cloud native middleware, there is a development workload for compatibility adjustment.
What container orchestration technology does your software use?
If your software runs based on container orchestration and the used one is not Helm Chart orchestration, you need to produce an artifact of Helm Chart version orchestration.
What method does your software use for LICENSE authorization?
If it is free software, you do not need to manage the LICENSE.
If the software is paid and relies on a self-built LICENSE service for LICENSE issuance and activation, it needs to be migrated to use the Marketplace LICENSE service.
If the software is paid but previously had no LICENSE management, it is recommended to integrate with the Marketplace LICENSE service to manage the LICENSE.
Technology Self-Check
For development teams with the following technical experience, it will be greatly helpful in the process of listing on the Marketplace. Teams lacking relevant experience can conduct technical pre-research in advance:
Terraform declarative syntax and deployment techniques (if the software is released based on CVM images);
Marketplace leverages Terraform syntax for resource declaration, with the resource deployment engine being self-developed.
If the software is based on a container, the following is required:
K8s container management technology.
K8s-based Helm Chart orchestration and delivery technology.
Commonly used IaaS/PaaS products on Tencent Cloud, including TKE, EKS, CVM, MySQL, Redis, COS, ES, TDMQ, CLS.
Technical Recommendations
When listing applications, vendors are obligated to design high-availability and high-reliability architectures for published applications, which can be achieved through the application's own mechanisms or by utilizing the high-availability solutions provided by Tencent Cloud.
The following are some high-availability solutions for applications and data on Tencent Cloud, for reference.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback