Choose the integration depth
Use UIKits for standard calling and live interfaces, or Core SDKs when your application needs its own interaction design.
Tencent CloudAI and live apps on Tencent Cloud
Procure Tencent-native model, real-time audio/video and edge services. Corebyte coordinates resource selection, account arrangements and implementation scope.
Plan a Tencent Cloud purchaseModel access with TokenHub
Tencent Cloud’s model service platform brings Tencent HY and supported third-party models into one supplier-managed service. Choose the model and capacity your application needs.
- Text and multimodal models
- Conversation, reasoning, code and visual understanding, selected by the exact model and version.
- Content generation
- Image, video, speech and 3D services, with separate specifications and usage units.
Model ID, service region, quota and metered usage are confirmed in the procurement scope.
Browse available modelsTRTC for live interaction
Put voice/video calls, conferences and interactive live sessions inside your application, using Tencent RTC SDKs and UIKits.
- Voice and video calls
- Online conferences
- Interactive live streaming
- AI voice interaction
Plan the complete media path
Match the real-time link, device platforms and weak-network needs; scope recording, transcoding and AI voice components separately.
What determines the RTC purchase
- Peak concurrency and participant duration
- Resolution, recording and transcoding requirements
- SDK platforms, deployment regions and service scope
Audio/video duration, recording and other services use their own billing rules. Chat MAU is a separate measure.
TRTC official product pageEdgeOne at the edge
Deliver your sites and APIs through Tencent Cloud’s edge platform, combining acceleration, security policies and edge development around the same application.
Bring content closer
Cache static assets and route dynamic requests to reduce unnecessary origin traffic.
Protect the request path
Select WAF, DDoS and Bot controls by plan, then tune policies for the application’s real traffic.
Operate with evidence
Use request analysis and log delivery to review cache behaviour, origin access and security events. Edge functions support scoped logic close to users.
Confirm domains, origin locations, certificates, DNS permissions, cache rules, security scope and log retention before deployment.
EdgeOne official product pageStart with the application
A model request, a live session and a web request need different resources. Select a scenario to see the purchasing inputs.
Connect models to business data
- Resource combination
- TokenHub + eligible Knowledge Engine APIs; CVM and COS where the application requires them.
- Before quotation
- Model and version, account permissions, region, request volume, concurrency and data boundary.
- Usage to reconcile
- Model tokens or task units; document processing, compute and storage are itemised separately.
- Delivery record
- Agreed model ID, access path, quota, resource inventory and usage/billing references.
Build a live interaction service
- Resource combination
- TRTC with the required Call, Conference or Live components; Chat and recording only where needed.
- Before quotation
- Peak participants, platforms, media quality, participant duration and recording needs.
- Usage to reconcile
- RTC duration, recording/transcoding units and Chat MAU are reconciled separately.
- Delivery record
- Application identifiers, authorised SDK access, configuration record and agreed verification scope.
Deliver and protect the application
- Resource combination
- EdgeOne with the selected acceleration and security plan; COS or CVM can provide the origin.
- Before quotation
- Domains, origins, markets, certificate/DNS control, traffic profile and security rules.
- Usage to reconcile
- Plan, requests, traffic and additional capabilities follow the selected product’s billing rules.
- Delivery record
- Domain and origin configuration, cache/security policies, logs and billing reference.
Procurement & handover
Confirm the account, the region and the delivery record.
01RequirementsPrepare the requirements
Share the purchasing entity, actual usage countries, existing Tencent Cloud accounts, target regions, models and estimated resource or media usage.
02ValidationAgree and validate the scope
Specify the supply route, account arrangement and separate model, infrastructure, media and service charges. Use a controlled test for model behaviour or real-time quality before launch.
03HandoverMake operations explicit
Document resource identifiers, access controls, metering, billing ownership and failure handling. Support coverage, escalation responsibilities and change or exit work are agreed separately.
Full purchasing requirements
TokenHub: plan model access for your application.
Match model access to the intended account, application and users.
Model and account eligibility
Confirm the target model, version, required activation, identity verification and account-specific quota. A product page alone is not proof that a particular account can use every listed model.
Endpoint and processing scope
Choose the documented endpoint and matching key for the agreed service. A Singapore entry point may route to a wider inference scope; confirm processing and data requirements separately.
Application access and metering
Scope key management, application integration and usage reconciliation. Separate input, output and any other applicable metering categories, and test the agreed model before production use.
Real-time services and the infrastructure behind them.
Plan application delivery and operating resources as part of the same project.
Real-Time Communication
Evaluate RTC for interactive audio and video use cases. Define user locations, integration work, expected concurrency and media-quality acceptance requirements.
EdgeOne
Assess edge application delivery and security services for the intended markets. Confirm the selected plan, domain arrangements and available features rather than assuming universal coverage.
CVM, COS and databases
Combine Cloud Virtual Machine, Cloud Object Storage and suitable database services around application workloads, data retention and backup. Include network and media-related charges in the estimate.
Confirm the account, the region and the delivery record.
Keep business terms and technical access consistent from proposal to handover.
Prepare the requirements
Share the purchasing entity, actual usage countries, existing Tencent Cloud accounts, target regions, models and estimated resource or media usage.
Agree and validate the scope
Specify the supply route, account arrangement and separate model, infrastructure, media and service charges. Use a controlled test for model behaviour or real-time quality before launch.
Make operations explicit
Document resource identifiers, access controls, metering, billing ownership and failure handling. Support coverage, escalation responsibilities and change or exit work are agreed separately.
Account & responsibilities
Tencent Cloud channel services
Discuss Tencent Cloud procurement through our channel services. The contracting entity, supply route and applicable authorisation material are confirmed before ordering.
Confirm product availability, model activation, account eligibility, regional conditions and service responsibilities for the specific order.
Company and credential information ↗More about this service
Bring Tencent Cloud infrastructure and model requirements into one procurement discussion, including the products, region and expected usage.
Products and resources
Tencent Cloud — compute, storage, networking and model services. These are examples of procurement options. Specific products, regions and delivery methods are confirmed in your proposal.
Model services through your chosen cloud
Browse the model catalogue for available channels. The exact model, version, region and delivery arrangement are confirmed in your proposal.
Prepare your procurement requirements
Tell us the products, region, expected usage and any existing cloud accounts. We confirm the resource scope, account arrangement and billing details before delivery.
Company and channel information
Review our operating companies and published channel credentials. The qualified entity responsible for contracting and delivery is identified in the agreement.
Confirm product availability, model activation, account eligibility, regional conditions and service responsibilities for the specific order.
Official resources
Official resources · Tencent Cloud Architecture Icons
Start with the resources you need.
A product list, preferred region and estimated usage are enough to begin a conversation.
Discuss your requirements