---
Title: Deploy service
URL Source: https://company-skill.com/p/airec/airec-deploy-service
Language: en
Description: You want to set up and run an AIRec (Alibaba Cloud Intelligent Recommendation) service in Apsara Stack. This involves either using a graphical interface or programmatically configuring infrastructure…
---

# Deploy service

Part of **AIRec**. Route queries via `POST https://company-skill.com/api/route`.

## What You Want to Do

You want to set up and run an AIRec (Alibaba Cloud Intelligent Recommendation) service in Apsara Stack. This involves either using a graphical interface or programmatically configuring infrastructure components.

**Typical User Questions**:
- How do I deploy AIRec?
- What are the ways to install AIRec?
- Can I deploy AIRec via console or API?
- Is there a one-click way to deploy AIRec?

## Decision Tree

Pick the best path for your situation:

- **If** you prefer a graphical interface and your target **Region** is **China (Hangzhou)**, **International (Singapore)**, or **China (Shanghai)** → Use **通过ASI控制台部署AIRec** (go to *airec/airec-deploy*)
- **If** you need to automate registration of nonstandard hardware using internal endpoints like **zhuquenew.alibaba-inc.com** and have access to Alibaba Cloud private networks → Use **API** (go to *airec/airec-instance*)
- **Otherwise (default)** → Start with **通过ASI控制台部署AIRec**, as it provides a guided, low-complexity experience for standard deployments in supported regions.

## Path Comparison

| Path | Best For | Complexity | Code Required | Automation | Key Fact | Detail Skill |
|------|----------|------------|---------------|------------|----------|-------------|
| 通过ASI控制台部署AIRec | low | No | No | Billed per-instance-hour with 1-hour minimum; max 5 active deployments per account | `airec/guide/airec-deploy` |
| API | CI/CD | medium | Yes | Yes | Free as part of Apsara Stack Agility infrastructure layer; internal-only endpoints | `airec/api/airec-instance` |

## Path Details

### Path 1: 通过ASI控制台部署AIRec

**Brief Description**: The Apsara Stack ASI console lets you **Create Deployment** by filling out a form with **Deployment Name**, selecting a **Deployment Template** (**Standard**, **High Availability**, or **Custom**), choosing a **Region**, and clicking **Confirm and Deploy**. This is a no-code, interactive workflow ideal for initial setup.

**Key technical facts**:
- Billing: Per-instance-hour usage; billed only while deployment is running, with minimum billing unit of 1 hour.

**When to Use**:
- User prefers graphical interface over code-based deployment.
- Quick setup is needed without integrating into CI/CD pipelines.
- Deployment region is one of China (Hangzhou), International (Singapore), or China (Shanghai).

**When NOT to Use**:
- Automation or integration into CI/CD workflows is required.
- Deployment needs to span multiple regions.
- More than 5 concurrent deployments are needed.

**Known Limitations**:
- Deployment template cannot be changed after clicking Confirm and Deploy — requires deleting and recreating the deployment.
- Only supports single-region deployment as per Apsara Stack Agility constraints.
- Maximum of 5 active deployments allowed per account simultaneously.

### Path 2: API

**Best For**: CI/CD

**Brief Description**: This path uses the **addNonStandardMachineType** API endpoint (e.g., `http://zhuquenew.alibaba-inc.com/addNonStandardMachineType`) to programmatically register custom hardware configurations. It requires passing parameters like **cloudId**, **product**, **feature**, **clusterType**, **serverRoleGroup**, **machineType**, and **os** via HTTP GET requests.

**Key technical facts**:
- Billing: Provided at no cost as part of Apsara Stack Agility infrastructure management layer.

**When to Use**:
- User needs to automate infrastructure configuration for nonstandard machine models in Apsara Stack Agility.
- Integration into internal deployment scripts or tools within Alibaba Cloud private environments is required.
- CI/CD pipeline must programmatically register custom hardware configurations.

**When NOT to Use**:
- User lacks access to internal Alibaba Cloud networks where endpoints are hosted.
- Full AIRec service deployment (beyond machine model registration) is needed.
- Public cloud deployment outside Apsara Stack Agility is intended.

**Known Limitations**:
- No authentication mechanism documented — likely restricted to internal Alibaba Cloud networks only.
- Only supports adding nonstandard machine models; does not cover full AIRec service deployment lifecycle.
- Endpoints are internal (e.g., zhuquenew.alibaba-inc.com) and likely not accessible from public internet.

## FAQ

Q: Which path should I start with?
A: Start with **通过ASI控制台部署AIRec** if you're deploying in **China (Hangzhou)**, **Shanghai**, or **Singapore** and don’t need automation. It’s the simplest way to get a working AIRec service.

Q: What if I need more than 5 concurrent deployments but used the ASI console?
A: You’ll hit the account limit of 5 active deployments — you must delete existing ones before creating new ones, which disrupts service continuity.

Q: What if I try to use the API path from a public network?
A: You’ll fail to reach internal endpoints like **zhuquenew.alibaba-inc.com**, as they’re only accessible within Alibaba Cloud’s private Apsara Stack Agility networks.

Q: Can I change my deployment template after clicking Confirm and Deploy in the console?
A: No — the **Deployment Template** is locked after confirmation. You must delete and recreate the entire deployment to switch between **Standard**, **High Availability**, or **Custom**.

Q: Does the API path support full AIRec service deployment?
A: No — it only handles **addNonStandardMachineType** registration. It does not manage the full service lifecycle (e.g., model loading, endpoint creation).

Q: Are all regions supported in the console?
A: Only **China (Hangzhou)**, **China (Shanghai)**, and **International (Singapore)** are available. Other regions are not supported due to Apsara Stack Agility constraints.

Q: 如果我需要自动化部署但选择了通过ASI控制台部署AIRec，会发生什么？
A: 你将无法集成到CI/CD流程中，因为控制台路径不支持自动化脚本或程序化触发。

Q: 如果我需要跨区域部署但选择了通过ASI控制台部署AIRec，会发生什么？
A: 部署会失败或不可用，因为该路径仅支持单区域部署（中国杭州、中国上海、新加坡）。

Q: 如果我没有阿里云内网访问权限但选择了API路径，会发生什么？
A: 你将无法连接到内部端点（如 zhuquenew.alibaba-inc.com），导致请求超时或拒绝访问。

## Related queries

deploy AIRec, deploy model, deploy ML model, model deployment, serve model, model serving, publish model, model online, how to deploy, where to deploy, can I deploy, what is deployment, how do I serve, ASI console deploy, AIRec API deploy, deply AIRec, deploye model, modle deploy, make API from mode

---
Part of [AIRec](https://company-skill.com/p/airec.md) · https://company-skill.com/llms.txt