Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- On September 4, 2026, Alibaba said QwenWork reached 30 million users after one month of public beta in China, with enterprise accounts accounting for more than half. This is an official disclosure, not an independently audited active-user count.
- The international edition is in public beta on the web and desktop clients, focusing on Asia, the Middle East and Latin America, with individual and enterprise plans.
- Build a five-layer inventory of people, devices, QwenWork accounts, business systems and network egress before enabling browser, file or CRM/ERP permissions.
- Fixed egress can improve access consistency and reproducibility for cross-region teams, but cannot replace subscriptions, model quotas, connector permissions, data governance or product availability.
- Run a small pilot with nonsensitive tasks. Stop expanding if permissions are exceeded, audits are missing, data locations are unclear or network evidence is contradictory.
What happened: 30 million users is an adoption signal, not an integration verdict
At 13:05 on September 4, 2026, Alibaba's official X account reported that QwenWork had reached 30 million total users after one month of public beta in China, with enterprise accounts making up more than half. An official article that day also said the product had shipped 120 version updates and added more than 1,000 features in 30 days. The figures indicate rapid expansion, but the original does not define total users as daily active users, paying users or independent enterprises.
During product selection, label these figures as officially disclosed by Alibaba. Do not convert them into retention rates, market share or stability promises. Actual suitability depends on regional availability, plan entitlements, data boundaries, authorized systems, audit capabilities and pilot results.
Confirm the version, entry point and task boundaries first
The international edition of QwenWork entered public beta on August 26, 2026. Official information says it is available through web and desktop clients, offers English and Simplified Chinese interfaces, and provides subscription-plus-credit plans for individuals and enterprises. Public beta is not a formal service-level commitment. Teams should check region, seats, credits, model tiers and support channels in the console and contract pages.
Register planned capabilities separately: ordinary Q&A, document generation, browser operations, local files, scheduled tasks, website publishing, connectors and cross-system operations. Record who will use each, what data it handles and which permissions it needs. Passing a low-risk summarization task does not justify opening local files or core business systems.
Map accounts and network paths with a five-layer inventory
The first layer records people and roles; the second, managed devices and browsers; the third, QwenWork accounts, plans and model tiers; the fourth, authorized systems such as DingTalk, CRM, ERP and cloud drives; and the fifth, offices, remote workstations or fixed proxy egress. Every layer needs an owner, purpose, region, permission scope, change date and revocation method.
Cross-region teams should not move the same administrator account repeatedly among temporary networks. For enterprise access that requires long-term maintenance, assign stable regional egress to fixed workstations or clearly defined business groups, and retain redacted DNS, connection, authentication and target-response records. Network egress is for consistent access and troubleshooting, not bypassing regional, account or product restrictions.
Grant least-privilege access to browsers, local files and connectors
Official descriptions say that, with user authorization, QwenWork can navigate websites, operate the local computer and execute multistep tasks, and plans to connect to enterprise tools through a connector framework. The risk is not merely whether it clicks automatically, but which information it can read, modify and send externally. Pilot accounts should access only the minimum directories, sites and system roles needed for the sample task.
Do not put production keys, customer information, payment credentials or complete proxy-account details into prompts, shared skills or public screenshots. For CRM or ERP work, prefer read-only test tenants, synthetic data and separate service accounts. Expand gradually only after the read fields, write actions, approval points, log retention and permission revocation can all be reviewed.
Verify sources, actions and final state in cross-system workflows
Alibaba's enterprise examples include querying customer records, inventory and orders from collaboration tools and synthesizing business recommendations. Your own acceptance checks must go beyond the final natural-language response. Each task should record data sources, query times, authorized identity, recommendations and actions actually executed. Orders, inventory, payments and permission changes should still be confirmed through the original systems.
Prepare three sample types: read-only information access, low-risk writes requiring human confirmation, and high-risk actions that must be prohibited. If the agent treats stale inventory as live, cannot identify a source, skips human confirmation or repeats writes across systems, stop the pilot immediately and clean up the resulting test data. Do not hide permission and state problems by simply making prompts longer.
Troubleshoot fixed egress and application errors at separate layers
Pages that will not open, DNS failures, connection timeouts, TLS certificate errors and proxy-authentication failures belong to the network layer. Missing features after login, insufficient credits, unavailable model selection, connector access denial and unauthorized local files belong to the account and application layer. Preserve the time, entry point, device, egress, status code and request identifier first, then retest after changing only one variable.
A fixed proxy egress can reduce cross-region login drift and make failures easier to reproduce on the same device and network. It cannot repair invalid accounts, subscriptions, model quotas, organization policies or connector authorization. Enter PuppyIP's proxy-connection troubleshooting flow only when there is clear evidence of DNS, TCP, TLS, timeout or proxy-authentication problems.
Seven pilot steps, stop conditions and rollback
Proceed in order: confirm the official entry point and region; build the five-layer asset inventory; create least-privilege test accounts; prepare nonsensitive samples; fix the device and network egress; record ten to twenty reproducible tasks; and have business, IT and security teams review them together. After acceptance, expand in batches by department and task type. Do not open company-wide files and business systems all at once.
Stop expansion if permissions are exceeded, audit logs are missing, data-storage locations are unclear, actions cannot be undone, network egress conflicts with account-region policies, repeated errors lack request evidence, or public-beta behavior changes frequently. Keep the original workflow and manual path available, revoke connector, file and administrator permissions, record affected tasks, and wait for official clarification or a support response.
Sources
Frequently Asked Questions
Are all 30 million QwenWork users paying or active users?
The official original only says total users reached 30 million and enterprise accounts made up more than half. It does not define the number as paying users, daily active users or independent enterprises. Do not convert it yourself.
Has the QwenWork international edition entered full commercial availability?
Official information says the international edition has been in public beta since August 26, 2026. Enterprises should separately verify current regions, plans, terms of service, data processing and support commitments.
Which permissions should an enterprise pilot open first?
Start with read-only test tenants, synthetic data and separate service accounts. Open only the directories, sites and system roles needed for one low-risk task. Consider writes and sensitive data only after audits and rollback have been verified.
Why should cross-region teams record fixed network egress?
Fixed devices and stable regional egress reduce changes in the access environment and make DNS, connection, authentication and target responses easier to reproduce. This does not authorize bypassing regional or account rules.
Should I change proxies first when a QwenWork login or task fails?
No. Distinguish network problems from account, subscription, model, connector and permission issues first. Investigate egress only when there is explicit DNS, connection, TLS, timeout or proxy-authentication evidence.
When should a pilot stop immediately?
Revoke permissions and restore the original workflow if permissions are exceeded, logs are missing, sensitive-data boundaries are unclear, writes cannot be undone, actions repeat, sources cannot be verified or public-beta behavior cannot be reproduced reliably.