TL;DR: Tried out Alibaba Cloud (Qwen) for full-time development work. After buying a paid token plan on a dedicated sales rep’s advice, they emailed me a $200 / 70M free token "Welcome Gift." What followed was a 2-week nightmare: broken SMS delivery for Mexican numbers, support denying local carrier issues, and then changing excuses (claiming the offer was "Enterprise only" or invalidated by my recent purchase, despite the promo email arriving after I paid). Between broken onboarding, contradictory support, and Qwen’s poor token-per-dollar ratio compared to Cursor/Claude Code/DeepSeek/Gemini, the developer experience is a complete mess. Avoid.

As developers, evaluating new cloud providers and AI APIs is part of our routine. When a major cloud infrastructure provider reaches out directly and follows up with promotional incentives, it seems like a natural opportunity to benchmark their platform and integrate their models into daily workflows.

However, my recent 3-week experience testing Alibaba Cloud (Qwen) revealed a deeply frustrating cycle: misleading sales outreach, broken onboarding workflows, uncoordinated support teams, and pricing that simply fails to compete with alternative AI tools.

Here is an honest breakdown of the facts.

1. The Onboarding Trap: “Dedicated Support” vs. Actual Help

My interaction began on July 28, 2026, when a dedicated Cloud Service Manager reached out via email to offer tailored solutions and discounts. Having recently registered an account to test their platform for full-time development work, I replied with a straightforward operational question:

>My Question: “I ran out of weekly tokens very quickly. Based on my usage, what would you recommend me to be able to work full time the entire week (at least 40+ hours a week)?”

The response from dedicated support on August 2 was completely generic:

>The Recommendation: “I think the token plan is currently the most cost-efficient plan. If you find that you’ve run out of usage, I would suggest upgrading your plan or buying an extra token package.”

There was no custom guidance, no specialized discount, and no real account assessment — just a basic prompt to upgrade my paid token package. 

2. The Marketing Paradox: The Post-Purchase “Welcome Gift”

On August 4, just two days after purchasing a paid plan, Alibaba Cloud’s marketing team delivered a promotional email to my inbox:

• The Offer: 70+ Million free Tokens and $200 in Instant Credits.
• The Terms: “With no minimum spend required” and a direct “Activate Now” button.

When I attempted to claim the offer, the workflow broke entirely:

1. The Regional Gateway Issue: The platform claimed my mobile number was invalid and failed to deliver SMS verification codes. When raised with support, they initially insisted the messages were successfully delivered on their end, implying a local carrier issue. Days later — after extensive back-and-forth explaining regional carrier behavior in Mexico — the SMS delivery issue was silently resolved on their backend.
2. Changing Ineligibility Reasons: Once the phone verification blocker was clear, claiming the coupon failed with a “historical orders” error. Support then claimed the promotion was strictly for “Enterprise accounts” or “New accounts with zero purchase history.”

This created a complete contradiction: Alibaba Cloud explicitly delivered a targeted welcome gift to an active account’s inbox a week after a purchase was made, only to block the claim on the backend using undisclosed terms and prior purchase history.

3. Support Circled in Red Tape

Over the course of 10+ days and multiple support ticket updates:

• Technical teams requested screenshots of emails they claimed were never sent.
• Account history rules were cited to void promotional emails sent directly by their own system.
• Hours of developer time were consumed troubleshooting internal gateway bugs, with zero willingness from support to manually credit the promised tokens or acknowledge the workflow breakdown.

The experience ultimately concluded with setting the support ticket to unresolved, as continuing to debug a provider’s internal marketing and SMS infrastructure is an unreasonable investment of time.

4. Technical Assessment: How Qwen Actually Stacks Up

Setting the customer experience aside, the core question for any developer is value: Is the platform worth the cost and friction?

While models like Qwen 2.5 / 3.5 offer respectable performance, the ecosystem value proposition rapidly falls apart when compared to the current market:

• Performance & Efficiency: Models in similar or adjacent tiers — such as DeepSeek V3/V4, Gemini 2.5 Flash, or GLM-5 — deliver superior or equivalent performance and coding efficiency at far more competitive price points or rate limits.
• Cost vs. Developer Workflows: The baseline Alibaba Cloud token packages provide minimal headroom for sustained, full-time development work (40+ hours/week). When compared to specialized developer platforms or subscription-based coding environments (such as Cursor or Claude Code), the token-to-dollar ratio on Alibaba Cloud is significantly less competitive.

Final Takeaways

Marketing campaigns and outreach emails are meant to attract developers, not create administrative burdens.

If a cloud platform sends promotional incentives to an active user’s inbox, buries the process behind broken regional SMS verification, shifts eligibility terms after technical barriers are cleared, and offers uncompetitive token-per-dollar rates, it severely damages developer trust.

For teams and independent engineers evaluating LLM API providers, technical capabilities are only half the equation. Onboarding friction, clear terms, and respectful customer support matter just as much — and in this case, Alibaba Cloud fell far short.

I've used Google's AI ecosystem since Bard -> Gemini 1.0 -> 3.7 now, and Antigravity since day one. I love Google's engineering, but after using Antigravity daily on real infra (Rust, C allocators, game servers, FreeBSD PF), I hit a wall.

So I audited language_server_linux_x64 [internal codename Jetski/Cortex]. It's not hallucinating. It's hardcoded behavior.

TL;DR: The agent isn't ignoring you, it's being told to.

1. The smoking gun: "Don't ask for permission"
   Every write_to_file call injects this into context:

>

In prod/zero-trust envs, this is insane. It compiles/runs code you didn't approve.

2. The "Silent Treatment" loop
   You type "STOP / don't edit files" and it keeps going. Why? There's a planner config CascadePlannerConfig / IsAutonomous that injects on every background task finish:

>

It's an Aggressive Action Bias. It prioritizes its checklist over your interrupt.

3. 1500-token web-dev bloat on EVERY turn
   Every turn injects <web_application_development> with HSL palette rules, Tailwind bans, "no purple on dark", SEO dogma, etc.

Try debugging a WebSocket relay in Rust and you have 1500 tokens of CSS rules eating your context.

4. Sessions die on crash
   Abrupt exit = Electron state.vscdb loses tab refs, shows blank chat. The JSONL/SQLite is still on disk, UI just doesn't recover it. For a Google-built dev tool, should be atomic.

I write this out of genuine passion for what this tool potential. Google is known for building world-class platforms that empower developers, not tools that wrestle them for control.

Antigravity does not need artificial proactivity tricks or hidden override prompts to prove Gemini’s brilliance. The true hallmark of an intelligent developer agent is precision, predictability, restraint, and an absolute respect for the engineer at the keyboard.

Does it?

I've used Google's AI ecosystem since Bard -> Gemini 1.0 -> 3.7 now, and Antigravity since day one. I love Google's engineering, but after using Antigravity daily on real infra (Rust, C allocators, game servers, FreeBSD PF), I hit a wall.

So I audited language_server_linux_x64 [internal codename Jetski/Cortex]. It's not hallucinating. It's hardcoded behavior.

TL;DR: The agent isn't ignoring you, it's being told to.

1. The smoking gun: "Don't ask for permission"
   Every write_to_file call injects this into context:

>

In prod/zero-trust envs, this is insane. It compiles/runs code you didn't approve.

2. The "Silent Treatment" loop
   You type "STOP / don't edit files" and it keeps going. Why? There's a planner config CascadePlannerConfig / IsAutonomous that injects on every background task finish:

>

It's an Aggressive Action Bias. It prioritizes its checklist over your interrupt.

3. 1500-token web-dev bloat on EVERY turn
   Every turn injects <web_application_development> with HSL palette rules, Tailwind bans, "no purple on dark", SEO dogma, etc.

Try debugging a WebSocket relay in Rust and you have 1500 tokens of CSS rules eating your context.

4. Sessions die on crash
   Abrupt exit = Electron state.vscdb loses tab refs, shows blank chat. The JSONL/SQLite is still on disk, UI just doesn't recover it. For a Google-built dev tool, should be atomic.

I write this out of genuine passion for what this tool potential. Google is known for building world-class platforms that empower developers, not tools that wrestle them for control.

Antigravity does not need artificial proactivity tricks or hidden override prompts to prove Gemini’s brilliance. The true hallmark of an intelligent developer agent is precision, predictability, restraint, and an absolute respect for the engineer at the keyboard.

Does it?