AIsphere
Real product and funding momentum, but still an under-documented unicorn security
AIsphere has enough product, scale, and financing evidence to stay investable, but the current unicorn-level price is still too under-documented on ARR quality, margin durability, and security terms to justify a buy call.
Cover facts
Company profile
AIsphere (北京爱诗科技有限公司) is a Beijing-based generative-video startup founded in April 2023 around founder and CEO Wang Changhu, with co-founder Xie Xuzhang publicly visible in 2026 financing coverage. Its flagship product, PixVerse, spans text-to-video, image-to-video, creator templates, mobile distribution, enterprise-style APIs, and a real-time world-model track through PixVerse R1. Public financing moved quickly from large Series A fundraising in 2025 to an Alibaba-led Series B and a CDH-led $300 million Series C in March 2026. The public case for the company is therefore real and scaled, but still under-documented on revenue quality, margin structure, governance, and security terms.
- Website
- aishiai.com
- Founded
- 2023-04-07
- Founders
- Wang Changhu, Xie Xuzhang
- Founding location
- Beijing, China
- Headquarters
- Beijing, China
- Product
- PixVerse combines proprietary AI video foundation models with web/mobile creation tools, creator templates, team/canvas workflows, API access, and a real-time world-model branch (R1) intended to extend the company from clip generation toward interactive audiovisual worlds.
- Customers
- Consumer creators and prosumers, social-video users, marketers and SMB content teams, licensed-IP activations, and a growing set of enterprise/API or partner workflows that need scalable video generation.
- Business model
- Most likely a mix of consumer subscriptions and credits, higher-tier plan upgrades, enterprise/API packaging, and partner / licensing workflows rather than a single monoline consumer app business; exact channel mix remains undisclosed.
- Stage
- Series C private company / unicorn-level headline valuation frame
- Funding status
- Publicly disclosed financing includes a >CNY400M aggregate Series A by March 2025, a $60M Alibaba-led Series B in September 2025, and a CDH-led $300M Series C in March 2026, with the latest round widely framed as a record financing for China's AI-video segment.
Executive summary
Top strengths
- Real product surface across consumer app, web, templates, APIs, and real-time world-model R&D rather than a single demo model.
- Public financing momentum is exceptional for a two-year-old China AI-video startup, culminating in a CDH-led $300M Series C.
- Reported scale markers (>100M users, >16M MAU, >$40M ARR floor) are meaningful if validated and support continued diligence rather than dismissal.
- PixVerse appears in independent benchmark and consumer-app ecosystems, suggesting the product story is broader than company-only marketing.
Top risks
- Public evidence still does not reconcile exact post-money valuation, preference stack, or the security quality of the March 2026 round.
- The >$40M ARR figure is company-linked and unaudited, leaving open whether revenue is durable enterprise/API spend or more fragile creator demand.
- AI-video competition remains intense across OpenAI, Runway, Kling, Wan, Hailuo, Jimeng/Seedance, and Pika, limiting pricing power and lock-in.
- China regulatory, labeling, copyright, and advanced-compute dependency risks could impair monetization or margin quality even if user growth stays strong.
Open gaps
- Audited ARR bridge, channel mix, gross margin, and unit economics by product surface remain undisclosed.
- March 2026 term sheet, post-money cap table, liquidation waterfall, and side letters are not public.
- Public sources do not disclose paying-customer count, retention / NRR, or top-customer concentration.
- Board composition, compliance audit artifacts, and detailed trust-and-safety implementation remain incomplete in the fetched record.
Contents
01Company Overview
1.1 Identity, founding, and product scope
AIsphere is publicly traceable as Beijing Aishi Technology Co., Ltd. (北京爱诗科技有限公司), a Beijing-based startup founded in April 2023. The official corporate site describes the company as building world-leading AI video generation large models and applications, while PixVerse serves as the outward-facing product layer for both consumer creation and enterprise API workflows. Public launch coverage shows PixVerse entering the overseas market in early 2024, and the official product surface now spans web, mobile, templates, APIs, and world-model research. That combination matters because AIsphere is not presenting itself as a one-off demo app; it is positioning itself as a vertically integrated video-model company with proprietary foundation-model R&D, distribution surfaces, and monetizable creation tooling. The fetched evidence also shows the company actively maintaining separate consumer, blog, app-download, and enterprise-facing surfaces, which strengthens confidence that the product footprint is operational rather than aspirational.[CO001, CO002, CO003, CO004, CO005, CO008]
| metric | value/status | date | confidence | gap |
|---|---|---|---|---|
| Legal / public name | Beijing Aishi Technology Co., Ltd. / AIsphere | 2026-07-03 | medium | |
| Founded | 2023-04-07 | 2023-04-07 | medium | |
| Headquarters | Beijing, China | 2026-03-06 | medium | |
| Current stage | Series C private startup at unicorn threshold / ~$1B headline valuation | 2026-03-12 | medium | Fetched public sources support the direction of a unicorn-level valuation but do not reconcile an exact post-money figure. |
| Latest disclosed round | $300M Series C led by CDH Investments | 2026-03-12 | medium | |
| Prior major round | $60M Series B led by Alibaba | 2025-09-24 | medium | |
| Reported ARR | >$40M at end-2025 | 2026-03-12 | medium | ARR is media-reported, not audited or company-filed. |
| Reported user base | >100M users globally | 2026-03-12 | medium | User count is repeated across company-linked and media-linked coverage but not independently audited. |
| Reported MAU | >16M | 2026-03-12 | medium | Monthly active users are cited in one Yicai chain and not independently corroborated in the fetched set. |
| Core products | PixVerse consumer + enterprise AI video platform; R1 real-time world model; V6 cinematic model | 2026-03-18 | medium | |
| Public governance visibility | low | No full board roster, cap table, or preference-stack disclosure appears in the fetched public record. |
Rows mix company claims, media reports, and observed product surfaces. Null values mark items the fetched public record does not verify precisely enough for a clean KPI strip.
[CO001, CO002, CO003, CO009, CO012, CO015]AIsphere connects proprietary video-model R&D to consumer distribution, enterprise APIs, strategic cloud support, and a still-open disclosure layer.
[CO004, CO005, CO024, CO025, CO030, CO031]1.2 Leadership, founder-market fit, and governance visibility
The public leadership record centers on Wang Changhu and, to a lesser extent, co-founder Xie Xuzhang. Wang’s prior experience at Microsoft Research Asia and ByteDance gives AIsphere a founder profile that maps directly to high-scale video and computer-vision systems, which likely helps both recruiting and investor trust. Xie appears in 2026 financing coverage as a public voice on strategy, global expansion, and the company’s world-model ambition. What is missing is equally important: the fetched public record does not disclose a full board roster, exact ownership structure, or preference-stack detail. That leaves governance and economic control less transparent than the fundraising headlines suggest. For diligence purposes, the lack of a published board roster matters almost as much as the presence of a strong founder, because later-round control can change quickly in capital-intensive AI companies.[CO006, CO007, CO036, CO040]
| person | role | background | founder-market fit or coverage | key-person dependency |
|---|---|---|---|---|
| Wang Changhu | Founder and CEO | Former Microsoft Research Asia researcher and former ByteDance visual-technology lead | Strong fit with computer vision, large-scale video systems, and AI talent recruiting | high |
| Xie Xuzhang | Co-founder | Publicly quoted on fundraising target expansion, market expansion, and world-model direction in 2026 coverage | Provides strategic and market-facing support but with a thinner public biography than Wang | medium |
The fetched public record clearly identifies Wang Changhu and repeatedly quotes Xie Xuzhang, but it does not disclose a complete executive bench or board roster.
[CO006, CO007, CO036]1.3 Funding history, stage, and investor coalition
AIsphere’s public financing path moved quickly from a >CNY400 million aggregate Series A by March 2025, to a $60 million Alibaba-led Series B in September 2025, to a $300 million Series C in March 2026 led by CDH Investments. The investor mix broadened across financial investors, strategic internet/cloud backers, state-linked funds, entertainment groups, and Southeast Asian financial institutions. Public coverage consistently describes the Series C as the largest single financing yet in China’s AI-video sector. That supports the user-supplied “Series C / unicorn” framing directionally, but the precise post-money valuation and preference terms remain under-disclosed in the fetched public record.[CO009, CO012, CO013, CO015, CO016, CO017]
| stakeholder | role | control or economic importance | diligence ask |
|---|---|---|---|
| CDH Investments | Series C lead investor | Anchors the headline 2026 scale-up round and valuation framing | Confirm ownership %, board rights, and liquidation preferences. |
| Alibaba / Alibaba Cloud | Series B lead investor and cloud partner | Supplies both capital and infrastructure / compliance support | Confirm exclusivity, cloud spend commitments, and strategic-control rights. |
| Fortune Capital | Early institutional backer | Helped fund the first disclosed scale-up round | Map whether early investors retained pro-rata through Series C. |
| Shenzhen Capital Group / Beijing AI Fund / E-Town Capital | State-linked capital providers | Signal policy and ecosystem support but may shape commercialization expectations | Clarify any policy, location, or industrial-partnership obligations. |
| Ruyi Holdings / 37 Interactive | Entertainment-sector investors | Potentially valuable for media / content distribution relationships | Test whether financial investment converts into distribution or licensing channels. |
| UOB Venture Management / Lion X Fund | Overseas financial investors | Support the global-expansion narrative and add non-mainland capital to Series C | Determine whether they add channel value or only balance-sheet capital. |
| Founders / management | Operating control | Public record identifies Wang and Xie but not the full cap table | Obtain cap table, board seats, vesting, and founder dilution history. |
This table enumerates the main publicly named capital and strategic stakeholders visible in fetched financing coverage. Control rights and ownership percentages remain private.
[CO009, CO012, CO013, CO015, CO016, CO017]AIsphere moved from a 2023 founding to rapid 2025-2026 financing, product iteration, and platform expansion while competition intensified.
[CO002, CO008, CO009, CO012, CO015, CO020]1.4 Traction claims, product milestones, and platform evolution
The company’s public story is unusually milestone-dense for a two-year-old startup. By March 2025, Yicai reported more than 40 million users and more than 15 million monthly active users. By late 2025 and early 2026, company-linked and media-linked coverage escalated that story to more than 100 million users, more than 16 million monthly active users, and ARR above $40 million. On the product side, AIsphere launched R1 in January 2026 as a real-time world model and V6 in March 2026 as a more controllable cinematic model, while official update pages show an expanding production platform that includes CLI, team, and enterprise-facing layers. The broad pattern is clear: AIsphere is scaling both product scope and distribution speed very rapidly.[CO010, CO011, CO014, CO018, CO019, CO020]
| date | event | type | amount/valuation/status | participants | implication |
|---|---|---|---|---|---|
| 2023-04-07 | Beijing Aishi Technology Co., Ltd. is established | founding | Company formed in Beijing | Founder Wang Changhu | Creates a dedicated AI-video startup shortly after Wang leaves larger-platform roles. |
| 2024-01-01 | PixVerse launches for overseas users | product | Consumer AI-video product enters market | AIsphere / PixVerse team | Gives the company an early global-consumer wedge. |
| 2024-03-18 | Series A round above RMB100M is reported | financing | US$14M equivalent disclosed by SCMP / >RMB100M | Fortune Capital-led round | Validates early investor appetite despite competitive skepticism. |
| 2025-03-06 | Series A cumulative financing exceeds CNY400M | financing | Series A5 led by Eminence; 40M+ users; 15M+ MAU | Eminence Ventures; Lighthouse Capital | Shows repeated early-stage capital access and consumer-adoption momentum. |
| 2025-09-24 | Series B closes at $60M | financing | $60M | Alibaba, Fortune Capital, Shenzhen Capital, Beijing AI Fund, Giant Network, Antler | Brings a top cloud/internet strategic investor into the company. |
| 2025-12-18 | Alibaba Cloud full-stack cooperation announced | partnership | Infrastructure, model-service, product, ecosystem, and business cooperation | AIsphere and Alibaba Cloud | Reduces some infrastructure uncertainty while increasing partner dependence. |
| 2026-01-14 | PixVerse R1 launches | product | 1080p real-time world model | AIsphere / PixVerse | Expands the story from text-to-video tooling toward interactive world models. |
| 2026-03-12 | Series C closes | financing | $300M; largest China AI-video round publicly reported; unicorn-level valuation narrative | CDH Investments + 20+ institutions | Elevates AIsphere into China’s top-funded AI-video startup cohort. |
| 2026-03-18 | V6 launches and platform narrative broadens | product | Cinematic control + CLI + production workflow emphasis | PixVerse product team | Signals a move from novelty templates toward pro / production usage. |
| 2026-03-18 | KrASIA highlights contrarian founding and competitive pressure | adverse | Subscription revenues reportedly cover costs, but competition remains intense | KrASIA / 36Kr retelling | Adds the main chapter-one caution that scaling still must beat far larger rivals. |
This is the single chronology of record for chapter 1. Month-level dates are used where the fetched public record anchors an event to a month but not an exact day.
[CO002, CO008, CO009, CO012, CO015, CO020]The public KPI picture shows unusually fast consumer and funding momentum, offset by limited audited disclosure.
[CO002, CO003, CO015, CO018, CO019, CO037]1.5 Adverse signals and disclosure caveats
The cautionary evidence is mostly strategic and disclosure-oriented rather than legal-penalty driven. KrASIA’s retelling of AIsphere’s rise emphasizes that the company was founded when many investors doubted independent video-model startups could survive beside OpenAI and China’s internet giants. The same article says subscription revenue now covers costs, but that remains a founder-reported milestone rather than an audited financial disclosure. More broadly, headline metrics such as ARR, user totals, and sector-leadership claims are still concentrated in company-linked or single-chain media reporting. Governance transparency is also thin: there is no clean public board roster, cap table, or exact Series C post-money valuation. That does not negate the business; it means chapter-one confidence should be grounded in product and funding reality while still carrying explicit evidence gaps.[CO032, CO033, CO034, CO036, CO037, CO038]
1.6 Exhibits
02Market Analysis
2.1 Market boundary: generative video AI is a workflow layer, not the whole AI economy
The most important discipline in this chapter is defining the boundary before sizing anything. The narrow market here is not all generative AI, and it is not all media software. TBRC defines generative AI in video creation as the use of generative models to create, edit, or enhance video content, while both TBRC and Research and Markets segment that category by deployment, application, and end-user. Those definitions capture text-to-video, image-to-video, editing and enhancement, collaboration, and cloud or on-premise delivery. They do not justify counting upstream GPU training spend, generic hyperscaler AI revenue, or non-AI production software as direct market revenue for video-creation vendors. The official surfaces of PixVerse, Runway, Pika, Vidu, Kling, Jimeng, and Wan also show that the competitive set now spans consumer creation tools, workflow platforms, and API products. That matters for AIsphere because the company sits inside a real but narrower wedge of the AI economy: creative-video generation and the workflows immediately around it, not the entire foundation-model stack.[CM001, CM002, CM003, CM004, CM005, CM006]
| Segment / category | Included spend | Excluded spend | Buyer / payer | Relevance to AIsphere |
|---|---|---|---|---|
| Consumer creation apps | Text-to-video, image-to-video, templates, editing, effects, subscriptions, and credits purchased by creators | Generic entertainment spending, non-AI editing tools, and unrelated social-platform ad revenue | Individual creator or prosumer payer | Relevant because PixVerse still competes for creator mindshare and bottom-up paid conversion |
| SMB / marketer workflow | Campaign video generation, ad creatives, social content, lightweight workflow automation | Broad marketing-cloud spend unrelated to video generation or production output | Marketing manager or SMB owner | Relevant because video AI can be funded from growth budgets rather than only creator subscriptions |
| Media / IP production | Collaborative production, branded templates, licensed content workflows, asset management, and distribution tooling | Traditional studio capex, unrelated post-production, and rights costs not tied to AI video workflows | Studio operations or media production budget owner | Relevant because controllability and branded workflows can support higher-value enterprise-like budgets |
| Developer / API layer | API calls, partner programs, workflow integrations, tool-builder usage, and embedded real-time video services | Generic cloud inference spend outside the video workflow or non-video developer tooling | Platform product owner or engineering budget | Relevant because AIsphere markets APIs and real-time video infrastructure, not only end-user creation |
| Enterprise / governed deployment | Team plans, governance, private or controlled deployment, procurement-led contracts, and compliance tooling | Broad digital-transformation budgets without a video-AI use case | IT, procurement, or business-unit owner | Relevant because enterprise buyers value control, governance, and workflow reliability more than one-off clip novelty |
| Adjacent but excluded upper layer | None directly counted as direct market revenue for video-app vendors | Foundation-model training capex, hyperscaler GPU spend, generic public-cloud AI revenue, and unrelated AI software | Compute and platform owners | Important as input cost and bargaining power, but not a clean direct TAM for AIsphere |
This table defines the countable market boundary for the chapter. It includes monetized video-generation workflows and excludes upstream AI infrastructure and unrelated software spend.
[CM001, CM002, CM003, CM004, CM005, CM006]2.2 Multiple sizing lenses are necessary because the published numbers measure different things
Public sizing only becomes usable once the chapter preserves multiple lenses instead of forcing one headline TAM. The narrowest lens comes from the dedicated generative-video reports: TBRC says the market reached $0.39 billion in 2025, grows to $0.47 billion in 2026, and reaches $0.98 billion in 2030; Research and Markets uses the same $0.47 billion 2026 starting point and the same $0.98 billion 2030 end point. That is a small market relative to the broader generative AI complex, where Fortune Business Insights estimates $103.58 billion in 2025, $161 billion in 2026, and more than $1.26 trillion by 2034. Those numbers are not contradictory so much as scope-mismatched: one measures a narrow application layer and the other measures a huge cross-modal technology stack. A third lens is adoption rather than revenue. a16z says AI video became fairly dependable for short clips and highlights video companies moving into the top consumer AI rankings, while Artificial Analysis shows enough convergence in quality and enough spread in pricing to support experimentation and buyer shopping. For diligence, the right answer is a range of frames, not a fake single TAM.[CM007, CM008, CM009, CM010, CM011, CM012]
| Publisher | Year / horizon | Geography | Value | Growth / adoption signal | What it actually measures | Limitation |
|---|---|---|---|---|---|---|
| The Business Research Company | 2025 current | Global | $0.39B | Market reaches $0.47B in 2026 and $0.98B in 2030 | Dedicated generative AI in video creation revenue pool | Narrow category lens only; not AIsphere-specific share |
| Research and Markets | 2026 current | Global | $0.47B | Projects $0.98B by 2030 at 20.4% CAGR | Dedicated generative AI in video creation market | Another narrow lens, but still not a company-specific SAM |
| Fortune Business Insights | 2025 current | Global | $103.58B | Broader market grows to $161B in 2026 and $1,260.15B by 2034 | Cross-modal generative AI market across many workloads | Far broader than video creation, so it should not be used as direct video TAM |
| a16z Top 100 Gen AI Consumer Apps | 2025 adoption proxy | Global consumer web/mobile | Ranking-based proxy | Video products enter top AI consumer rankings and Hailuo/Kling surpass Sora in monthly visits | Demand and usage proxy rather than revenue size | Does not show paid conversion or segment mix |
| Artificial Analysis | 2026 benchmark proxy | Global model benchmark surface | Elo 1069–1096 in cited examples | PixVerse V6 competes within a narrow quality band but at lower posted price than Veo 3.1 | Performance and price proxy for buyer experimentation | Benchmark scores are not the same as market share or revenue |
| PixVerse official pricing | 2026 monetization proxy | Global self-serve platform | $1 = 5 V6 starter videos | Usage-based credits show low-friction creator entry point | Bottom-up monetization and developer API economics | Company-authored pricing does not reveal realized net revenue or retention |
| Runway pricing | 2026 monetization proxy | Global self-serve plus enterprise | $12 / $28 / $76 plus enterprise custom credits | Tiered packaging supports creator, pro, and enterprise expansion | Comparable vendor pricing and packaging lens | Competitor pricing still does not reveal industry contract sizes or churn |
These rows intentionally preserve different units of analysis: narrow market reports, broad generative-AI context, consumer adoption proxies, and monetization proxies. They are complementary lenses, not additive TAM components.
[CM007, CM008, CM009, CM010, CM011, CM012]A multi-layer lens that keeps broad AI context, narrow video-market size, and monetization/adoption wedges separate.
This figure intentionally mixes direct market sizes with adoption and monetization wedges because no reviewed public source isolates a clean AIsphere-specific SAM/SOM.
[CM009, CM010, CM012, CM013, CM015, CM035]Published dollar ranges that preserve scope differences across narrow video creation and the broader generative-AI stack.
The rows are range presentations of different but related market quantities. They should be read as dispersion across scope and time, not as additive components.
[CM007, CM008, CM010, CM012]2.3 Buyer, user, and payer are fragmented across five economically different segments
The buyer map is more fragmented than a casual “creator app” label suggests. Individual creators are real users, and Google Play plus PixVerse's blog make clear that templates, viral effects, and mobile workflows can attract bottom-up adoption. But TBRC also names marketing and social-media use cases, and Vidu explicitly sells into ad and storytelling workflows, so marketers and SMBs are another budget owner. Media and IP holders form a third segment because branded content, licensed templates, and collaborative production processes require workflow control beyond one-off consumer prompts. Developers and API teams are separate again: PixVerse's R1 partner program targets studios, platform developers, and tool builders, while Runway markets a real-time Characters API. Finally, enterprise and governed teams buy differently from casual creators. They care about control, deployment model, team access, and contract packaging. In practice, that means the chapter has to distinguish user from buyer and buyer from payer: the end creator may love a product, but the economic decision often sits with a marketing lead, studio operations owner, platform product manager, or enterprise procurement function.[CM019, CM020, CM021, CM022, CM023, CM024]
| Segment | Buyer | User | Payer | Workflow | Budget owner | Adoption trigger |
|---|---|---|---|---|---|---|
| Creators / prosumers | Individual creator | Individual creator | Self-serve subscription or credits | Template use, social clips, personal storytelling | Creator wallet or side-income budget | Fast output, mobile convenience, low starting cost |
| Marketers / SMBs | Marketing lead or SMB owner | Marketer, social manager, or freelancer | Campaign budget | Ads, product promos, short-form social content | Growth or marketing owner | Need to produce more video creative with less time and staff |
| Entertainment / media / IP | Studio operations or branded-content owner | Editors, producers, licensors | Production budget | Branded templates, collaborative production, asset management | Production or content operations lead | Need controllability, collaboration, and brand-safe reuse |
| Developers / API teams | Product or platform engineering lead | Developers and tool builders | Platform or R&D budget | Embed real-time generation or video agents into another product | Platform GM or engineering director | Need differentiated video capability without training a proprietary model |
| Enterprises / governed workflows | IT, procurement, or business-unit sponsor | Cross-functional team or internal creators | Contracted software / transformation budget | Governed workflows, team workspaces, automation, and compliance | CIO, COO, or BU owner | Need governance, workflow integration, and production reliability |
Buyer, user, and payer separate quickly in this market. The end creator is often not the economic decision-maker once workflow governance, branded content, or API embedding enters the picture.
[CM019, CM020, CM021, CM022, CM023, CM024]A flow from casual experimentation toward governed platform usage, showing where budget ownership changes.
Real buyers can skip steps or operate in parallel, but the figure captures the common budget progression from creator experimentation to governed deployment.
[CM019, CM022, CM024, CM025, CM027, CM029]2.4 Growth drivers are expanding the category from clip generation into broader production workflows
The strongest growth drivers are clear and fairly well corroborated. TBRC explicitly names the expansion of social media and digital platforms as a demand driver, and both market publishers point to automated editing, personalized marketing, collaboration, and cloud workflows as tailwinds. Official product surfaces suggest why. PixVerse now markets a world engine with long-horizon generation, real-time 1080p, and production-ready APIs; Runway pushes general world models and interactive video characters; Pika pushes agents and workflow automation. These are not just prettier clip generators. They are attempts to move video AI into repeatable workflows, interactive experiences, and software budgets that can scale beyond novelty. Pricing design also helps adoption. PixVerse exposes low-dollar, credits-based creation economics, while Runway offers free entry, prosumer subscriptions, and enterprise custom packaging. That mix supports a classic land-and-expand path: creators can test cheaply, teams can formalize workflows, and enterprises can negotiate larger deployments once the output is good enough and operationally reliable.[CM030, CM031, CM032, CM033, CM034, CM035]
| Driver / constraint | Direction | Timing | Implication | Diligence ask |
|---|---|---|---|---|
| Social and digital-platform expansion | positive | current | Expands demand for fast, repeatable short-form video creation | Quantify which channels actually convert casual usage into paid accounts or recurring enterprise demand. |
| Automated editing, collaboration, and personalization | positive | current | Moves value from novelty clips into recurring workflow software | Test whether workflow features improve retention and willingness to pay versus pure generation quality. |
| World models, agents, and real-time APIs | positive | emerging | Create new developer and interactive-media budgets beyond creator subscriptions | Ask how much current revenue already comes from API or production-platform usage. |
| Low-friction self-serve pricing | positive | current | Supports land-and-expand adoption from creators into teams | Measure paid conversion, ARPU, and the share of users who later upgrade to team or enterprise plans. |
| Compute cost and advanced-chip access | negative | current | Can cap margins and slow iteration for China-linked vendors | Review cloud/GPU commitments, model serving cost per minute, and hardware dependency by product line. |
| Labeling, governance, and filing requirements in China | negative | current | Turn trust and compliance into recurring operational cost and launch friction | Request filing status, moderation process, and average lead time for compliance review. |
| Platform continuity and reliability risk | negative | current | Buyers may hesitate if leading vendors can change or discontinue products | Check SLA terms, export options, data portability, and API versioning commitments. |
| Crowded substitute set and price competition | negative | current | Competition can compress value capture even if demand grows quickly | Map win reasons versus Runway, Pika, Vidu, Kling, and other substitutes by segment. |
The market has real growth tailwinds, but each positive row has an operational qualifier. In this category, adoption often scales faster than durable revenue capture.
[CM030, CM031, CM032, CM033, CM034, CM035]Indexed funnel showing where public evidence suggests friction accumulates between first trial and scaled deployment.
Values are relative index points with creator trial = 100. They are not measured conversion rates; they simply encode where constraints stack up in the public evidence.
[CM037, CM038, CM039, CM040, CM041, CM042]2.5 Constraints: compute, regulation, trust, and competition all limit how much value any one vendor can capture
The constraint stack is just as important as the growth stack. On the trust and regulation side, China's 2023 generative AI measures apply to services that generate text, images, audio, and video for the public, while the 2025 labeling rules require AI-generated online content to be marked. That means speed to market is conditioned by filing, governance, moderation, and labeling obligations, not only by model quality. On the cost and supply side, BIS says advanced-computing exports to China-linked entities still need licenses even when the entity sits outside China, and outside legal commentary confirms that requirement remained in force in 2026. Compute availability therefore remains a real bottleneck for China-linked vendors. Reliability and platform continuity also remain unresolved. a16z says AI video only recently became fairly dependable for short clips, and OpenAI's Sora discontinuation shows that even category leaders can change product direction abruptly. Finally, competition is intense: official sites and benchmarks show a wide field of credible substitutes, which means not every usage surge will translate into durable revenue or margin capture for AIsphere.[CM038, CM039, CM040, CM041, CM042, CM043]
2.6 Exhibits
03Competitors
3.1 Landscape: direct peers, substitutes, internal build, and likely entrants
AIsphere's competitor set is unusually broad because buyers can solve the same job in several ways. The narrowest direct-peer bucket is creator-facing AI video generation: Runway, OpenAI Sora, Kling, Vidu, Hailuo, Wan, Jimeng/Seedance, and Pika all market some combination of text-to-video, image-to-video, audio, or controllable cinematic workflows. Those are the cleanest substitutes when a creator, studio, or prosumer wants a packaged video-generation product rather than a general chatbot. Benchmark sources further show that Chinese labs and apps now dominate much of the quality frontier: Artificial Analysis currently places ByteDance Seedance above Kling, Vidu, Wan, and PixVerse on multiple leaderboards, while Hailuo, Grok, LTX, and Veo keep adding more alternatives at different price points. That means PixVerse is competing inside a dense and rapidly iterating global field rather than a niche category it can name by itself. The market boundary is even wider once substitutes are included. Internal build is credible because the benchmark field already includes open-weight models such as LTX-2.x and Wan variants, which gives sophisticated teams a self-hosted option instead of a subscription product. Model-routing platforms are another substitute: Runway now bundles third-party models like Kling, Seedance, and Veo inside its own paid plans, while Pika's MCP and agent positioning openly promise access to “all the models.” Finally, likely entrants do not have to launch a standalone video app to matter. Generalist labs such as OpenAI and Moonshot can pull developers into broader agent or assistant ecosystems, while OS-level or distribution incumbents can win simply by becoming the default surface where creation already happens. For AIsphere, that makes the real question less “who else makes AI video?” and more “which surfaces own the user, the workflow, and the routing layer around AI video?”[CP013, CP014, CP015, CP020, CP021, CP022]
| Competitor / alternative | Category | Scale or strategic signal | Target segment | Differentiation | Limitation |
|---|---|---|---|---|---|
| AIsphere / PixVerse | Direct peer | PixVerse positions itself as an enterprise-ready AI media platform with APIs and global creator reach | Creators, prosumers, teams, and API builders | Fast iteration, strong price positioning, and China/global bridge | Must prove retention and workflow ownership, not just model quality |
| Runway | Global direct peer / aggregator | $315M Series E at $5.3B valuation; world-model platform ambitions | Creators, studios, agencies, enterprise teams | Multi-model packaging, branded tooling, and enterprise GTM | Benchmark edge can still be routed across many model providers |
| OpenAI Sora | Global direct peer / likely entrant | Previewed as world-simulation product, then sunset the standalone experience in 2026 | Developers and creators already inside OpenAI ecosystem | OpenAI brand, safety tooling, and adjacent platform reach | Standalone durability looked weaker than the headline suggested |
| Kling | Chinese direct peer | Kling 3.0 and 3.0 Omni ranked near the top of AA leaderboards | Prosumers and premium creator workflows | Strong cinematic control, long-form storyboards, native audio | Public price points are relatively high versus PixVerse and Vidu |
| Vidu | Chinese direct peer | AA-ranked quality plus reference-video workflow positioning | Fast-turn social, ad, and storytelling creators | Reference-video workflow and competitive benchmark pricing | Fetched public governance material is relatively light |
| Hailuo | Chinese direct peer | a16z cites Hailuo as a Chinese video product exported globally | Consumer creators | Brand visibility and China-led iteration speed | Fetched landing page exposes little pricing or compliance detail |
| Wan | Chinese direct peer / internal-build substitute | AA benchmark presence across model variants and open-style field comparison | Developers and creators mixing closed and self-hosted flows | Strong benchmark visibility with open-style substitute pressure around the family | Public landing page is thin; enterprise packaging is unclear in retained sources |
| Jimeng / Seedance | Chinese direct peer / likely entrant | Seedance leads retained AA leaderboards; Jimeng exposes ByteDance creator workflow DNA | Chinese creators and ByteDance-adjacent users | Leaderboard-leading quality plus community and Chinese prompt fit | ByteDance can route value through broader ecosystems rather than a standalone vendor |
| Pika | Global direct peer / routing layer | Agent and MCP framing promises access to “all the models” | Creators who want effects plus AI-agent workflows | Can aggregate models instead of betting on one frontier model | Public fetched pricing is thin and positioning is still evolving |
| Internal build / open-weight stack | Substitute | LTX open-weight models and benchmarked open-style alternatives are already in buyer comparison sets | Studios, agencies, and technical teams | Lowest routing cost and highest control | Requires ops talent and may trail premium apps on polish |
| Generalist entrants (Moonshot, Veo, Grok) | Likely entrants / adjacent substitutes | Moonshot has $20B valuation; Veo and Grok appear near the frontier in AA rankings | Developers who want broad AI workspaces, not just video tools | Can bundle video with coding, search, reasoning, or platform defaults | Video may be one feature among many, pressuring pure-play margins |
Rows intentionally mix direct apps, substitutes, and adjacent entrants because buyers can solve the same job through packaged apps, routed platforms, or self-hosted stacks.
[CP001, CP002, CP006, CP007, CP008, CP009]Ordinal map of openness / routability versus distribution / trust power across the main retained alternatives.
Scores are evidence-backed ordinal judgments derived from retained pricing pages, product pages, benchmark summaries, and regulatory documentation rather than disclosed vendor metrics.
[CP020, CP021, CP031, CP033, CP035, CP040]3.2 Capability and pricing: quality is crowded and packaging is becoming the weapon
Capability quality is no longer enough to stand out on its own. Artificial Analysis compares quality, speed, and price across a wide model field and shows that the top of the leaderboard is crowded: Seedance currently leads both text-to-video and image-to-video arenas, while Kling, Vidu, Wan, Grok, Veo, and PixVerse all appear within a relatively tight performance band. That compresses any claim that PixVerse owns a uniquely superior capability stack. Even when PixVerse performs well, buyers can benchmark it directly against several close substitutes on the same independent scoreboard, which reduces room for opaque value-based pricing. AIsphere's official materials still make a credible product case — enterprise-ready APIs, near-real-time generation, and aggressive price positioning — but the independent evidence says the category has already become compare-and-switch friendly. Pricing and packaging reinforce that pressure. PixVerse's public docs say $1 buys five V6 720p 5-second no-audio videos on the starter pack, while Runway publishes free, Standard, Pro, and Max tiers with fixed monthly credits and increasingly broad model access. Artificial Analysis adds API-level comparables for direct peers: Vidu Q3 Pro is listed at $9.60 per minute, Seedance 2.0 at $9.07, Wan 2.7 at $16.90, and several Kling variants materially above PixVerse's own claimed rate. At the low end, open-weight LTX models show that developers can buy or self-host much cheaper video generation if they accept weaker quality. The result is a barbell market: premium branded apps compete on polish, community, and workflow control, while open or aggregated stacks cap how much margin any single video model can sustain. That is good news for category growth but bad news for a durable standalone moat.[CP003, CP012, CP014, CP015, CP016, CP017]
| Capability | PixVerse | Runway | Sora | Kling | Vidu | Jimeng / Seedance | Pika | Internal build / open weights |
|---|---|---|---|---|---|---|---|---|
| Text-to-video quality signal | Strong | Strong | Strong but unstable product path | Strong | Strong | Strongest in retained leaderboards | Moderate | Moderate |
| Image-to-video and controllability | Strong | Strong | Moderate in retained sources | Strong | Strong | Strong | Moderate | Variable by chosen model |
| Native audio or audio-linked creation | Strong | Strong | Strong | Strong | Unknown in retained surface | Video and image creation visible; audio not emphasized on fetched page | Moderate | Variable / model dependent |
| Long-form consistency / storyboard control | Strong | Strong | Moderate | Strong | Moderate | Moderate | Moderate | Variable and more engineering-heavy |
| API / enterprise packaging | Strong | Strongest | Weak in retained fetched set | Unknown | Unknown | Unknown | Moderate | Strong if the buyer can self-operate |
| Consumer community / brand surface | Strong | Strong | Strong brand, weak standalone durability | Strong | Moderate | Strong in China creator context | Strong | Weak |
| Model routing / multi-homing support | Weak | Strong | Weak | Weak | Weak | Weak | Strongest | Strong |
| Public trust / compliance documentation | Moderate | Strong | Strong | Moderate | Weak-moderate | Moderate | Moderate | Buyer-owned |
Cells are evidence-backed qualitative judgments from retained official pages, benchmark summaries, and legal/regulatory sources. “Weak” or “unknown” means the fetched set did not prove a stronger claim, not that the competitor necessarily lacks the capability.
[CP003, CP004, CP005, CP007, CP008, CP011]| Provider / alternative | Public price or unit signal | Packaging model | Included capabilities | Unknowns / implication |
|---|---|---|---|---|
| PixVerse | $1 = 5 V6 720p 5s no-audio videos; enterprise memberships from $1,500 to $6,000 / month | Credits plus membership and enterprise tiers | Short-form generation, API, team / business packs | Official pricing is legible, but realized enterprise pricing is still unknown |
| Runway | Free tier plus Standard $12, Pro $28, Max $76 billed annually | Credits per month plus enterprise sales | Runway models plus third-party models like Kling, Seedance, Veo, and more | Packaging power is strong because routing layer owns the subscription |
| Kling 3.0 | $20.16 / min for 1080p Pro; $15.12 / min for 720p Standard in AA benchmark view | Model-level API pricing in benchmark comparisons | High-end video generation, Omni variants, native audio | Premium quality comes with meaningfully higher public unit economics |
| Vidu Q3 Pro | $9.60 / min in AA benchmark view | Model-level API pricing in benchmark comparisons | Text, image, and reference-video workflow | Looks more price-competitive than Kling while staying near PixVerse on quality |
| Seedance 2.0 720p | $9.07 / min in AA benchmark view | Model-level API pricing in benchmark comparisons | Category-leading text-to-video and image-to-video quality | If the best benchmark quality is also price-competitive, margin room compresses for everyone else |
| Wan 2.7 | $16.90 / min in AA benchmark view | Model-level benchmark pricing; public landing page is thin | Competitive image/video quality and open-style substitute pressure around the family | Benchmarked presence is real, but public packaging transparency is limited |
| Pika | No clean public price card in retained fetched home page | App, experiments, agent, and MCP surface | Effects, agent workflows, and multi-model access | Routing convenience may matter more than transparent unit pricing |
| Internal build / LTX-2.3 Fast | $2.40 / min (AA benchmark view) | Open-weight or self-hosted route | Lower-cost self-managed video generation | Cheapest retained option caps what premium apps can charge for commodity use cases |
This table compares the best public economics retained in the source set; not every competitor exposes a clean subscription or API card, so benchmark $/min and official credit pricing are mixed intentionally and labeled as such.
[CP003, CP014, CP015, CP016, CP030, CP031]A readiness lens that combines benchmark strength, pricing clarity, compliance fit, and routing flexibility.
Labels such as strong, moderate, or weak are evidence-backed synthesis scores using the retained source set, not vendor-provided metrics.
[CP012, CP014, CP015, CP017, CP025, CP026]3.3 Distribution, trust, and switching costs: the control plane is moving above the model
Distribution and trust are where the asymmetry becomes most important. Runway is no longer just a model vendor; it is building a world-model platform and already uses pricing to position itself as a multi-model gateway. Pika is doing something similar through agents and MCP, and a16z's Top 100 report argues that many persistent consumer winners either route to third-party models or succeed without owning the best frontier model. That is strategically important for AIsphere: even if PixVerse keeps pace on quality, value can migrate upward to the routing layer or sideways to the platform that already has the user relationship. The same report says Chinese video products such as Hailuo and Kling have exported globally, while app stores are cracking down on copycat surfaces. That favors products with a real brand and community, but it also means new consumer leaders can emerge without owning a unique underlying model. Trust and regulatory posture add another selection filter. China-facing vendors already operate under the 2023 Interim Measures for generative AI services and the 2025 labeling regime that requires visible and metadata-based identification of AI-generated content. Those rules create operational burdens around labeling, logging, export/download controls, and platform review. U.S. and EU-facing enterprise buyers have a different lens: NIST's AI RMF, the EU AI Act, and Article 53-style GPAI obligations push toward documentation, copyright handling, training-data summaries, and identifiable generated content. In other words, product quality gets a vendor shortlisted, but governance process can determine who survives procurement. The public record is mixed here: OpenAI and Runway discuss safety or product limitations in detail, while Hailuo and Wan expose far less public governance detail on their fetched surfaces. If AIsphere wants to sell deeper into enterprise or regulated creative workflows, its trust posture has to become as legible as its model demos.[CP020, CP021, CP023, CP024, CP025, CP026]
Compact signals showing why competitive durability now depends on more than model quality.
KPI values mix benchmark metrics, public rule effective dates, and product-status facts because the goal is competitive-readiness synthesis rather than a single numeric dashboard.
[CP006, CP014, CP015, CP024, CP029, CP035]3.4 Moat durability: adverse evidence points to commoditization unless PixVerse owns workflow and compliance
The adverse competitor evidence is strong enough to treat commoditization as a base-case risk rather than a tail risk. OpenAI's Sora is the clearest warning sign: the company previewed a world-simulation narrative, deployed a limited 20-second version with acknowledged physics weaknesses and safety overlays, and then discontinued the standalone web and app experience in April 2026. That sequence shows how quickly a headline entrant can re-prioritize distribution or fold a product into a broader platform. The same lesson appears from the opposite direction in China. Moonshot raised roughly $2 billion at a $20 billion valuation and reportedly passed $200 million of ARR, despite not being a pure-play video app. Capital is flowing to generalist labs and agent ecosystems that can absorb video as one feature among many. If buyers increasingly want one AI workspace that can code, search, reason, and generate media, standalone video leaders face a harder upsell. AIsphere still has a plausible path, but it is narrower than raw benchmark performance suggests. PixVerse can remain competitive if it keeps three things true at once: first, independent quality stays in the first tier; second, official pricing keeps the product cheaper or simpler than premium Western peers; and third, the company wins sticky workflow real estate through templates, APIs, teams, or geographic compliance fit. What would weaken the story is any evidence that users are simply shopping among near-equal models or using aggregators like Runway and Pika as their control plane. In that world, PixVerse would still matter as a strong model and app, but the margin would accrue elsewhere. The diligence burden is therefore commercial, not just technical: AIsphere must prove retention, win-loss reasons, and enterprise contract stickiness before investors should underwrite a durable competitive moat.[CP006, CP018, CP019, CP035, CP036, CP037]
| Moat claim or dependency | Competitive threat | Severity | Evidence | Mitigation / diligence ask |
|---|---|---|---|---|
| PixVerse can win on raw model quality | Seedance, Kling, Vidu, Wan, and Veo keep quality clustered within a benchmarked field | High | Artificial Analysis leaderboards show several nearby substitutes and a non-PixVerse leader | Request normalized win-rate, retention, and output-preference data for paying cohorts, not only benchmark screenshots |
| PixVerse can price above peers | Runway, Seedance, Vidu, and open-weight LTX set visible price anchors | High | Official PixVerse and Runway pricing plus AA $/min comparisons | Map realized ASP, discounting, and enterprise price floors versus the top five alternatives |
| Standalone app distribution will remain enough | Aggregators and routing layers can own the subscription while swapping the underlying model | High | Runway bundles third-party models and Pika promises access to “all the models” | Measure how often customers multi-home and whether PixVerse remains the default generation surface over time |
| China and enterprise compliance will be a differentiator | Rules create burden, but better-documented rivals can turn compliance into a sales advantage | Medium-high | China labeling rules, EU GPAI obligations, and NIST trust expectations all raise process requirements | Audit visible governance artifacts, labeling workflows, copyright position, and customer-ready trust documentation |
| China-linked supply and scaling risk is manageable | BIS export-control diligence can still complicate advanced-computing access for China-linked entities | Medium | BIS homepage and GT guidance confirm continuing license requirements | Review compute counterparties, geography of access, and backup capacity plans under tighter export enforcement |
| Generalist labs are not a near-term threat | Moonshot, Veo, Grok, and future assistant ecosystems can absorb video into broader AI workspaces | Medium-high | Moonshot funding scale and benchmark entrants from Google/xAI | Track whether enterprise buyers increasingly prefer all-in-one AI suites over single-purpose video apps |
Severity rates the risk to AIsphere’s durable competitive position, not the attractiveness of AI video demand overall. The main issue is whether value stays with PixVerse or migrates to the routing, OS, or generalist-platform layer.
[CP018, CP019, CP028, CP031, CP035, CP036]3.5 Exhibits
04Financials
4.1 Pricing and revenue surfaces: list pricing exists, realized economics do not
Unlike many private AI startups, AIsphere does expose a visible commercial surface. PixVerse runs a public platform site, an official pricing document, consumer app flows, and 2026 product updates that describe team billing, pooled credits, API access, and partner programs. The strongest official pricing fact is simple and useful: the docs say $1 equals five V6 videos at 720p, five seconds, and no audio on the Starter pack. The same page meters usage by model, resolution, duration, audio, and motion mode, and it also shows larger credit packs and higher-tier plans. That is enough to conclude that AIsphere has moved beyond pure hype into a real credit economy. It is not enough to conclude what investors ultimately care about. Public materials still do not reveal realized enterprise pricing, discounting, refunds, conversion from free to paid, or segment revenue mix between consumer subscriptions, prepaid credits, API usage, and negotiated contracts. The fetched record therefore proves monetization intent and some list pricing, but not revenue quality.[CI001, CI002, CI003, CI004, CI005, CI006]
| stream | mechanism | unit | current value/status | quality | diligence ask |
|---|---|---|---|---|---|
| Consumer credit or subscription spend | Users pay through PixVerse plans and credit balances to generate clips on the consumer surface | Per month / per credit / per clip | Official pricing docs expose credit-based list pricing and monthly plan structures, but actual paid-user conversion is undisclosed | Medium for existence, low for realized yield | Provide paying-user count, conversion rate, refund rate, and net revenue per active payer by plan. |
| Prepaid credit top-ups | Customers buy one-off credit packs for additional generation volume | Per pack / per credit | Official docs show pack denominations from $50 to $5,000, implying wallet-style upsell | Medium for packaging, low for demand quality | Disclose top-up frequency, share of revenue from packs versus subscriptions, and breakage policy. |
| API or developer-platform usage | Developers or product teams integrate generation through the public platform and API surfaces | Per generation / usage contract | Platform pages and docs show API positioning, but realized API price and volume are not public | Medium for surface existence, low for economics | Provide API tariff card, committed-volume terms, and margin by model family. |
| Team workspace billing | Organizations buy pooled credits, admin controls, and shared workspaces through Team Plan | Per seat / pooled credits / org subscription | Official production-platform update confirms consolidated billing and pooled credits; no public rate card for teams was fetched | Medium for feature existence, low for pricing clarity | Provide team-plan seat pricing, overage rules, and average organization spend. |
| Selective R1 partner contracts | Studios, streamers, and tool builders integrate real-time video via gated partner access | Negotiated contract / usage commitment | Official partner-program post says pricing is favorable and grandfathered for early partners, but no public numbers are disclosed | Medium for GTM motion, low for monetization visibility | Provide partner count, average contract value, committed volume, and support burden. |
| Vertical workflow tools and commercial production services | Mini Apps and workflow tooling target ads, marketing, and other production use cases | Per campaign / per workflow / enterprise contract | Official workflow posts show productized commercial tooling, but no public segment revenue is broken out | Low to medium | Disclose whether vertical tools monetize via standalone SKU, usage uplift, or enterprise bundle expansion. |
Rows separate publicly visible monetization surfaces from still-undisclosed realization data. Presence of a product surface does not prove its revenue contribution.
[CI001, CI004, CI005, CI006, CI007, CI008]| surface | price / unit | list vs realized pricing | discounts / unknowns | source |
|---|---|---|---|---|
| Starter-pack V6 list-price anchor | $1 = 5 videos (V6, 720p, 5s, no audio) | Clear official list-pricing anchor | Unknown whether enterprise buyers receive materially different effective rates | Official pricing docs |
| Resolution, duration, audio, and motion billing | Credits vary by model parameters; fast motion doubles credit consumption | Clear list-pricing rule | Unknown how often customers choose premium settings or whether bundles soften pricing | Official pricing docs |
| Prepaid credit packs | $50, $500, $2,000, and $5,000 denominations shown on the fetched page | Visible list pricing | Unknown credits-per-dollar after promotions, enterprise rebates, or annual commitments | Official pricing docs |
| Scale plan | Displayed as $1,500 with 239,230 monthly credits and 5,316 generated videos on the fetched text extraction | Visible list pricing, though page extraction is imperfect | Entry-tier layout is partially garbled in the fetched text, so lower tiers should be rechecked live before quoting externally | Official pricing docs |
| Business plan | Displayed as $6,000 with 1,069,500 monthly credits and 23,766 generated videos on the fetched text extraction | Visible list pricing, though page extraction is imperfect | Unknown contract length, user cap, support entitlements, and whether the displayed economics reflect a specific model baseline | Official pricing docs |
| Team and partner contracts | Quote-based or selectively priced; official posts mention consolidated billing and grandfathered partner pricing without public rates | Likely mostly realized pricing rather than open list pricing | No public seat minimums, discount bands, support markups, or committed-volume terms were fetched | Production-platform and R1 partner-program updates |
Only clearly legible official numbers are reproduced. The pricing-doc extraction is partially noisy, so this table uses the visible anchors while explicitly flagging ambiguity where present.
[CI002, CI003, CI004, CI005, CI006, CI007]AIsphere’s public revenue path appears to run from consumer creation and developer access into credits, teams, API usage, and negotiated partner contracts, but realized revenue and gross profit remain opaque.
This is a qualitative monetization bridge built from official product and workflow surfaces plus repeated 2026 revenue and funding reporting; it is not a disclosed segment revenue waterfall.
[CI001, CI004, CI005, CI006, CI008, CI011]4.2 GTM proxies and revenue quality: the funnel is broad, but contract quality is opaque
The public go-to-market picture is broader than a single consumer app. Google Play copy, app-download flows, and A16Z’s consumer ranking still point to a creator-led top funnel, while the production-platform, Canvas, and R1 partner-program updates show AIsphere trying to convert that attention into teams, developers, studios, streaming platforms, and tool builders. Team Plan features such as consolidated billing and pooled credits are classic organizational upsell mechanics, and the partner program is explicitly selective, with engineering-capacity requirements and roadmap access that look closer to enterprise sales than to self-serve checkout. The traction proxies are meaningful but still uneven in quality. March 2026 coverage repeatedly echoed ARR above $40 million, more than 100 million users, and more than 16 million MAU; PR and official posts add 175-plus countries and two billion generated videos. Those numbers make the company look commercially real, but they do not answer how many customers actually pay, how often they renew, what ACVs look like, or whether usage is durable enough to support software-like retention.[CI008, CI009, CI010, CI011, CI013, CI014]
| metric | value / null | confidence | why it matters | diligence ask |
|---|---|---|---|---|
| Official starter-pack price anchor | $0.20 per V6 720p 5s no-audio video (derived from $1 = 5 videos) | Medium | Gives the clearest public unit-price floor, but not the realized mix or enterprise rate card | Provide realized ASP by consumer plan, enterprise contract, and API workload. |
| Public ARR | >$40M (reported) | Medium | Shows the business is likely monetizing at meaningful scale, but not how durable or profitable that revenue is | Provide monthly revenue bridge, deferred revenue, and auditor-reviewed recognition policy. |
| Public user base | >100M users (reported / claimed) | Medium | Large funnel size helps explain investor appetite and freemium-style monetization potential | Break users into registered, active, paying, and retained cohorts by geography. |
| Public monthly active users | >16M MAU (reported) | Medium | MAU is a useful engagement proxy, but not a substitute for paying accounts or revenue retention | Provide MAU to payer conversion, payer churn, and share of MAU on paid plans. |
| Official platform scale claim | 100M+ users, 175+ countries, 2B+ generated videos (company-claimed) | Medium | High usage can help data flywheels and distribution, but it may also raise compute and moderation costs | Disclose paid vs unpaid generation share and support or moderation cost per active user. |
| Founder-reported profitability marker | Subscription revenues cover costs | Low | Potentially important if true, but the claim is not audited and does not specify whether it excludes R&D or stock comp | Provide GAAP and non-GAAP contribution margin by major product line. |
| Gross margin / NRR / enterprise customer count | Low | These are the core quality metrics needed to judge whether AIsphere behaves like a durable software business | Provide gross margin, NRR, top-customer count, large-account thresholds, and cohort retention. |
This table mixes public traction proxies with intentional nulls where the public record stops. Nulls mark missing underwriting inputs, not zero values.
[CI002, CI011, CI012, CI014, CI015, CI021]Public evidence is strongest at top-of-funnel adoption and visible credit pricing, weaker at contract economics, and weakest at retention and margin quality.
The bridge intentionally stops where public disclosure stops. Downstream nodes are diligence questions, not verified company metrics.
[CI011, CI015, CI018, CI021, CI022, CI036]4.3 Cost structure and capital intensity: richer workloads likely pull the business up the cost curve
AIsphere’s own materials hint at why the margin path is still the core financial question. Credit pricing rises with resolution, duration, audio, and faster generation, which means the customer-facing tariff already reflects variable resource intensity. The product roadmap then moves further toward expensive workloads: real-time 720p API access for partners, continuous shared worlds, multi-user sessions, and official claims of real-time 1080p output. None of that proves weak unit economics, but it does show that the highest-value use cases are probably also the most compute-hungry. Public-company filings are helpful here as analogies, not as substitutes for company data. Datadog discloses cloud-hosting costs in cost of revenue, Cloudflare discloses network and equipment-serving costs, Snowflake warns about minimum cloud commitments, and NVIDIA frames cost per token as a live infrastructure battle. Against that backdrop, AIsphere’s lack of disclosed gross margin, compute commitments, or working-capital profile is material. The economics may improve with better hardware and routing, but public evidence does not yet prove they already have.[CI003, CI007, CI015, CI021, CI022, CI023]
The cost stack likely rises from richer product workloads into cloud, network, support, and commitment pressure, while the latest round merely buffers rather than resolves the runway question.
This figure combines company product signals with public-company filing context to map likely cash-flow pressure points; it is not a disclosed AIsphere budget or burn waterfall.
[CI021, CI022, CI023, CI024, CI025, CI026]4.4 Capital adequacy and financing dependency: fresh capital lowers near-term risk but does not clear runway
AIsphere is not presenting like a capital-starved pre-product startup. Multiple March 2026 reports independently place the latest round at $300 million, describe it as a record financing for China’s AI-video segment, and say the proceeds are for R&D, new-business exploration, and global expansion. AI Insider adds the now-familiar unicorn framing, while KrASIA says the founder believes subscription revenue already covers costs. Those signals matter because they lower immediate survivability risk and suggest investors are comfortable funding world-model ambitions. But the underwriting ceiling is still low. No fetched source discloses cash on hand, monthly burn, runway, debt, cloud commitments, or the exact next-round trigger. Even the strongest positive evidence remains directional rather than balance-sheet specific. Runway’s February 2026 $315 million round at a $5.3 billion valuation is useful context: frontier AI-video peers can still require very large financings even after proving demand. AIsphere’s latest raise is therefore a buffer, not proof that the company has escaped financing dependency.[CI010, CI011, CI012, CI016, CI020, CI032]
| item | public value / status | confidence | implication | diligence ask |
|---|---|---|---|---|
| Latest disclosed financing | $300M Series C in March 2026 | Medium | Provides a meaningful near-term capital buffer for R&D and expansion | Obtain close memo, cash received date, and post-money ownership effects. |
| Stated use of funds | R&D, new-business exploration, and global expansion | Medium | Shows proceeds are intended for growth rather than only balance-sheet repair | Request 12- to 24-month budget by compute, personnel, sales, and international infrastructure. |
| Investor breadth | 20+ institutions reported; CDH-led round with domestic and overseas investors | Medium | Broad participation lowers single-investor risk and may support future financing access | Provide board rights, pro-rata obligations, and any strategic-commercial side letters. |
| Founder-reported operating coverage | KrASIA says subscription revenues cover costs | Low | Helpful directional signal, but insufficient to infer full-company profitability or cash generation | Provide audited income statement and definition of “costs” used in the founder statement. |
| Cash on hand | Low | Without cash, investors cannot estimate solvency or strategic flexibility | Provide latest unrestricted cash, restricted cash, and short-term investments. | |
| Monthly burn and runway | Low | The single largest missing input for financing dependency | Provide current burn, scenario runway, and monthly compute spend by workload. | |
| Debt, leases, and cloud commitments | Low | Commitments can make a seemingly asset-light AI company meaningfully more fixed-cost than it appears | Disclose debt, leases, minimum cloud commitments, and hardware-financing obligations. | |
| Next-round trigger | Low | Investors need to know whether growth, model training, or infrastructure scale will force another raise soon | Provide the internal trigger metrics for raising again, including user, revenue, and compute thresholds. |
Public evidence proves fundraising access, not capital adequacy. The missing cash, burn, and commitment rows are the real diligence blockers.
[CI010, CI012, CI016, CI020, CI032, CI037]The strongest public numeric anchors are financing and reported ARR, while the larger context comes from peer financings and public-company backlog markers rather than AIsphere’s own balance-sheet disclosure.
All values are shown in USD millions. Peer items are context for capital intensity and disclosure standards, not implied valuations or revenue for AIsphere.
[CI010, CI011, CI027, CI032, CI037]4.5 Financial verdict and diligence blockers: monetizing business, still not a fully underwritable one
The financial verdict is mixed but clear. Positive side: AIsphere has visible list pricing, a broad consumer funnel, organizational monetization features, repeated ARR and scale claims, and a very recent $300 million financing that should buy execution time. Negative side: the evidence still stops before the variables that determine revenue quality and margin durability. Public materials do not show customer count, ACV distribution, cohort retention, backlog, deferred revenue, contracted revenue, gross margin, operating cash flow, cash balance, debt, or concentration by geography and customer type. Public comparables make the omission more obvious because they routinely disclose exactly those markers. That does not mean AIsphere is weak; it means investors cannot yet distinguish a strong software business from a fast-growing but compute-heavy, discount-heavy, or services-assisted business. The correct stance for this chapter is therefore cautious: revenue is likely real, pricing is definitely real, but revenue quality remains medium-to-low confidence until management produces board-grade financials and contract-level cohort evidence.[CI027, CI028, CI029, CI030, CI031, CI033]
| missing private metric | impact on judgment | exact diligence path |
|---|---|---|
| Revenue mix by consumer, team, API, and partner contracts | Prevents any clean view of concentration, quality, and dependence on low-value consumer usage | Request monthly revenue bridge by product line and geography with paying-account counts. |
| Realized enterprise pricing and discount bands | Prevents translating visible list prices into actual contract economics | Review top 20 contracts, rate cards, discount approvals, and overage schedules. |
| Gross margin and compute COGS | Prevents judging whether real-time AI video is scaling profitably or only growing usage | Request model-level serving cost, GPU-hours, bandwidth, storage, moderation, and support cost allocation. |
| Customer concentration, ACV, and retention | Prevents knowing whether ARR comes from durable software accounts or a small volatile account set | Request top-customer concentration, ACV buckets, cohort churn, NRR, and renewal schedules. |
| Deferred revenue, backlog, or RPO | Prevents comparing AIsphere with public software-style revenue quality markers | Provide deferred-revenue rollforward, signed backlog, and remaining performance obligations. |
| Cash, burn, runway, debt, and cloud commitments | Prevents any serious conclusion on next-round timing or downside resilience | Request current balance sheet, debt schedule, lease obligations, and minimum cloud-commitment contracts. |
These are the minimum public-data gaps that block a clean underwriting case on AIsphere financials as of 2026-07-03.
[CI027, CI028, CI029, CI030, CI034, CI036]4.6 Exhibits
05Product & Technology
5.1 Delivered product: PixVerse now spans consumer creation, collaborative workflow, programmable APIs, and an early world-model layer
The public product definition is much broader than a single prompt box. The consumer-facing surface is visible on app.pixverse.ai, whose navigation now exposes Creation, Agent, Canvas, Mini-Apps, Marketing Hub, and API Platform; the mobile tutorial and Google Play listing show that the same stack is distributed through official iOS and Android apps with cloud-sync behavior rather than as a separate stripped-down companion. That matters because it turns PixVerse into a cross-surface workflow: a solo creator can start with a template or text prompt on mobile, a team can move into shared workspaces and centralized assets, and a developer can escalate the same generation workflow into API or CLI automation. The 2026 production-platform update makes that layering explicit by adding Team Plan permissions, pooled billing, and Mini Apps, while Canvas adds a node-based board for scripts, references, storyboards, batches, and finals. In workflow terms, AIsphere is delivering a creator operating system for AI video, not only a model endpoint. The strategic implication is positive: workflow ownership and surface breadth make switching harder than a raw leaderboard comparison does. The caveat is that public proof is strongest for packaging and feature breadth, and much thinner for how much revenue or enterprise retention each layer is already carrying.[CE001, CE002, CE003, CE004, CE005, CE006]
| Module / surface | Primary user | Status / maturity | Differentiation | Diligence gap |
|---|---|---|---|---|
| Consumer creation app + web | Solo creators and prosumers | Mature public surface | Fast multi-mode creation across text, image, transition, extension, references, and templates | Public materials do not split paid conversion or retention by web vs app cohort |
| Canvas visual workspace | Creators, agencies, and internal teams | New but clearly productized | Node-based board keeps scripts, references, batches, and finals in one traceable workspace | No public usage or adoption metrics by team size were located |
| Team Plan + shared asset library | Collaborative production teams | Commercially announced | Shared workspaces, role-based permissions, centralized assets, and pooled billing move PixVerse beyond single-user tooling | Seat pricing, admin controls, and audit-log depth are not public |
| Mini Apps / Ad Master | Marketers and vertical operators | Early product extension | Purpose-built workflow shells reduce distance from brief to deliverable in specific use cases | Only the first mini app is described in detail; broader module roadmap is still sparse |
| PixVerse Platform API + CLI path | Developers, studios, and enterprises | Active but partly gated | Programmable generation with priced credits and automation hooks | Public docs remain pricing-heavy; full API schema, SLA, and auth detail are not visible |
| V6 / C1 proprietary video models | High-end video creators and production teams | Core commercial engine | Proprietary model stack with 1080p output, audio, camera control, and per-second pricing | Independent proof supports first-tier quality, but not uncontested category leadership |
| R1 real-time world model | Studios, platform builders, interactive-experience developers | Emerging / selective access | Persistent interactive world generation pushes PixVerse beyond clip synthesis | General-availability timing, throughput, and reliability remain undisclosed |
| IP / partner workflow layer | Rights holders, game studios, brand programs | Experimental but distinctive | KAGAMI Gate licensing and Tripo look-dev create workflow hooks competitors do not all expose | Current proof is partnership-blog depth rather than long-run production case studies |
Status reflects what is visible on public surfaces as of 2026-07-03: mature means broadly shipped, announced means commercial surface exists, and emerging means partner-gated or still evidence-light.
[CE003, CE005, CE006, CE007, CE009, CE012]| User job | Current workflow | PixVerse solution | Measurable benefit | Limitation |
|---|---|---|---|---|
| Create a short social video from a text prompt or image | Single-purpose mobile editor or cloud clip generator | Consumer app/web with text-to-video, image-to-video, templates, and extension | Fast HD output with one account across web and mobile | Credit economics and retries still shape usability |
| Run a multi-shot brand or ad workflow | Separate prompt tools, folders, spreadsheets, and editors | Canvas plus Mini Apps and Team Plan workflow surfaces | Project state, assets, and variants stay on one board instead of scattered tabs | Public evidence on creative approvals and enterprise admin controls is limited |
| Automate generation inside a product or pipeline | Manual web generation or stitched third-party scripts | API Platform plus claimed CLI support | Programmable generation and transparent per-second/credit pricing | Public docs do not yet expose full SLA, auth, or quota disclosure |
| Prototype an interactive world or live narrative | Game engine plus bespoke assets and logic stack | R1 real-time world model and partner API | Continuous world generation, avatars, synchronized audio, and narrative steering | Selective partner gating means the surface is not broadly self-serve |
| Validate a game asset look before 3D modeling | Static concept art followed by blind modeling | PixVerse cinematic look-dev linked to Tripo Studio | Teams can test lighting, motion, and silhouette before mesh production | The proof is a partner workflow post, not a neutral customer case study |
| Launch licensed fan or brand templates | Unofficial fan content or after-the-fact takedown risk | KAGAMI Gate controlled licensing plus Captain Tsubasa templates | Rights holder terms are applied at creation time rather than after publication | The licensing system is still proof-of-concept and franchise-specific |
| Operate a mobile-first creator workflow | Browser-first tool with weak phone support | Official iOS/Android app plus cloud sync | On-the-go generation and direct social sharing widen distribution | The app remains cloud-backed rather than local, so service quality still depends on backend performance |
Benefits are stated only where the reviewed sources show a concrete workflow change, pricing logic, or product-control difference; they are not audited ROI claims.
[CE004, CE007, CE008, CE009, CE018, CE019]A typical PixVerse workflow now moves from idea capture into organized project state, generation, review, and external publishing or integration.
[CE004, CE007, CE008, CE009, CE010, CE018]Consumer creation and workflow packaging look mature; R1 and public trust disclosures still show earlier-stage characteristics.
Maturity labels are analyst judgments synthesized from public product breadth, access model, and governance disclosure rather than internal rollout metrics.
[CE003, CE005, CE007, CE009, CE018, CE019]5.2 Architecture and operating model: proprietary video foundation models underneath, with R1 pushing toward a persistent multimodal world engine
The public architecture story has two layers. The first is the mature video-generation stack around V6, V5.6, C1, and related creation modes. Official launch material, pricing docs, and the detailed V6 review show a cloud model family that already supports text-to-video, image-to-video, transition, extension, reference-to-video, integrated audio, and 1080p outputs with transparent credit pricing. The second is the newer R1 direction, which PixVerse describes not as a clip generator but as a real-time world model: continuous interactive 1080p video, omni-native multimodal processing, low sampling steps, memory-augmented attention, and updated support for single-photo avatars, persistent sessions, and multi-user shared worlds. That operating model is strategically important because it shifts AIsphere from competing only on short-form clip quality toward an architecture that could support simulations, interactive entertainment, and live environments. The partner-program packaging, however, shows the immaturity of this layer: the most novel R1 capability is still selectively gated, early-access infrastructure rather than a broad self-serve production API. In other words, the proprietary video foundation-model layer looks commercial today; the world-model layer looks technologically ambitious but still partially pre-general-availability.[CE010, CE011, CE012, CE013, CE014, CE015]
| Layer / component | Role | Dependency | Risk |
|---|---|---|---|
| Consumer creation shell | Hosts creation modes, templates, references, and creator UX | Web app, mobile apps, account sync, and cloud generation backend | High feature breadth can still mask weak enterprise observability or governance disclosure |
| Workflow orchestration layer | Stores project state, nodes, references, storyboards, batches, and team assets | Canvas, Team Plan, shared libraries, and permission model | Operational complexity rises as PixVerse moves from a clip tool to a collaborative system of record |
| Proprietary video foundation models | Generate core V6/C1 clip outputs with camera, audio, and multi-shot behavior | Training data, inference infrastructure, and per-second pricing engine | Independent benchmarks show strong but not dominant quality, so raw-model edge is contestable |
| Audio / scene-control layer | Coordinates speech, music, effects, camera motion, and shot continuity | Integrated audio switches, literal prompting discipline, and multi-shot handling | Brand-accurate product shots, multilingual dialogue, and chaotic action still need human review |
| R1 world-model layer | Creates continuous interactive video worlds instead of discrete finished clips | Omni-native multimodal processing, low-step sampling, memory-augmented attention | Selective-access packaging means real throughput and support characteristics are still under-disclosed |
| API / automation layer | Lets partners and developers script generation or embed it in pipelines | Platform pricing docs, claimed CLI access, and R1 partner program | Public docs emphasize commercial access more than implementation detail or SLA depth |
| Rights / compliance layer | Applies labeling, IP rules, and usage policies at distribution or creation time | China labeling obligations, KAGAMI Gate controls, app-store review, internal moderation | No public trust-center equivalent or provenance standard is described on official surfaces |
| Compute / supply chain layer | Supplies the GPUs and advanced computing needed for training and inference | Export-control environment, vendor relationships, and backend cloud capacity | BIS guidance shows China-linked compute access remains a live operational dependency |
The architecture table mixes software modules, governance layers, and external dependencies because PixVerse’s public operating model is commercial workflow plus cloud service, not only model architecture in the narrow ML sense.
[CE009, CE010, CE012, CE014, CE015, CE016]PixVerse stacks creator UX, workflow orchestration, proprietary generation models, and an emerging real-time world-model layer on top of cloud delivery and compliance controls.
[CE003, CE005, CE009, CE012, CE015, CE018]5.3 Deployment, integration, and differentiation: the moat is workflow ownership, ecosystem hooks, and selective partner distribution more than absolute benchmark leadership
AIsphere’s differentiation is easiest to understand by following deployment surfaces outward. Consumer users enter through templates, reference-image tools, speech and motion controls, and cross-platform app distribution. Teams can then move into Canvas boards, shared asset libraries, and role-based collaboration. Developers can automate through the API platform and, according to company-authored materials, CLI access. Finally, higher-complexity partners can use R1 through a gated program aimed at studios, streaming platforms, and tool builders. The ecosystem posts around Tripo Studio, KAGAMI Gate, Captain Tsubasa, and AI for Good show how AIsphere is trying to embed PixVerse into game asset look-dev, rights-managed IP workflows, branded template ecosystems, and global creator programs. That is a real product strategy, but it does not mean PixVerse is the undisputed technical leader. Artificial Analysis still places V6 in the first tier rather than at the very top, and AppBrain reviews show that some users continue to experience drift, unwanted edits, or credit waste. The result is a balanced product verdict: PixVerse is unusually broad and commercially packaged for an AI-video startup, but its public evidence supports “production platform with strong workflow design” more confidently than it supports “clear category-best model.”[CE020, CE021, CE022, CE024, CE025, CE026]
| Date / stage | Feature / milestone | Status | Implication | Source |
|---|---|---|---|---|
| 2026-01 | R1 launch as real-time AI world model | Released / early access | Established the world-model direction and interactive-1080p positioning | Official launch post |
| 2026-02 | PixVerse V5.6 marketing around independent ranking | Released and promoted | Signals product confidence in blind-test benchmark positioning | Official ranking post + Artificial Analysis |
| 2026-03 | V6 launch with camera control, character performance, multilingual text, multi-shot audio, and CLI integration | Released | Upgrades PixVerse from quick clips toward production-oriented workflows | Official V6 launch |
| 2026-03 | Production-platform expansion with Team Plan, Mini Apps, CLI, and API framing | Released | Broadens buyer from solo creator to teams and developers | Production-platform post |
| 2026-spring | Canvas visual workspace announced | Released | Adds project-state management and batch orchestration around generation | Canvas post |
| 2026-04 | AI for Good summit workshop and film-festival program | Ecosystem milestone | Reinforces responsible/global-creator platform positioning | AI for Good post |
| 2026-06 | R1 720p real-time API and partner program opened | Selective access | Makes the newest world-model surface commercially relevant but still partner-gated | R1 partner post |
| 2026-06 | R1 updates add single-photo avatars, persistent sessions, and multi-user worlds | Current-generation upgrade | Moves R1 closer to collaborative environments rather than demo sessions | R1 updates post |
| 2026-06 to 2026-07 | KAGAMI Gate / Captain Tsubasa rollout and challenge | Proof-of-concept deployment | Shows how PixVerse could ship licensed, governed IP workflows instead of generic fan content only | KAGAMI + Captain Tsubasa posts |
The roadmap table mixes product releases with ecosystem deployments because PixVerse’s product thesis depends on both core-model iteration and the workflow/IP programs wrapped around those models.
[CE005, CE007, CE011, CE015, CE017, CE018]PixVerse depends on cloud compute, regulatory compliance, partner channels, and app-store/community distribution as much as on model quality itself.
[CE021, CE031, CE033, CE034, CE036, CE037]5.4 Trust, compliance, and limitations: regulation is visible, public governance disclosure is still thinner than the product surface
Public trust evidence is mixed. On the positive side, PixVerse is clearly operating inside visible governance constraints: China’s 2023 generative-AI rules apply to public video services, 2025 labeling measures require visible and metadata-based markings for AI-generated content, and the KAGAMI Gate experiment shows the company is testing a permissioned IP-licensing layer rather than relying only on takedowns. The Google Play and AppBrain surfaces also make the mobile permission footprint legible, while the Harris and BIS materials highlight that compliance risk is not hypothetical: content-labeling enforcement, export licensing, and workflow documentation all matter operationally. The weakness is what the company has not publicly shown. Across the reviewed official web, app, blog, and platform surfaces, there is no public trust center, no SOC 2 or ISO 27001 page, no public uptime/status history, and no clear equivalent to the watermarking and provenance disclosures that some frontier peers already publish. That absence does not prove weak internal controls, but it does mean diligence on moderation, abuse handling, watermarking, API SLA, incident response, and GPU-supply resilience still has to move from public-web review into private diligence. For underwriting, that is the main technical risk: product breadth is already public, but enterprise-grade governance and reliability are not.[CE030, CE031, CE032, CE033, CE034, CE035]
| Control / signal | Status | Scope | Gap |
|---|---|---|---|
| China generative-AI service rules | Publicly applicable | Video services provided to the public in China must use lawful data, protect personal information, label certain outputs, and provide stable service | Compliance implementation detail at PixVerse is not publicly documented |
| 2025 China AI-content labeling rules | Publicly applicable and time-bound | Visible labels plus metadata/implicit labels for AI-generated text, image, audio, video, and virtual scenes | Public PixVerse pages do not spell out what labeling path users or APIs actually receive |
| IP-rights control via KAGAMI Gate | Visible proof-of-concept | Rights-managed template creation for Captain Tsubasa collaboration | The framework is promising but not yet proven across multiple major franchises |
| Mobile permission and privacy footprint | Visible through app-store and AppBrain surfaces | Camera, microphone, storage, notifications, ad IDs, and network access align with a media-generation app | Users still need better public explanation of data handling, ads, and retention practices |
| Public reliability / trust center surface | Not located on reviewed official pages | Status history, SOC 2, ISO 27001, incident reporting, trust center, or API SLA | Enterprise buyers still need private diligence because the public control plane is thin |
| Public provenance / watermark disclosure | Not located in reviewed PixVerse materials | Whether generated videos carry explicit provenance metadata or default watermarks | Frontier peers disclose more here, so trust differentiation remains unclear |
| User-visible output quality and credit complaints | Mixed | AppBrain reviews praise voice models and free credits but also mention drift and wasted credits | The presence of complaints does not prove systemic failure, but it does show production reliability is not frictionless |
“Not located” means the item was not visible on the reviewed public surfaces; it does not prove the control is absent internally.
[CE031, CE032, CE033, CE034, CE035, CE036]5.5 Exhibits
06Customers
6.1 Buyer, user, and payer segmentation spans consumer creators, teams, and embedded users
PixVerse’s public customer map is broad on users and much narrower on disclosed payers. The most visible users are consumer creators who encounter PixVerse through the mobile app, Google Play, third-party Android stores, Product Hunt, and viral template pages. Those surfaces are optimized for quick social-video creation rather than for procurement-style sales. A second layer sits above them: prosumers, marketers, and agencies that need repeatable campaign workflows, client organization, and better output quality. Official Team Plan and Canvas materials show PixVerse explicitly productizing for that segment with shared workspaces, pooled credits, role-based permissions, and campaign or client organization. Beyond that, the company is also targeting API and embedded users through the R1 partner program, where the buyer is a studio, platform developer, or tool builder rather than a consumer creator. The net result is a credible buyer-user-payer ladder, but public evidence still identifies user surfaces far more clearly than it identifies who pays at meaningful scale.[CU001, CU002, CU005, CU007, CU008, CU009]
| Segment | Buyer / user / payer | Primary use case | Public proof surface | Strategic value | Key gap |
|---|---|---|---|---|---|
| Consumer creators | Individual creator discovers, uses, and sometimes pays through self-serve plans | Quick social clips, photo animation, text-to-video, viral effects | Google Play, app-download page, AppBrain, Uptodown, APKPure | Largest visible top-of-funnel user base | Paid conversion and subscriber count are undisclosed |
| Prosumers / marketers | Individual or small-team payer; creator or marketer is the daily user | Campaign clips, product demos, social-ready brand content | APKPure marketer language, Canvas workflow copy, hot-template pages | Bridges casual creation into repeat commercial use | No segment revenue, ACV, or retention split is public |
| Team / agency workspaces | Admin pays; creators, reviewers, and admins use the product | Shared asset management, campaign organization, pooled credits, approvals | Production-platform Team Plan and Canvas pages | Clearest emerging enterprise-style layer | No named agencies, seat counts, or renewal proof |
| API / embedded partners | Studio, platform developer, or tool builder pays; downstream end user consumes the output | Real-time video generation embedded in products or workflows | R1 partner program and platform surfaces | Potential higher-ACV route beyond self-serve subscriptions | Selective program with no disclosed contract sizes or live customer count |
| IP / licensing partners | Brand or IP partner plus end-user fans; commercial payer mix unclear | Licensed template libraries and governed use of character IP | Captain Tsubasa collaboration and KAGAMI Gate PoC | Differentiates PixVerse from generic prompt tools | Promo value is visible; recurring revenue terms are not |
| Institutional / creator programs | Organizer, sponsor, or creator may pay depending on program design | Film-festival submissions, workshops, community storytelling | UN AI for Good program and Product Hunt community surface | Extends trust and reach beyond pure entertainment apps | Monetization and renewal from these programs are not disclosed |
Segments are inferred from public product surfaces and named programs; the evidence identifies users more clearly than it identifies high-value payers.
[CU001, CU005, CU007, CU008, CU010, CU029]Public evidence shows a path from self-serve discovery into paid access, team workflow, partner integration, and then an unresolved renewal stage.
[CU001, CU008, CU021, CU023, CU029, CU031]6.2 Adoption evidence is strongest in app-store distribution and broad creator reach
AIsphere’s public adoption proof is strongest where consumer platforms publish telemetry or rankings. AppBrain provides the sharpest external read: the page displays 50,000,000+ downloads, separately says the app has been downloaded 73 million times, shows roughly 980 thousand downloads in the last 30 days, ranks the app #2 in photography, and reports a 4.49 rating from roughly 4.3 million ratings. Product Hunt adds a much smaller but still useful prosumer signal, with 304 followers, six reviews, and four launches. Apptopia confirms an iOS listing under MotivAI Private Limited, while Google Play, Uptodown, and APKPure together show broad distribution beyond a single storefront. At the company-claim layer, PRNewswire, PixVerse’s production-platform update, and March 2026 financing coverage all reinforce the same headline: more than 100 million users, international reach, and very large cumulative video volume. What those numbers do not reveal is the fraction of users who pay, stay, or expand into higher-value contracts.[CU012, CU013, CU014, CU015, CU016, CU017]
| Metric | Value | Date | Source | Confidence | Implication | Missing denominator |
|---|---|---|---|---|---|---|
| AppBrain install base snapshot | 50,000,000+ on-page downloads; 73M lifetime downloads | 2026-07 snapshot | AppBrain | Medium | Very large Android distribution footprint is externally visible | Store/download counts do not equal paying users |
| AppBrain recent momentum | ~980K downloads in last 30 days; #2 in photography | 2026-07 snapshot | AppBrain | Medium | Consumer funnel still appears active in mid-2026 | No cohort, geography split, or payer conversion |
| AppBrain rating base | 4.49 / 5 from ~4.3M ratings | 2026-07 snapshot | AppBrain | Medium | Large consumer interaction footprint and broadly positive sentiment proxy | Ratings are not retention, revenue, or enterprise satisfaction |
| Product Hunt prosumer footprint | 304 followers; 6 reviews; 4 launches; 4.3 score | 2025-12 archive snapshot | Product Hunt (via Wayback) | Low-to-medium | Shows some maker/prosumer awareness beyond mobile stores | Community footprint is modest relative to mass-market app installs |
| Company PR scale claim | 100M+ users and 800M+ generated videos | 2025-09-24 | PR Newswire | Medium | Large installed base existed before the March 2026 financing cycle | No disclosure of paid share or active-user frequency |
| Financing-coverage scale claim | 100M+ users; 16M MAU; $40M+ ARR | 2026-03 | CnTechPost / Yicai / AI Insider | Medium | Multiple March 2026 reports repeat the same broad scale narrative | User and ARR claims are not broken down by segment or geography |
| Official platform-scale update | 100M+ users across 175+ countries; 2B+ videos generated | 2026-07 snapshot | PixVerse production-platform update | Medium | Company claims both breadth and accelerating output volume | No link to paying-account count, renewal, or account concentration |
| iOS distribution presence | App listed under MOTIVAI PRIVATE LIMITED in Photo & Video / Entertainment | 2026-07 snapshot | Apptopia | Low-to-medium | Shows PixVerse is multi-platform, not Android-only | No iOS download or revenue estimate is public on the captured page |
The trajectory table mixes marketplace telemetry, company claims, and financing coverage because AIsphere does not publish a conventional paying-customer KPI dashboard.
[CU012, CU013, CU014, CU015, CU016, CU017]The public motion runs from broad discovery and activation into a much smaller set of paid, collaborative, and partner-led use cases.
[CU012, CU017, CU021, CU022, CU025, CU027]6.3 Named proof is real, but it is partner- and template-led rather than classic enterprise-logo heavy
The most concrete named public proofs are not Fortune-500 customer stories with quantified ROI. They are partner programs, branded campaigns, workflow integrations, and creator initiatives. Captain Tsubasa and KAGAMI Gate show PixVerse being used as the operating surface for a licensed IP campaign and an IP-usage tracking proof-of-concept. Tripo Studio shows a concrete game-art workflow in which PixVerse acts as the cinematic look-development stage before a 3D asset is built. The UN AI for Good partnership gives PixVerse an institutional creator program with workshop and film-festival exposure. At the same time, the template pages matter because they reveal how everyday users actually behave: they use pre-built, low-friction creative formats such as Dancing Baby, Winter Sovereign, and Fly to the Sun, rather than only blank-canvas prompt engineering. This is meaningful customer evidence, but it is better read as proof of active community behavior and partner experimentation than as proof of diversified enterprise revenue.[CU021, CU022, CU023, CU024, CU025, CU026]
| Customer / partner | Segment | Deployment or use case | Production vs pilot | Outcome / proof quality | Limitation |
|---|---|---|---|---|---|
| Captain Tsubasa / KAGAMI Gate | IP licensing / fan creation | Licensed character templates and governed AI-video IP usage tracking | Live limited-time campaign plus proof-of-concept infrastructure | Named counterparties, concrete use case, surfaced inside official app-store copy and official campaign pages | No contract economics, renewal, or revenue contribution disclosed |
| UN AI for Good Global Summit | Institutional creator program | Workshop plus AI for Good Film Festival submissions on a UN stage | Live 2026 program | Named institutional partner and globally visible creator call-to-action | Program prestige is clear; direct monetization is not |
| Tripo Studio | Game / 3D workflow partner | Look-development in PixVerse before conversion into 3D assets | Live integration feature | Concrete job-to-be-done for game teams, stronger than generic co-marketing | No named downstream paying studio or contract detail |
| R1 partner program | API / embedded users | Selective early access for studios, platform developers, and tool builders | Early commercial program | Buyer archetypes and commercial mechanics are explicit | Customers are unnamed and pricing remains selective rather than standard GA |
These are named public proofs, but most are partner/program examples rather than disclosed recurring enterprise customers.
[CU027, CU028, CU029, CU030, CU031, CU032]| Template / behavior | Audience | Proof surface | Repeat or monetization signal | Limitation |
|---|---|---|---|---|
| AI Dancing Baby | Social-first consumer creators | PixVerse hot-template page | Company claims millions of social views and one-click repeatable creation | Official page does not disclose unique users or spend |
| Winter Sovereign | Fantasy / cosplay / cinematic creators | PixVerse hot-template page | Shows reusable transformation workflow beyond a single meme format | No usage count or campaign conversion data |
| Fly to the Sun | Cinematic storytelling creators | PixVerse hot-template page | Shows template-led photo-to-video storytelling that can be reused across users | No retention or revenue disclosure by template family |
| Captain Tsubasa licensed effects | Anime / football fans and branded-campaign users | Official campaign page plus Google Play listing | Licensed templates are pushed through consumer acquisition surfaces, not just buried in enterprise materials | Limited-time campaigns may create spikes rather than durable cohorts |
| Invite-code and Discord behavior | Early adopters and active community members | Official R1 invite-code guide | Ongoing social distribution and Discord activity imply repeat attention around premium features | Community participation is not the same as paying retention or enterprise value |
These rows show public behavior patterns around templates and community motion; they are useful adoption proxies but not direct revenue-quality proof.
[CU022, CU025, CU026, CU027, CU032]Proof quality is highest where named counterparties and concrete workflows exist, but revenue and durability visibility remain weak across every public segment.
Cells summarize public proof depth rather than internal sales status; they show where evidence is concrete versus where it remains opaque.
[CU015, CU027, CU030, CU031, CU034, CU038]6.4 Repeat-usage proxies exist, but retention and durability disclosure remains weak
PixVerse does have public signals that users come back: paid subscribers get automatic R1 access, higher resolutions are highlighted as premium-quality outputs, invite codes are continuously distributed through Discord and social channels, and template pages are refreshed across multiple themes instead of being frozen launch artifacts. Consumer satisfaction proxies are also directionally positive, with AppBrain’s large rating base and Product Hunt’s smaller review set. But none of those proxies clears the diligence bar for customer durability. They do not tell investors how many users convert to paid, how long they stay, whether gross or net retention is positive, or whether branded programs turn into repeat spend. Even the strongest official monetization pages stop at pricing surfaces, access rules, and collaboration features. The chapter therefore treats ratings, template refreshes, and subscription gating as repeat-usage hints rather than as substitutes for retention cohorts or renewal data.[CU014, CU021, CU022, CU023, CU024, CU033]
| Metric | Value / status | Segment | Confidence | Diligence ask |
|---|---|---|---|---|
| Paying-customer count | All monetized segments | Low | Provide paid subscriber count, paying-team count, and paying API-partner count. | |
| NRR / GRR / logo churn | Team, API, and enterprise-adjacent accounts | Low | Provide cohort retention bridge with contraction, churn, and expansion by segment. | |
| Contract length / renewal terms | Team Plan, API partners, branded programs | Low | Provide median contract term, renewal windows, and renewal rate. | |
| Customer concentration / top account share | Enterprise and partner revenue | Low | Provide top-1, top-5, and top-10 customer revenue shares plus partner concentration. | |
| Public satisfaction proxy | AppBrain 4.49/5 from ~4.3M ratings; Product Hunt 4.3 from 6 reviews | Consumer creators / prosumers | Medium | Separate active-user satisfaction from install-base sentiment with paid cohort CSAT or NPS. |
| Repeat-usage proxy | Paid R1 access, invite-code community, and refreshed template library suggest ongoing usage | Consumer creators / prosumers | Medium | Disclose subscriber retention, paid monthly actives, and repeat-generation frequency by cohort. |
Null means not publicly disclosed in the reviewed source set; the non-null rows are proxies, not true retention or revenue-quality metrics.
[CU014, CU015, CU021, CU022, CU023, CU024]6.5 Expansion paths are plausible across teams, API, and partners, but concentration and revenue mix are unknown
PixVerse’s expansion logic is legible from the public record. Broad creator distribution feeds self-serve experimentation; paid R1 access and higher quality settings create an upsell path; Team Plan and Canvas add the controls needed for agencies, marketing teams, and professional creators; and the partner program creates an embedded or API route into studios, platform developers, and tool builders. Branded programs such as Captain Tsubasa and AI for Good show that PixVerse can also package its product into licensing and campaign contexts. That is a credible land-and-expand story. The unresolved issue is concentration. No reviewed source discloses whether enterprise/API revenue is material, whether it is concentrated in a handful of partners, or whether consumer subscriptions still dominate the mix. KrASIA’s financing coverage adds another reminder: even when management says subscriptions cover costs, public customer economics remain thin. Investors can see the motion; they still cannot underwrite the account base.[CU039, CU040, CU041, CU042, CU043, CU044]
| Expansion driver | Public proof | Concentration risk | Impact | Diligence path |
|---|---|---|---|---|
| Free creator to paid subscriber upsell | R1 access is immediate for paid subscribers and premium quality is emphasized in official guides | Free-to-paid conversion is undisclosed | Could be the core consumer monetization lever if conversion is healthy | Disclose conversion, payer ARPU, and subscriber retention by plan. |
| Solo creator to team workspace | Team Plan, shared workspaces, pooled credits, and Canvas project organization | No named teams, seat counts, or renewals are public | Key bridge from consumer traction into higher-value accounts | Disclose team-plan logos, seat growth, and renewal cohorts. |
| Team workflow to API / embedded program | Selective R1 partner program for studios, platform developers, and tool builders | Selective access may mean revenue is concentrated in a few partners | Potentially highest ACV route, but also the biggest opacity source | Disclose partner count, contract size, and top-partner exposure. |
| Branded / IP campaigns | Captain Tsubasa, KAGAMI Gate, and AI for Good show PixVerse can package branded or mission-driven programs | Could be one-off promotional revenue rather than repeat revenue | Adds strategic optionality in licensing and campaigns | Disclose repeat program count, contract structure, and renewal history. |
| Toolchain / game workflow partners | Tripo Studio creates a concrete prosumer-to-pro workflow | No named downstream paying studios are public | Supports gaming and 3D expansion, but commercial depth is unproven | Disclose active partner-generated accounts and studio expansion. |
| Distribution platforms and community channels | Google Play, iOS, third-party stores, Product Hunt, and social invite channels drive discovery | Acquisition mix may be overly dependent on platforms and virality | Large funnel, but higher platform-policy and trend risk | Disclose acquisition mix by store, web, referral, and partner channels. |
Risk rows are based on public channel structure and disclosure gaps; they describe plausible expansion mechanics, not verified realized revenue mix.
[CU021, CU039, CU040, CU041, CU042, CU043]6.6 Exhibits
07Risks
7.1 Severity-Ranked Risk Overview
AIsphere's risk stack is led by three issues that can compound rather than appear in isolation. First, PixVerse is a public AI-video product with Chinese and international surfaces, so China's generative-AI and labeling rules are not theoretical background: they directly govern content labeling, complaint handling, personal-information duties, and potential service suspension if regulators view controls as insufficient. Second, frontier video quality and low-latency inference still depend on advanced computing and cloud infrastructure, leaving AIsphere exposed to U.S. export-control tightening, NVIDIA supply limits, and concentration around Alibaba Cloud-backed global deployment. Third, the company sits inside the unresolved copyright zone facing the broader generative-AI industry, where training-data provenance, output ownership, and licensed IP usage remain contested. Below that top tier sit model-quality and consumer-distribution fragility, since app-store scale and leaderboard status can reverse quickly in AI video, followed by capital and execution risk because AIsphere has ample fresh financing but little public disclosure on burn, customer concentration, or compliance staffing. The risk picture is therefore best understood as a transmission chain from regulation and supply into product reliability, enterprise trust, margin quality, and eventually valuation.[CR036, CR041, CR042, CR043, CR045]
Likelihood, impact, mitigation maturity, and residual exposure for the major AIsphere risk clusters.
Cells synthesize source-backed severity and mitigation maturity; they are judgmental rankings, not probability forecasts.
[CR041, CR042, CR043, CR045]7.2 Legal and Regulatory Risk
Legal and regulatory exposure is AIsphere's clearest top-tier risk because PixVerse combines exactly the features that regulators are trying to discipline: public-facing generative video, real-time interaction, user-uploaded content, and growing API distribution. China's interim measures apply to public generative-AI services that generate text, images, audio, video, or other content, require lawful training-data sources, and explicitly mandate labeling obligations through the deep-synthesis regime. The 2025 labeling measures add both explicit user-facing marks and implicit metadata requirements, while also pushing providers toward complaint handling, user agreements, logging, and content-safety controls. For AIsphere, that creates a concrete implementation burden rather than a remote policy headline because PixVerse markets Chinese and global web surfaces, consumer apps, and production workflows. Export controls are the second major legal vector: BIS clarified in 2026 that advanced-computing items still require licenses for China-linked entities, so any tightening in frontier GPU access can flow straight into model cadence and service economics. The third legal vector is copyright. Generative-AI litigation in the United States still leaves open questions around training-data fair use, output ownership, and downstream liability, and AI-video products face additional exposure when they market branded or character-based outputs. AIsphere has started to experiment with licensed-IP infrastructure, which is directionally helpful, but public evidence does not yet show a mature, audited legal-control stack.[CR001, CR002, CR003, CR004, CR005, CR006]
| Risk | Jurisdiction / regime | Status | Likelihood | Severity | Mitigation maturity | Residual exposure | Diligence path |
|---|---|---|---|---|---|---|---|
| China generative-AI and labeling compliance | CAC interim measures + 2025 labeling rules | In force | High | Critical | Medium | High | Request CAC filing or security-assessment history, label implementation logs, and complaint workflows |
| Frontier GPU export-control access | BIS advanced-computing controls | License requirement active | Medium | Critical | Low | High | Review GPU vendors, license posture, inventory coverage, and fallback hardware plans |
| Training-data and output copyright exposure | U.S. and global AI copyright litigation | Unresolved | Medium | High | Low | High | Review training-data provenance, indemnities, and output-rights policies |
| EU transparency and documentation duties | EU AI Act / GPAI downstream use | Phased rollout | Medium | Medium | Low | Medium | Map API, customer, and documentation obligations by geography |
| Personal-information and user-record handling | China data and user-protection obligations | In force | Medium | Medium | Medium | Medium | Inspect retention, deletion, DPA, and user-request response controls |
| Licensed-IP governance | Branded content and licensing infrastructure | Proof-of-concept | Medium | Medium | Low | Medium | Audit rights scope, renewal terms, and infringement escalation processes |
Severity is ranked by direct regulatory leverage and transmission into service continuity, enterprise trust, and valuation; the table is material but not an exhaustive legal review.
[CR001, CR003, CR004, CR007, CR009, CR014]7.3 Operational, Model-Quality, and Security Risk
Operationally, AIsphere is no longer just a consumer effects app. Its public materials now describe a production platform, real-time world-model features, and an API partner program, which expands the failure surface across latency, moderation, partner support, and enterprise reliability. Real-time video matters here because continuous interaction is harder to label, review, and moderate than one-off clip generation, especially once user prompts, uploads, and downstream distribution all happen at scale. Public evidence supports strong momentum rather than mature operational disclosure: Artificial Analysis shows PixVerse among leading video-model vendors, AppBrain shows very large mobile adoption, and the company highlights broad feature breadth. What is missing is just as important. Public sources do not show a robust incident history, enterprise SLA schedule, or implementation evidence for compliance operations across China and international markets. Dependence on cloud and infrastructure vendors also deserves attention. Comparable public-cloud filings from Cloudflare, Datadog, and Snowflake all warn that outages, security incidents, and third-party infrastructure failures can damage availability and customer trust. AIsphere is unlikely to be exempt from those dynamics; if anything, fast product expansion and real-time video raise the operational bar further. The result is a risk profile where reliability, moderation, and security are not known weak points today, but are materially under-documented relative to the ambition of the product roadmap.[CR011, CR012, CR013, CR016, CR018, CR019]
| Failure mode | Likelihood | Severity | Mitigation maturity | Residual exposure | Unresolved gap |
|---|---|---|---|---|---|
| GPU or cloud-capacity interruption | Medium | Critical | Low | High | Supplier terms, capacity buffers, and fallback plans are undisclosed |
| Real-time labeling or moderation failure | Medium | High | Low | High | No public evidence of live-video control benchmarks or audit results |
| Service outage or degraded latency | Medium | High | Medium | Medium-High | No public enterprise SLA schedule or incident history |
| Security or privacy incident | Low-Medium | High | Medium | Medium | No public audit pack, breach history, or detailed data-governance artifacts |
| Model-quality regression versus leaders | Medium | High | Medium | Medium-High | No independent cadence for win-rate or failure-rate disclosure |
| App-store distribution or payment disruption | Medium | Medium | Low | Medium | Store ranking dependence and take-rate economics are undisclosed |
Operational register combines company disclosures with risk patterns repeatedly disclosed by scaled cloud and software platforms in public filings.
[CR013, CR016, CR031, CR032, CR033, CR034]How regulatory, infrastructure, and quality failures can transmit into revenue, margin, and valuation.
Edges show the likely direction of downside transmission rather than a fully quantified causal model.
[CR033, CR046, CR048]7.4 Partner, Dependency, Customer, and Competition Risk
AIsphere's dependency stack is unusually dense. Alibaba Cloud reportedly provides full-stack support for training, inference, global deployment, and compliance, which makes the relationship strategically valuable but also makes cloud concentration a direct economic and availability risk. GPU dependence compounds that problem because frontier video models still need advanced computing, while export rules can affect China-linked access at exactly the time when world-model ambitions increase compute appetite. Distribution is also concentrated. App-store scale is a strength, but it means discovery, payments, ranking visibility, and part of customer trust sit on third-party platforms rather than inside AIsphere's own channels. Enterprise monetization introduces a different dependency pattern: the R1 API partner program is selective instead of fully open, so near-term enterprise revenue may depend on a relatively small set of qualified partners and support resources. Licensed-IP and workflow partnerships cut both ways as well. Captain Tsubasa and KAGAMI Gate show that AIsphere is trying to build rights-cleared growth loops, while the Tripo integration broadens creator workflows, but each partner also becomes a potential point of delay, renegotiation, or dilution. Competition raises the stakes further because Runway and other video labs pursue similar world-model narratives, and fast shifts in category leaders can turn current traction into tomorrow's churn if quality leadership slips.[CR020, CR021, CR022, CR023, CR024, CR025]
| Dependency | Counterparty | Role | Concentration | Failure scenario | Severity | Mitigation | Residual exposure |
|---|---|---|---|---|---|---|---|
| Advanced GPU supply | NVIDIA / export-controlled supply chain | Core model training and inference | High | Capacity loss, price spike, or delayed access to frontier compute | Critical | Hardware diversification and licensing discipline | High |
| Cloud deployment backbone | Alibaba Cloud and related infrastructure vendors | Training, inference, deployment, compliance support | High | Price shock, outage, or strategic reprioritization harms availability and margin | High | Multi-region architecture and secondary-vendor planning | High |
| Mobile app distribution | Google Play / app-store ecosystems | User acquisition, billing, trust surface | Medium-High | Store policy, ranking, or suspension hits downloads and monetization | High | Web distribution and stronger direct channels | Medium-High |
| Enterprise API monetization | Selective R1 partners | Distribution and early enterprise conversion | Medium | Slow onboarding or partner churn delays enterprise revenue mix shift | Medium | Broader self-serve onboarding and partner enablement | Medium |
| Licensed-IP growth loops | KAGAMI Gate and rights holders | Branded templates and rights management | Medium | Rights lapse or weak enforcement causes campaign disruption or legal exposure | Medium | Contracted rights scope and auditable content tracking | Medium |
| Workflow ecosystem expansion | Tripo Studio and creator-tool partners | Extended use cases for creators and studios | Low-Medium | Partner roadmap slippage reduces differentiated workflow value | Medium | Build native capabilities or redundant integrations | Medium |
The common pattern is that external partners provide growth, infrastructure, or rights coverage while also becoming points of strategic fragility.
[CR024, CR025, CR026, CR027, CR028, CR029]Critical external dependencies around compute, cloud, distribution, rights, and ecosystem expansion.
The map emphasizes dependency concentration, not contractual hierarchy or revenue share.
[CR025, CR027, CR035, CR047]7.5 Capital and Execution Risk
Capital risk is real even after the Series C because fresh financing does not answer the core underwriting questions. Public evidence shows AIsphere raising $300 million and pushing into larger product surfaces, but burn, runway, customer payback, top-customer concentration, and retained gross-margin profile remain undisclosed. That matters because PixVerse's pricing is explicitly credit-based and low-friction, which can accelerate adoption while masking whether heavy usage translates into durable contribution margins once compute and support costs are fully allocated. Execution risk also sits higher than the company's growth narrative might suggest. The organization now needs a leadership bench that can support compliance, trust and safety, partner enablement, enterprise support, cloud operations, and legal oversight at the same time. Yet public materials mostly emphasize product velocity rather than the staffing depth behind those functions. The result is a mid-to-high risk bucket: financing strength reduces immediate insolvency concern, but incomplete operational and financial disclosure means investors still cannot test whether AIsphere can convert consumer-scale momentum into durable, compliant, and economically attractive enterprise growth.[CR017, CR030, CR038, CR039, CR043]
| Role / function | Dependency or gap | Likelihood | Severity | Mitigation | Diligence path |
|---|---|---|---|---|---|
| Finance and planning | Burn, runway, and unit-economics disclosure are absent | Medium | High | Monthly planning discipline and conservative liquidity targets | Review board pack, monthly cash forecast, and scenario model |
| Legal / trust-and-safety operations | Expanding China and global compliance workload is not matched by visible staffing detail | Medium | High | Dedicated policy, moderation, and legal-ops bench | Request org chart, headcount by function, and escalation KPIs |
| Enterprise support and solutions engineering | Selective API program implies scarce onboarding capacity | Medium | Medium | Partner playbooks, SLA ownership, and support staffing | Inspect partner onboarding funnel and response-time data |
| Leadership bench depth | Public materials emphasize product velocity more than management redundancy | Medium | Medium-High | Add experienced operators in finance, compliance, and enterprise GTM | Review executive bios, board observers, and hiring plan |
| Model evaluation and red-teaming | Real-time video expands failure modes that require disciplined testing | Medium | High | Formal pre-release evals, adversarial testing, and incident drills | Request evaluation rubric, release gates, and postmortem process |
Execution risk is less about founder quality than about whether support, compliance, and finance functions are scaling as quickly as product ambition.
[CR017, CR030, CR038, CR039, CR043]7.6 Mitigations, Monitoring Indicators, Thesis-Break Triggers, and Diligence Asks
The visible mitigation story is coherent but incomplete. AIsphere is not ignoring risk: licensed-IP experiments, a selective API partner program, enterprise workflow tooling, and public benchmarking all suggest the company is trying to move from viral consumer novelty toward rights-aware and enterprise-usable infrastructure. NIST-style governance principles provide a credible blueprint for the controls the company should eventually show. But the current evidence base still points to mitigation maturity that is mixed rather than proven. Investors should therefore monitor a small set of hard signals instead of broad narratives: whether PixVerse can demonstrate China-labeling and complaint-handling compliance in practice, whether frontier GPU or cloud access remains stable, whether app-store ratings and download momentum hold up, whether enterprise partner conversion expands beyond selective pilots, and whether future disclosures finally bound burn and customer concentration. The cleanest thesis-break events are also clear. A regulatory action in China, loss of credible access to advanced compute, or sustained quality and distribution slippage that prevents consumer traction from converting into enterprise revenue would each materially weaken the investment case. The highest-priority diligence asks are compliance artifacts, GPU and cloud contracts, customer-concentration data, burn and runway, and staffing depth for legal, trust-and-safety, and partner support.[CR044, CR045, CR046, CR047, CR048]
| Risk | Monitorable trigger | Threshold / event | Action implication |
|---|---|---|---|
| China compliance and labeling | Regulatory notice or missing audit evidence | Takedown, warning, or inability to show label workflow | Pause underwriting until controls are verified |
| Frontier GPU access | License delay or shrinking capacity buffer | Less than 6-12 months credible access to required compute | Cut growth and model-cadence assumptions |
| Copyright and provenance | No training-data controls or weak indemnities | Management cannot evidence provenance, rights-cleared data, or indemnity posture | Reduce enterprise revenue confidence or avoid |
| Cloud concentration | Single-vendor dependency remains dominant | No meaningful failover or commercial leverage versus a primary provider | Discount reliability and gross-margin assumptions |
| App-store dependence | Consumer distribution weakens | Ratings, downloads, or store status deteriorate materially | Lower scale and monetization assumptions |
| Model-quality expectations | Benchmark slippage versus leaders | Loss of top-tier quality standing for multiple release cycles | Lower moat and conversion assumptions |
| Capital adequacy | Runway shortens faster than planned | Under 12 months runway without committed capital | Treat financing as thesis-critical |
| Execution depth | Support or compliance bench does not scale | Partner backlog, unresolved incidents, or missing compliance hires | Move to research-more unless corrected |
Triggers are designed to be monitorable and investment-relevant rather than abstract risk labels.
[CR044, CR045, CR048]7.7 Exhibits
08Valuation
8.1 Financing context and the implied ARR multiple
AIsphere has enough evidence to support a valuation discussion, but not enough to support a clean price. Multiple March 2026 reports independently confirm a $300 million Series C and repeat the same commercial shorthand: AIsphere had surpassed $40 million in ARR, more than 100 million users, and over 16 million monthly active users. Those are meaningful scale markers for an AI-video startup. They also fit the earlier report framing that the company is directionally a unicorn-level asset after the round. The problem is that none of the retained public sources fully reconcile the exact post-money, the cap-table effects, or the economics of the security being sold. That uncertainty matters because it changes how to read the headline multiple. If the company was marked at roughly $1 billion and ARR merely exceeded $40 million, the implied headline multiple is around 25x ARR or lower because the disclosed ARR number is only a floor. On the surface that is less aggressive than the hottest AI-video and Chinese AI scarcity comps. But the discount is not obviously a bargain. It mostly compensates for weak visibility into revenue quality, paid-customer mix, gross margin, and preference structure. In other words, AIsphere looks investable enough to stay on the funnel, but not transparent enough to treat the current headline price as self-validating.[CV001, CV002, CV003, CV004, CV005, CV006]
| Decision field | Current view | Supporting evidence | Decision implication |
|---|---|---|---|
| Recommendation | research-more | The company looks real and scaled, but public evidence still underspecifies revenue quality and security terms. | Keep AIsphere live in the funnel; do not clear the current price for investment yet. |
| Confidence | medium | Funding, product, and comp evidence are real, but exact valuation mechanics and ARR quality remain under-documented. | Prioritize data-room diligence over a hard pass or positive term-sheet recommendation. |
| Risk rating | high | Valuation support depends on revenue conversion, compute economics, and a favorable AI capital-markets window. | Treat any deal as diligence-heavy and downside-sensitive. |
| Valuation stance | stretched | A ~$1B headline mark on >$40M ARR implies a lower multiple than hotter peers, but also reflects weaker disclosure and proof. | Require either better evidence or a more forgiving entry price. |
| Entry discipline | No fresh capital at the current mark without cap-table and revenue-bridge clarity | The biggest unresolved variables are preference stack, paid-customer quality, and gross-margin durability. | Push for price protection, milestone tranching, or wait. |
| Upgrade path | Audited proof or cheaper entry | A cleaner ARR bridge and terms package would move the call faster than another narrative funding headline. | Revisit only when evidence or price changes materially. |
This table is intentionally price-sensitive: it summarizes what the current mark already assumes rather than scoring AIsphere as a company in the abstract.
[CV007, CV026, CV030, CV031, CV032, CV033]The recommendation follows from real scale signals being offset by weaker revenue-quality and term-sheet visibility.
The flow is qualitative rather than probabilistic; it maps the decision chain implied by the retained valuation evidence.
[CV001, CV003, CV007, CV026, CV030, CV033]8.2 Comparable set and where AIsphere actually sits
The best way to read AIsphere's implied mark is as a middle position inside a frothy but internally stratified comp set. Runway is the closest private AI-video workflow comp: TechCrunch says it raised at a $5.3 billion valuation in February 2026, while Sacra estimates $90 million of annualized revenue in 2025, implying roughly a 59x revenue multiple. Pika sits much lower at about a $470 million valuation, but public sources do not disclose its revenue cleanly enough to produce a reliable multiple. At the high end, Moonshot's May 2026 round and April ARR disclosure imply something like a 100x ARR floor, while MiniMax's Hong Kong IPO valuation against reported revenue and losses shows that public markets were willing to underwrite very rich Chinese AI multiples as long as narrative momentum held. AIsphere is cheaper than those hotter comps on the headline arithmetic, but it is also weaker on proof. Independent benchmarks place PixVerse V6 in the competitive first tier, not the clearly dominant slot, and the category remains crowded enough that buyer switching is real. The public record also lacks the enterprise-quality disclosure that later-stage software or infrastructure investors would normally demand. That is why the right takeaway is not “AIsphere is cheap because 25x is below 59x or 100x.” The better takeaway is that the market may be giving AIsphere a disclosure discount for good reason, even while conceding that the company has real scale and a credible product.[CV008, CV009, CV010, CV011, CV012, CV013]
| Comparable | Key metric | Multiple / valuation / status | Relevance | Limitation |
|---|---|---|---|---|
| AIsphere (private, Mar 2026) | >$40M ARR claim; >100M users; >16M MAU | Directionally unicorn-level / ~$1B headline mark; exact post-money undisclosed | Direct asset under review | ARR is a company-linked floor and the security terms are not public. |
| Runway (private, Feb 2026) | Sacra estimated $90M annualized revenue in 2025 | $5.3B valuation; ~59x revenue on Sacra's estimate | Closest AI-video workflow and world-model comp with visible 2026 financing | Revenue is third-party estimated rather than audited, and Runway has broader enterprise proof. |
| Pika (private, Jun 2024) | Consumer-first AI-video product; revenue undisclosed | ~$470M valuation after an $80M round | Useful lower-end AI-video comp for the category's floor | Older mark and no clean revenue base for a multiple comparison. |
| Moonshot AI (private, May 2026) | ARR topped $200M in April 2026 | ~$20B valuation; roughly ~100x ARR on the disclosed floor | Upper-bound China AI scarcity comp with fresh ARR commentary | Much broader model, API, and agent scope than AIsphere. |
| Zhipu AI (Hong Kong IPO, Jan 2026) | Hong Kong IPO targeting about $640M of proceeds | ~$6.7B / HK$51.2B IPO valuation target | Shows public investors were willing to back Chinese AI scarcity in 2026 | Our retained set gives limited normalized revenue detail for a clean multiple comparison. |
| MiniMax (Hong Kong IPO, Jan 2026) | $53M of 9M25 revenue; $512M loss | ~$6.5B IPO valuation and later $33B market-cap rally after model-driven enthusiasm | Best public AI-video-adjacent China comp for frothy late-stage appetite | Listing-day and post-rally pricing are volatile and not steady-state fair value. |
This is a sample-based comparable set intended to bracket valuation logic across private AI-video peers and public Chinese AI issuers rather than to force one “correct” multiple.
[CV002, CV007, CV008, CV011, CV013, CV015]AIsphere's value is more sensitive to proof quality and terms than to another narrative funding headline.
Values are ordinal impact scores from 1 to 5, not probabilities or a mechanistic pricing model.
[CV020, CV022, CV023, CV024, CV025, CV037]8.3 Investment thesis, anti-thesis, and recommendation
The thesis is straightforward. AIsphere is not a slideware company. It has raised real capital, exposes real product surfaces, shows real user-scale claims, and appears in independent benchmark sets rather than only in its own marketing. Those facts matter because they separate AIsphere from pre-revenue concept stories and make a unicorn-level narrative at least directionally understandable. The anti-thesis is equally important. The company has not shown the exact valuation mechanics, the ARR claim remains company-linked rather than audited, and the current evidence does not tell investors whether the revenue base is mostly sticky enterprise/API spend or a more fragile mix of creator subscriptions and promotional traffic. Public filings from Adobe, Snowflake, Datadog, Cloudflare, and NVIDIA make that disclosure gap impossible to ignore. Given those offsets, the supportable call is research-more, not buy. Confidence should be medium because the company-quality case is real but the security-quality case is still incomplete. Risk should be high because valuation support depends on multiple things going right at once: revenue conversion, compute discipline, and a still-open AI capital-markets window. The valuation stance should therefore be stretched. AIsphere is not obviously absurd at the headline mark, but the current evidence base is too thin to say the price is attractive.[CV019, CV020, CV021, CV022, CV023, CV024]
| Argument | Direction | What supports it | What would change the view |
|---|---|---|---|
| AIsphere is a real scaled asset, not a concept story. | thesis | The company raised $300M, exposes paid product surfaces, and appears in independent benchmark sets. | Audited channel-level revenue and cohort data would turn this from credibility proof into full underwriting proof. |
| The current mark may still be mostly a narrative mark. | anti-thesis | The public record does not reconcile the exact post-money, preference stack, or recognized-revenue quality. | A clean term sheet and revenue bridge would reduce the narrative premium. |
| AIsphere is cheaper than the hottest AI comps on surface arithmetic. | thesis | A rough 25x ARR ceiling sits below Runway and Moonshot headline multiples. | If ARR quality is weak or terms are aggressive, the discount disappears. |
| PixVerse is competitive but not clearly dominant. | anti-thesis | Artificial Analysis shows a first-tier product in a tight field rather than a runaway benchmark leader. | Durable benchmark leadership or segment-specific win-rate evidence would strengthen premium-multiple arguments. |
| Disclosure quality is materially below mature public software norms. | anti-thesis | Public filings disclose revenue-quality and margin markers that AIsphere does not publish. | Management-level KPI disclosure and audited statements would narrow the credibility discount. |
| Security quality may lag company quality. | anti-thesis | No public cap table, liquidation waterfall, or side-letter economics are visible. | Clean terms could improve investability faster than more growth headlines. |
The anti-thesis is mainly about pricing, proof quality, and security structure rather than denying that AIsphere has a real product.
[CV019, CV020, CV021, CV022, CV026, CV029]AIsphere scores well on strategic relevance and product credibility, but poorly on evidence depth and security visibility.
Scores are IC-style heuristics based on retained evidence as of the run date; they are not management KPIs.
[CV019, CV020, CV026, CV029, CV030, CV031]8.4 Bull / base / bear logic and price discipline
Scenario analysis is more defensible here than a single-point target. In the bull case, AIsphere would turn the public ARR and user claims into a cleaner audited bridge, prove that enterprise/API economics are meaningful, and keep PixVerse competitive enough that the company still benefits from sector-level scarcity. Under that fact pattern, a valuation in roughly the $1.4 billion to $1.8 billion range is supportable. In the base case, the public commercial story proves directionally real but not cleanly underwritten: ARR is real yet partly creator-heavy, margins remain hard to assess, and terms stay private. That supports something like $0.85 billion to $1.1 billion, which makes the current headline mark closer to fair-to-stretched than obviously cheap. The bear case is a double hit. If paid conversion, enterprise quality, or API depth disappoints at the same time that AI-video scarcity premiums cool, the valuation could compress toward roughly $0.55 billion to $0.75 billion. That does not require the company to fail. It only requires investors to decide that a still-opaque AI-video startup should no longer be valued like the most exuberant peers. This is why entry discipline matters more than narrative enthusiasm: the upgrade path is better evidence or a better price, ideally both.[CV033, CV034, CV035, CV036, CV037, CV038]
| Scenario | Assumptions | Valuation / return logic | Probability signal | Key risks |
|---|---|---|---|---|
| Bull | Audited ARR and channel mix validate software-quality recurring revenue; terms are clean; PixVerse remains first-tier on benchmarks. | $1.4B-$1.8B; the current mark looks acceptable only if disclosure quality catches up to the story. | low-medium | Requires enterprise/API economics to prove much stronger than the public record currently shows. |
| Base | ARR proves real, but the mix remains only partly disclosed and security terms stay private. | $0.85B-$1.1B; today's mark is roughly fair to stretched, with limited margin of safety. | medium | Leaves investors exposed to multiple compression and term-sheet surprises. |
| Bear | Paid conversion, enterprise quality, or sector appetite weakens before AIsphere demonstrates cleaner economics. | $0.55B-$0.75B; the company could rerate well below unicorn rhetoric without needing to fail operationally. | medium-high | Narrative premium and revenue-quality concerns can break at the same time. |
Ranges are scenario valuations, not DCF outputs, because public evidence does not disclose cap-table mechanics, recognized revenue quality, or margin structure well enough for false precision.
[CV033, CV034, CV035, CV036, CV037, CV038]A scenario band is more defensible than a single-point target because price support depends on evidence that is still missing.
Ranges are editorial scenario estimates derived from disclosed ARR floors, comp brackets, and disclosure quality rather than from a DCF or exit-model precision exercise.
[CV033, CV034, CV035, CV036, CV038, CV042]8.5 Final diligence asks and thesis-break triggers
The remaining diligence work is unusually concentrated and highly actionable. First, investors need a monthly bridge from bookings to ARR to recognized revenue by channel, because the current >$40 million ARR claim is not enough to tell whether AIsphere deserves a software-quality multiple. Second, investors need the March 2026 term sheet, post-money cap table, liquidation waterfall, and any side letters, because security quality can be much weaker than company quality at the same headline valuation. Third, investors need unit-economics proof: compute cost per video minute, gross margin by product surface, and the share of revenue that is renewal-like rather than campaign-like. The kill triggers are correspondingly concrete. A down round, heavy senior preferences, or a weak revenue bridge would show that the unicorn narrative got ahead of the evidence. A widening benchmark gap or lower paid conversion would weaken the claim that product quality can sustain premium economics. And a colder Hong Kong or Chinese AI funding tape would remove the scarcity premium that currently helps support comparables. Until those items are closed, the right posture is continued diligence rather than conviction buying.[CV037, CV038, CV040, CV041, CV042, CV043]
| Trigger | Threshold | Transmission to thesis | Action implication |
|---|---|---|---|
| A down round or heavy structured financing | New capital prices below the implied unicorn level or adds aggressive senior preferences | Shows that the current headline mark overstated outside support or overstated security quality. | Move from research-more to avoid / wait-for-reset unless terms improve dramatically. |
| Weak revenue bridge | Recognized revenue, ARR composition, or API/enterprise mix does not support the >$40M headline in quality terms | Breaks the thesis that scale signals are converting into durable software economics. | Re-rate valuation into the bear band. |
| Thin paid-customer quality | Low paid conversion, weak renewals, or high concentration behind the user headline | Turns product popularity into a weaker monetization story than the valuation assumes. | Require a lower entry price or milestone-based structure. |
| Benchmark slippage | PixVerse loses first-tier status or falls meaningfully behind on quality/cost tradeoffs | Undercuts the argument that product competitiveness can sustain premium pricing. | Reduce bull-case probability and compress acceptable multiple. |
| Sector multiple compression | Hong Kong or private-market appetite for Chinese AI cools materially | Removes scarcity support that currently props up private and newly public comps. | Shift posture from diligence to wait-for-repricing. |
These are valuation-specific kill criteria linked to entry price and security quality rather than a general risk register restatement.
[CV027, CV028, CV040, CV041, CV042]| Topic | Missing evidence | Why it matters | Owner / diligence path |
|---|---|---|---|
| Revenue bridge | Monthly bookings, ARR, deferred revenue, and recognized revenue by consumer, API, and enterprise channels | Determines whether the >$40M ARR headline supports a software-quality multiple or only a promotional scale story. | Finance team, board materials, and auditor pack. |
| Cap table and preference stack | Post-Series C capitalization table, liquidation waterfall, anti-dilution, and side-letter economics | Defines security quality and true downside at the current headline valuation. | Company counsel and financing document review. |
| Unit economics | Gross margin by product surface, compute cost per video minute, support burden, and cloud commitments | Tests whether AI-video usage can scale profitably rather than just visibly. | FP&A, infrastructure, and cloud-contract review. |
| Cohort quality | Paid customer count, NRR, churn, expansion, and concentration by top accounts | Separates user scale from durable recurring revenue quality. | Revenue operations and billing exports. |
| Enterprise/API proof | Named enterprise accounts, API revenue share, contract terms, and renewal history | Shows whether AIsphere deserves to be valued closer to workflow/API peers than to consumer novelty tools. | Sales leadership plus top-customer contract sampling. |
| Next-round / exit path | Timing and structure of the next financing, secondary, or listing plan | Current private marks are partly supported by a favorable AI funding and Hong Kong issuance window. | Board, lead investors, and banking advisors. |
These asks are prioritized by how quickly they would change the recommendation or acceptable entry price, not by how easy they are to obtain.
[CV037, CV043, CV044, CV045, CV046]8.6 Exhibits
Disclaimer
This report is for informational purposes only and reflects public-source diligence as of 2026-07-03. AIsphere is a private company; many commercial, governance, and security details remain unaudited or undisclosed and should be independently verified before any investment decision.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | AIsphere is the English name used by Beijing Aishi Technology Co., Ltd., whose official corporate site describes it as an AI-video-generation model and applications company. | Medium | SO001, SO020 |
| CO002 | Public registry-style and encyclopedia sources place AIsphere’s establishment on 2023-04-07 in Beijing. | Medium | SO020, SO014, SO017 |
| CO003 | AIsphere’s headquarters are publicly described as being in Beijing. | Medium | SO014, SO015, SO020 |
| CO004 | The company’s official positioning is to build world-leading AI video generation large models and applications for the AGI era. | Medium | SO001 |
| CO005 | PixVerse is AIsphere’s flagship AI-video product surface for global users across web and mobile. | Medium | SO002, SO003, SO024, SO025 |
| CO006 | Founder and CEO Wang Changhu previously worked at Microsoft Research Asia and led visual-technology efforts at ByteDance. | Medium | SO021, SO014, SO017 |
| CO007 | Co-founder Xie Xuzhang is quoted publicly on financing strategy and product direction in 2026 coverage. | Medium | SO010, SO011 |
| CO008 | AIsphere launched PixVerse for overseas users in January 2024 and released a domestic beta shortly afterward. | Medium | SO014 |
| CO009 | The company completed more than CNY 400 million of Series A fundraising by March 2025, including an A5 round led by Eminence Ventures. | Medium | SO015 |
| CO010 | Yicai reported that AIsphere employed around 50 workers as of March 2025. | Medium | SO015 |
| CO011 | PixVerse had more than 40 million worldwide users and more than 15 million monthly active users by March 2025, according to Yicai. | Medium | SO015 |
| CO012 | Alibaba led AIsphere’s $60 million Series B round in September 2025. | Medium | SO016, SO017, SO009 |
| CO013 | Series B participants publicly named by TMTPOST included Fortune Capital, Shenzhen Capital Group, the Beijing AI Industry Investment Fund, Giant Network, and Antler. | Medium | SO017 |
| CO014 | Public 2025 company statements said PixVerse had already passed 100 million users worldwide and more than 800 million generated videos. | Medium | SO016 |
| CO015 | AIsphere’s March 2026 Series C raised $300 million and set a new record for a single China AI-video financing round. | Medium | SO009, SO010, SO011 |
| CO016 | CDH Investments led the March 2026 Series C round, with more than 20 institutions participating according to CnTechPost. | Medium | SO009 |
| CO017 | Yicai said Series C investors also included Ruyi Holdings, 37 Interactive Entertainment, E-Town Capital, Suzhou Capital Group, Lion X Fund, and UOB Venture Management. | Medium | SO010 |
| CO018 | Late-2025 to early-2026 public coverage put AIsphere’s annual recurring revenue above $40 million. | Medium | SO009, SO010 |
| CO019 | Yicai reported that PixVerse and Paiwo AI together exceeded 100 million users, with more than 16 million monthly active users, by October 2025 / early 2026. | Medium | SO010 |
| CO020 | AIsphere publicly launched PixVerse R1 in January 2026 as a real-time world model supporting 1080p generation. | Medium | SO006, SO007, SO018 |
| CO021 | Official product materials describe R1 as moving AI video from offline clip generation to continuous, interactive world simulation. | Medium | SO006, SO007, SO002 |
| CO022 | AIsphere launched V6 in March 2026 with stronger camera control, character performance, multilingual text rendering, multi-shot audio, and CLI integration. | Medium | SO005, SO004 |
| CO023 | Sina reported in December 2025 that AIsphere had iterated its self-developed video model five times in about two years. | Medium | SO019 |
| CO024 | PixVerse’s official homepage says its enterprise stack combines proprietary video foundation models, APIs, template ecosystems, and near-real-time generation for production workflows. | Medium | SO002 |
| CO025 | Official product pages market PixVerse across both consumer creation and enterprise API use cases. | Medium | SO002, SO003, SO024 |
| CO026 | Official and company-linked sources frame V5.6 as ranking #2 globally on Artificial Analysis video-generation leaderboards. | Medium | SO008, SO016 |
| CO027 | Sina reported that PixVerse also entered a16z’s global top-50 generative-AI consumer mobile-app ranking at #25 in 2025. | Medium | SO019, SO022 |
| CO028 | The Google Play listing shows PixVerse distributing frequent consumer-facing features such as text-to-video, image-to-video, upscaling, templates, and licensed effects. | Medium | SO023 |
| CO029 | PixVerse maintains dedicated app-download and mobile tutorial pages for iOS and Android distribution. | Medium | SO024, SO025 |
| CO030 | AIsphere and Alibaba Cloud announced a full-stack AI cooperation in December 2025 covering infrastructure, model services, products, ecosystem, and commercial globalization. | Medium | SO019 |
| CO031 | The Alibaba Cloud agreement explicitly tied cloud infrastructure and compliance support to training and inference for PixVerse’s proprietary video model. | Medium | SO019 |
| CO032 | KrASIA reported that Wang Changhu told 36Kr subscription revenues from AIsphere’s products already cover costs. | Medium | SO013 |
| CO033 | KrASIA also framed AIsphere’s 2023 founding as a contrarian bet made while many investors doubted independent video-model startups could survive against OpenAI and Chinese internet giants. | Medium | SO013 |
| CO034 | Public reporting repeatedly places AIsphere in a highly competitive field that includes OpenAI Sora, ByteDance Seedance/Jimeng, and Kuaishou Kling. | Medium | SO009, SO013, SO014 |
| CO035 | Official materials present AIsphere as a vertically integrated AI-video company spanning proprietary models, consumer creation tools, and enterprise APIs rather than a single demo model. | Medium | SO001, SO002, SO003, SO024 |
| CO036 | The public record still does not disclose a full board roster or a clean, current cap-table breakdown. | Medium | SO020, SO021, SO009 |
| CO037 | The exact March 2026 post-money valuation is directionally around unicorn level but not independently reconciled in the fetched public record. | Medium | SO009, SO010, SO011, SO012 |
| CO038 | User, ARR, and “largest-in-sector” claims are concentrated in company-linked or single-chain media reports rather than audited disclosures. | Medium | SO009, SO010, SO013, SO016 |
| CO039 | AIsphere appears to be following a consumer-first global distribution strategy before deeper enterprise monetization. | Medium | SO013, SO019, SO024, SO025 |
| CO040 | The fetched public evidence supports AIsphere as a real Beijing-based AI-video startup with fast funding momentum, but leaves governance, exact valuation mechanics, and independently audited economics unresolved. | Medium | SO001, SO009, SO010, SO020, SO021 |
| CM001 | TBRC defines generative AI in video creation as the use of generative models to create, edit, or enhance video content. | Medium | SM002 |
| CM002 | TBRC segments the category by deployment, applications, and end users, specifically naming on-premise versus cloud, marketing/education/entertainment/social media, and large enterprises/SMEs/individual creators. | Medium | SM002 |
| CM003 | Research and Markets separately frames the market by deployment, application, end user, and end-use industries such as media and entertainment companies and educational institutions. | Medium | SM001 |
| CM004 | Official vendor surfaces show that the market boundary now spans consumer creation, production workflows, and APIs rather than only one-off text-to-video clips. | High | SM008, SM013, SM015, SM016 |
| CM005 | Runway, Pika, Vidu, Kling, Jimeng, and Wan all market AI video generation directly, confirming a crowded substitute set outside AIsphere. | Medium | SM008, SM024, SM025, SM026, SM027, SM028 |
| CM006 | Upstream GPU/training spend and the broader generative AI software stack are better treated as adjacent or enabling spend than direct revenue for video-creation vendors. | Medium | SM001, SM002, SM003 |
| CM007 | TBRC says the generative AI in video creation market reached $0.39 billion in 2025, will grow to $0.47 billion in 2026, and is projected to reach $0.98 billion in 2030. | Medium | SM002 |
| CM008 | Research and Markets says the generative AI in video creation market is valued at $0.47 billion in 2026 and projected to reach $0.98 billion by 2030 at a 20.4% CAGR. | Medium | SM001 |
| CM009 | The two narrow-market publishers agree that dedicated generative-video-creation revenue remains sub-$1 billion today even while growing around 20% annually. | High | SM001, SM002 |
| CM010 | Fortune Business Insights sizes the broader generative AI market at $103.58 billion in 2025, $161 billion in 2026, and $1,260.15 billion by 2034. | Medium | SM003 |
| CM011 | Fortune says North America held 48.70% of the broader generative AI market in 2025 and that enterprise adoption plus foundation-model innovation are major growth drivers. | Medium | SM003 |
| CM012 | Because the broader generative AI market is roughly two orders of magnitude larger than the narrow video-creation estimates, using one figure as a stand-in for the other would materially overstate direct addressable spend. | Medium | SM001, SM002, SM003 |
| CM013 | a16z says AI video models moved from experimental to fairly dependable for short clips over the prior six months. | Medium | SM004 |
| CM014 | The same a16z report says Hailuo, Kling, and Sora debuted on the web rankings and that Hailuo and Kling surpassed Sora in monthly visits by January 2025. | Medium | SM004 |
| CM015 | Artificial Analysis frames category competition around quality Elo, speed, and pricing across text-to-video, image-to-video, and audio-enabled models. | Medium | SM005 |
| CM016 | Artificial Analysis' text-to-video leaderboard lists PixVerse V6 at Elo 1,069 and $6.90 per minute, versus Veo 3.1 at Elo 1,096 and $24.00 per minute and Vidu Q3 Pro at Elo 1,082 and $9.60 per minute. | Medium | SM006 |
| CM017 | Artificial Analysis' image-to-video leaderboard lists PixVerse V6 at Elo 1,074 and $6.90 per minute, versus Veo 3.1 at Elo 1,086 and $24.00 per minute. | Medium | SM007 |
| CM018 | Benchmark dispersion is narrow enough on quality but wider on price that workflow fit and cost control matter almost as much as absolute leaderboard position. | Medium | SM005, SM006, SM007 |
| CM019 | Google Play and PixVerse's blog/home surfaces position PixVerse for simple creator workflows, viral effects, and mobile-first experimentation. | Medium | SM011, SM017 |
| CM020 | TBRC explicitly lists marketing and social media among the main applications for generative video AI. | Medium | SM002 |
| CM021 | Vidu markets fast workflows for social content, ads, and storytelling, showing how SMB marketers can buy AI video for campaign production rather than entertainment alone. | Medium | SM025 |
| CM022 | PixVerse's production-platform update says teams need collaboration, asset management, automation, and distribution, indicating that media or IP buyers care about more than clip generation quality. | Medium | SM015 |
| CM023 | PixVerse's blog homepage highlights officially licensed Captain Tsubasa templates, suggesting that branded-content and licensing relationships can matter in media-oriented workflows. | Medium | SM017 |
| CM024 | PixVerse's R1 API partner page targets studios, platform developers, and tool builders, making developers and API teams a distinct buyer class from end creators. | Medium | SM016 |
| CM025 | Runway markets Characters as a real-time video-agent API for custom conversational characters, reinforcing the existence of an API-led developer segment in the category. | Medium | SM008 |
| CM026 | TBRC says on-premise deployment offers more control and customization but requires more maintenance and upfront costs, which is a real enterprise tradeoff rather than just a technical option. | Medium | SM002 |
| CM027 | PixVerse's English homepage claims enterprise-ready foundational models, APIs, and production-ready workflows, showing the company is courting enterprise rather than only consumers. | High | SM013, SM014, SM015 |
| CM028 | Runway's pricing page reserves enterprise plans for teams scaling AI-video production with custom credit packages and contact sales, showing enterprise spend is sold differently from creator subscriptions. | Medium | SM009 |
| CM029 | Budget ownership is fragmented across creator subscriptions, SMB campaign budgets, media production budgets, developer platform budgets, and enterprise transformation budgets. | Medium | SM002, SM009, SM015, SM016, SM025 |
| CM030 | TBRC names expanding social media and digital platforms as a direct growth driver for the narrow market. | Medium | SM002 |
| CM031 | Research and Markets and TBRC both point to automated editing, personalized marketing, real-time collaboration, and cloud-based collaborative video production as core trend or driver categories. | High | SM001, SM002 |
| CM032 | PixVerse's English homepage says its world engine supports end-to-end multimodal generation, long-horizon streaming generation, and real-time 1080p video in interactive scenarios. | Medium | SM014 |
| CM033 | Runway says it is building general world models and a real-time Characters API, showing that leading vendors are expanding toward interactive video agents, not only rendered clips. | Medium | SM008 |
| CM034 | Pika markets agents, MCP integrations, and automation workflows, widening the category from pure generation into workflow tooling. | Medium | SM024 |
| CM035 | PixVerse's pricing doc says $1 buys five V6 720p, 5-second, no-audio videos on the starter pack, while higher resolutions and audio consume more credits. | High | SM012, SM013 |
| CM036 | Runway's pricing starts free, then scales through $12, $28, and $76 annualized monthly-equivalent plans before enterprise custom credits. | Medium | SM009 |
| CM037 | Self-serve creator pricing and enterprise custom-credit plans let vendors land with low-friction experimentation and then expand into higher-value team workflows. | Medium | SM009, SM012, SM015 |
| CM038 | China's 2023 generative AI measures apply to public services that generate text, images, audio, and video, and impose requirements around lawful data use, personal-information protection, content governance, transparency, labeling, risk mitigation, and filing or registration. | High | SM018, SM019 |
| CM039 | China's 2025 AI-labeling measures require AI-generated online content to be labeled and are intended to curb false information and misuse. | High | SM020, SM021 |
| CM040 | Compliance affects go-to-market speed because public video products in China must pair growth with labeling, governance, and filing operations rather than just creative feature velocity. | High | SM018, SM019, SM020, SM021 |
| CM041 | BIS states that a license is required to export advanced computing items to China-linked entities even if those entities are located outside China, and GT Law says the requirement remained fully in force in 2026. | High | SM022, SM023 |
| CM042 | Export controls and compute access remain adoption constraints for China-linked vendors because model iteration speed and cost still depend on advanced computing supply. | Medium | SM022, SM023, SM005 |
| CM043 | OpenAI says the Sora web and app experiences were discontinued on April 26, 2026 and the Sora API is scheduled to end on September 24, 2026. | Medium | SM010 |
| CM044 | Even category leaders can discontinue products, so buyers evaluating AI-video vendors still face platform-continuity and migration risk alongside pure model-quality questions. | Medium | SM008, SM010, SM024 |
| CM045 | Public evidence does not isolate AIsphere's paid share, enterprise mix, or attributable spend capture inside the broader generative-video market, so a clean SAM or SOM remains unproven from public sources alone. | Medium | SM001, SM002, SM015, SM016 |
| CP001 | PixVerse publicly positions itself as a full-stack AI media generation platform with APIs, enterprise-ready workflows, and service in more than 177 countries. | Medium | SP001 |
| CP002 | Runway now frames itself as a world-model company with products such as GWM-1 and Characters, not only as an AI video generator. | Medium | SP003, SP018 |
| CP003 | Runway publishes free, Standard, Pro, Max, and enterprise tiers and includes third-party models such as Kling, Seedance, and Veo in higher plans. | Medium | SP004 |
| CP004 | OpenAI’s original Sora preview said the model could generate videos up to one minute long and framed Sora as progress toward real-world simulation. | Medium | SP005 |
| CP005 | OpenAI’s deployed Sora experience was limited to up to 1080p, up to 20-second outputs and was publicly described as still struggling with unrealistic physics and long-duration actions. | High | SP005, SP006 |
| CP006 | OpenAI later discontinued the Sora web and app experience on April 26, 2026 and plans to discontinue the Sora API on September 24, 2026. | High | SP006, SP007 |
| CP007 | Kling 3.0 and Kling 3.0 Omni publicly emphasize deep multimodal instruction parsing, long-form storyboard control, native audio, and cross-scene consistency. | Medium | SP008 |
| CP008 | Vidu markets text, image, and reference-video generation workflows for social content, ads, and storytelling. | Medium | SP009 |
| CP009 | The fetched Hailuo landing page confirms a live AI video and image product but exposes little public detail on pricing, enterprise packaging, or governance. | Medium | SP010 |
| CP010 | The fetched Wan landing page confirms a live AI video brand but leaves pricing and trust posture under-disclosed on the public surface. | Medium | SP011 |
| CP011 | Jimeng publicly highlights text/image-to-video generation, first-and-last-frame control, Chinese prompt support, and a creator community. | Medium | SP012 |
| CP012 | Pika has expanded into agent and MCP tooling and explicitly says agents can access “all the models,” making Pika as much a routing layer as a single-model product. | Medium | SP013 |
| CP013 | Artificial Analysis compares quality, speed, and pricing across a broad video-model field that includes Kling, Hailuo, Vidu, Wan, Seedance, Sora, Grok, and open-weight LTX models. | Medium | SP014 |
| CP014 | In Artificial Analysis’s retained text-to-video leaderboard, Seedance 2.0 720p leads at 1222 Elo, while Kling 3.0 1080p scores 1106, Vidu Q3 Pro 1082, PixVerse V6 1069, and Wan 2.6 1024. | Medium | SP015 |
| CP015 | In Artificial Analysis’s retained image-to-video leaderboard, Seedance 2.0 720p leads at 1194 Elo, while Wan 2.7 scores 1093, PixVerse V6 1074, Kling 3.0 1080p 1072, and Vidu Q3 Pro 1061. | Medium | SP016 |
| CP016 | PixVerse’s public platform docs say $1 buys five V6 720p five-second no-audio videos and show memberships scaling from $1,500 to $6,000 per month for larger plans. | Medium | SP002 |
| CP017 | PixVerse’s public marketing site uses a vendor-authored chart to position PixVerse V6 against Grok, Kling, Veo, and Sora on quality, affordability, and speed. | Medium | SP001 |
| CP018 | TechCrunch reported that Runway raised $315 million at a $5.3 billion valuation in February 2026 to expand its next generation of world models. | Medium | SP018 |
| CP019 | TechCrunch reported that Moonshot AI raised about $2 billion at a $20 billion valuation and that its ARR topped $200 million in April 2026. | Medium | SP019 |
| CP020 | a16z’s Top 100 Gen AI Apps report says the consumer AI ecosystem is stabilizing, app stores are cracking down on copycat apps, and Pixverse moved from the brink list into the core rankings. | Medium | SP017 |
| CP021 | The same a16z report says many persistent AI consumer winners either use third-party or open models or operate as model aggregators, weakening the idea that model ownership alone wins distribution. | Medium | SP017 |
| CP022 | a16z says Chinese video products such as Hailuo and Kling have exported globally and that Chinese video models had tended to outperform Western-developed models until Veo 3. | Medium | SP017 |
| CP023 | China’s 2023 Interim Measures apply to public generative AI services for text, image, audio, video, and other content and require lawful data sources, transparency, stable service, and labeling through related rules. | High | SP020, SP021 |
| CP024 | China’s March 2025 labeling guidance requires visible marks on AI-generated internet content and prohibits deleting, tampering with, fabricating, or concealing those labels. | High | SP021, SP022 |
| CP025 | Loeb says China’s labeling measures extend explicit labels and metadata obligations to service providers and app distribution platforms, not only end users. | Medium | SP022 |
| CP026 | Harris says complying with China’s AI labeling regime requires metadata-preserving workflows, agency governance, and platform-specific operational controls. | Medium | SP023 |
| CP027 | NIST’s AI RMF and generative-AI profile signal that enterprise buyers increasingly expect structured documentation and trustworthiness practices around generative AI systems. | Medium | SP024 |
| CP028 | BIS and Greenberg Traurig say advanced-computing exports to China-linked entities still require licenses even when the recipient sits outside China, preserving compute-supply diligence risk for China-linked labs. | High | SP025, SP026 |
| CP029 | The EU AI Act requires identifiable AI-generated content and imposes documentation, copyright, and training-summary duties on providers of general-purpose AI models. | High | SP027, SP028 |
| CP030 | Because the retained benchmark field already includes open-weight LTX models and Wan variants, internal build and self-hosted stacks remain credible substitutes for some technical buyers. | Medium | SP014, SP015, SP016 |
| CP031 | Runway and Pika both teach buyers to think in multi-model terms, which lowers switching costs by letting the subscription or workflow layer route across changing frontier models. | Medium | SP004, SP013 |
| CP032 | PixVerse’s most direct creator-facing peers are Runway, Sora, Kling, Vidu, Hailuo, Wan, Jimeng/Seedance, and Pika because each markets text-, image-, or audio-linked AI video creation rather than only assistant chat. | Medium | SP001, SP003, SP005, SP008, SP009, SP010, SP011, SP012, SP013 |
| CP033 | The most powerful substitutes extend beyond standalone AI video apps to aggregators, internal build stacks, and adjacent AI workspaces that can satisfy the same content-creation job. | Medium | SP004, SP013, SP014, SP017 |
| CP034 | Runway’s current scope now includes video agents and broader world-model products, so it competes for workflow ownership rather than just per-clip generation. | Medium | SP003, SP018 |
| CP035 | Sora is a cautionary example that a headline entrant can preview frontier capability, launch with safety and quality caveats, and still retreat from the standalone product surface within the same cycle. | High | SP005, SP006, SP007 |
| CP036 | Relative to Runway’s subscriptions, PixVerse’s official credit pricing looks competitively aggressive on short-form generation, but that does not yet prove realized enterprise pricing power. | Medium | SP002, SP004 |
| CP037 | Independent leaderboard data shows PixVerse is first-tier but not clearly dominant because Seedance leads and Kling, Vidu, and Wan all remain close enough on quality and price to keep the category crowded. | Medium | SP015, SP016 |
| CP038 | Competitive pressure in China is not limited to pure-play video startups because generalist labs like Moonshot can attract developers into broader coding, reasoning, and agent ecosystems instead of standalone video apps. | Medium | SP017, SP019 |
| CP039 | Regulatory and trust posture may become a real competitive separator because China-facing vendors face visible labeling rules while EU- and U.S.-facing enterprise sellers face GPAI disclosure and AI-risk-management expectations. | Medium | SP020, SP021, SP022, SP024, SP027, SP028 |
| CP040 | Switching costs at the model layer are low enough that any durable moat probably has to come from workflow ownership, contract stickiness, or proprietary data rather than raw model access alone. | Medium | SP014, SP015, SP016, SP017, SP004, SP013 |
| CP041 | Public disclosure quality is uneven across the field, with Hailuo and Wan exposing substantially less retained detail on packaging and governance than Runway, OpenAI, or even PixVerse. | Medium | SP010, SP011, SP003, SP006, SP001 |
| CP042 | The retained benchmark set shows a global and volatile frontier because Chinese leaders, Google’s Veo family, and xAI’s Grok all appear near the top at once. | Medium | SP014, SP015, SP016 |
| CP043 | Because Runway bundles third-party models and Pika promises access to all models, buyers can multi-home without rewriting their workflow around one proprietary video brand. | Medium | SP004, SP013 |
| CP044 | Publicly legible compliance can matter commercially because some consumer-first Chinese video apps expose limited governance material in the retained set while rulebooks keep expanding. | Medium | SP010, SP011, SP021, SP022, SP023, SP027 |
| CP045 | AIsphere’s competitor set is bifurcating into destination apps, routing layers, and broader AI workspaces, which makes the category boundary porous and raises substitution risk from adjacent products. | Medium | SP014, SP017, SP019 |
| CI001 | PixVerse maintains a public platform surface for AI video API access alongside its consumer creation surfaces. | Medium | SI002, SI008 |
| CI002 | PixVerse’s official pricing docs state that $1 equals five V6 videos at 720p, five seconds, and no audio with the Starter pack. | Medium | SI003 |
| CI003 | The same pricing docs meter usage by model, resolution, duration, audio, and motion mode rather than by a single unlimited flat rate. | Medium | SI003 |
| CI004 | Official PixVerse pricing materials display prepaid credit packs from $50 to $5,000 and larger Scale and Business plan tiers, indicating both wallet top-ups and higher committed spend paths. | Medium | SI003 |
| CI005 | PixVerse’s production-platform update says Team Plan pools credits, centralizes billing, and adds role-based permissions and shared asset libraries for organizations. | Medium | SI004 |
| CI006 | PixVerse’s R1 partner program is selective rather than general availability and offers early access, grandfathered pricing, roadmap input, and technical support to qualified teams. | Medium | SI005 |
| CI007 | PixVerse Canvas documentation says project costs are measured in credits that vary by model, inputs, and plan, while video generation is priced separately by model, length, and settings. | Medium | SI006 |
| CI008 | PixVerse simultaneously maintains a consumer app, an app-download funnel, and developer or API surfaces, indicating a dual consumer-plus-platform distribution model. | Medium | SI002, SI008, SI009, SI010 |
| CI009 | A16Z’s August 2025 top-100 consumer AI ranking says PixVerse moved from the prior mobile brink list into the core rankings, providing an external adoption proxy beyond company PR. | Medium | SI011 |
| CI010 | CnTechPost, Yicai, and AI Insider all reported a $300 million March 2026 Series C round for AIsphere. | Medium | SI012, SI013, SI014 |
| CI011 | Those March 2026 reports also repeated that AIsphere had surpassed $40 million in ARR and 100 million users, with more than 16 million monthly active users. | Medium | SI012, SI013, SI014 |
| CI012 | KrASIA reported founder Wang Changhu’s statement that PixVerse subscription revenues already cover costs, but the claim is founder-reported rather than audited. | Low | SI016 |
| CI013 | PixVerse’s September 2025 PRNewswire release said the platform served more than 100 million users and had generated over 800 million videos. | Medium | SI017 |
| CI014 | PixVerse’s 2026 production-platform update claimed 100M+ users across 175+ countries and more than 2 billion videos generated. | Medium | SI004 |
| CI015 | The same production-platform update marketed about 68% cost reduction and about 57% faster production for organizations, which is evidence of enterprise value messaging rather than verified realized savings. | Low | SI004 |
| CI016 | The R1 partner program targets gaming studios, streaming platforms, and tool developers with required engineering capacity, launch timelines, and scale ambitions, implying a higher-touch enterprise sales motion. | Medium | SI005 |
| CI017 | Team Plan features like shared workspaces, pooled credits, and administrator billing are consistent with a land-and-expand workspace model instead of pure one-seat creator subscriptions. | Medium | SI004 |
| CI018 | Canvas supports task matrices, live queues, projected cost and time estimates, bulk export, and side-by-side model comparison, which fits professional workflow spend rather than casual one-off use. | Medium | SI006 |
| CI019 | Google Play copy still markets PixVerse as a mass-market creation tool and points users toward the official hub and API integration, supporting a broad top-of-funnel consumer wedge. | Medium | SI010 |
| CI020 | Longbridge’s Yicai summary said AIsphere is considering evolving its technology into an AI-native video game engine and cited interest from gaming and short-drama clients. | Low | SI015 |
| CI021 | Because official pricing varies with resolution, duration, audio, and motion mode, higher-fidelity or faster outputs likely consume more credits and expose customers to visibly higher unit prices. | Medium | SI003 |
| CI022 | PixVerse’s updated R1 post says the product now supports continuous shared worlds, multi-user interaction, and real-time 1080p generation, features that likely raise serving complexity beyond single clip generation. | Medium | SI007 |
| CI023 | Datadog’s 2025 10-K says cost of revenue includes payments to third-party cloud infrastructure providers for hosting software plus operations and support costs. | Medium | SI019 |
| CI024 | Snowflake’s 2026 10-K warns that failing to meet minimum commitments under third-party cloud infrastructure agreements can negatively impact results of operations. | Medium | SI020 |
| CI025 | Cloudflare’s 2025 10-K says cost of revenue includes co-location, network and bandwidth, certificate-authority, and equipment-depreciation expenses tied to serving paying customers. | Medium | SI018 |
| CI026 | NVIDIA’s 2026 10-K says Blackwell Ultra increases token throughput and reduces cost per token versus Hopper, underscoring that AI-serving economics depend heavily on underlying infrastructure efficiency. | Medium | SI021 |
| CI027 | Cloudflare disclosed $2,495.8 million of remaining performance obligations at year-end 2025 and expected to recognize 63% within 12 months, a transparency metric AIsphere does not publish. | Medium | SI018 |
| CI028 | Snowflake reported 125% net revenue retention as of January 31, 2026 and growth in $1 million product-revenue customers from 576 to 733, while AIsphere discloses neither NRR nor large-account counts. | Medium | SI020 |
| CI029 | Datadog reported $914.7 million of free cash flow in 2025 and explicitly monitors customers with ARR of $100,000 or more, another public quality marker absent from AIsphere’s disclosures. | Medium | SI019 |
| CI030 | Adobe’s 2025 annual report disclosed $2.55 billion of cost of revenue, $12.51 billion of operating expenses, $7.13 billion of net income, and $10.03 billion of operating cash flow, highlighting the disclosure gap between mature creative-software leaders and AIsphere. | Medium | SI022, SI023 |
| CI031 | Runway’s official pricing page uses the same basic design pattern as PixVerse—credits, tiered plans, and contact-sales enterprise packaging—suggesting AIsphere’s credit economics are not unusual for AI-video peers. | Medium | SI024 |
| CI032 | TechCrunch reported that Runway raised $315 million at a $5.3 billion valuation in February 2026 to pre-train next-generation world models, showing that frontier AI-video platforms remain capital-hungry even at scale. | Medium | SI025 |
| CI033 | Artificial Analysis publicly compares video-model quality, speed, and pricing across providers, which increases pricing transparency and competitive pressure in AI video. | Medium | SI026 |
| CI034 | Public evidence proves that AIsphere has real monetization surfaces and list pricing, but it does not reveal realized customer pricing, discount bands, or segment revenue mix. | Medium | SI002, SI003, SI004, SI005, SI006 |
| CI035 | The most plausible public revenue stack is a mix of consumer credits or subscriptions, team-workspace billing, API usage, and selective enterprise or partner contracts rather than a single homogeneous SaaS SKU. | Medium | SI002, SI003, SI004, SI005, SI006 |
| CI036 | AIsphere’s public revenue-quality evidence is materially weaker than public software comparables because it does not disclose backlog or RPO, NRR, enterprise customer counts, renewal cohorts, or cash flow. | Medium | SI018, SI019, SI020, SI022, SI023 |
| CI037 | Forward financing risk is lower than that of a pre-revenue startup because AIsphere closed a $300 million Series C and claims subscriptions cover costs, but the absence of cash, burn, runway, and debt data prevents a clean capital-adequacy conclusion. | Medium | SI012, SI013, SI014, SI016 |
| CI038 | Capital intensity is likely highest in real-time, high-resolution, multi-user, and API-driven workloads rather than in lightweight template-led consumer clips. | Medium | SI003, SI005, SI006, SI007 |
| CI039 | The company appears to be moving upmarket from creator acquisition into organizational sales by adding pooled billing, admin controls, API access, and partner programs. | Medium | SI004, SI005, SI006 |
| CI040 | The repeated ARR and user claims raise confidence that AIsphere is commercially real, but their reliance on company-linked reporting keeps confidence in revenue quality at medium rather than high. | Medium | SI012, SI013, SI014, SI016 |
| CI041 | The correct financial verdict is that AIsphere is financeable and monetizing, but still under-disclosed on margin, cash, contract quality, and concentration, so financial diligence should stay open. | Medium | SI003, SI012, SI013, SI018, SI019, SI020 |
| CE001 | PixVerse’s public app shell now exposes Creation, Agent, Canvas, Mini-Apps, Marketing Hub, and API Platform in one surface. | Medium | SE002 |
| CE002 | PixVerse’s homepage frames the company around frontier AI research, proprietary video foundation models, APIs, and a global video-intelligence ecosystem. | Medium | SE001 |
| CE003 | PixVerse is delivering a multi-surface product stack across consumer app, creator web, workflow tools, and API surfaces rather than a single generation endpoint. | High | SE001, SE002, SE005 |
| CE004 | PixVerse distributes official mobile access on iOS and Android and says the same account can be used across web and mobile with cloud sync. | High | SE003, SE020 |
| CE005 | The 2026 production-platform update adds Team Plan shared workspaces, role-based permissions, a shared asset library, and pooled billing. | Medium | SE008 |
| CE006 | PixVerse is introducing Mini Apps as purpose-built workflow shells above the core generation platform, with Ad Master as the first example. | Medium | SE008 |
| CE007 | Canvas is described as a node-based workspace where references, scripts, storyboards, generation batches, and finished cuts live on one connected board. | Medium | SE009 |
| CE008 | Canvas adds traceable prompts and settings, status tags, filtered views, batch queues, retry controls, and cost/time estimates for larger runs. | Medium | SE009 |
| CE009 | PixVerse presents a real developer surface through a priced platform and company-authored claims of CLI/API integration into automated pipelines. | High | SE005, SE008, SE012 |
| CE010 | PixVerse’s pricing docs show that generation is commercialized through credits across C1, V6, V5.6, audio, resolution, and duration settings. | Medium | SE004 |
| CE011 | The V6 launch says PixVerse’s proprietary next-generation video model adds camera tracking, perspective shifts, depth-of-field control, multilingual text rendering, multi-shot audio, and CLI integration. | Medium | SE006 |
| CE012 | The V6 review says V6 supports text-to-video, image-to-video, transition, extension, reference-to-video, 1–15 second duration, and up to 1080p output. | High | SE006, SE012 |
| CE013 | PixVerse’s pricing docs and V6 review both state that 1080p V6 generation costs 18 credits per second without audio and 23 credits per second with audio. | High | SE004, SE012 |
| CE014 | PixVerse’s public stack emphasizes integrated audio, multi-shot continuity, physics behavior, and literal camera control as part of the core product narrative. | Medium | SE001, SE006, SE012 |
| CE015 | R1 is positioned as a real-time AI world model that generates continuous interactive 1080p video instead of isolated finished clips. | High | SE007, SE010 |
| CE016 | PixVerse says R1 uses omni-native multimodal processing, 1–4 sampling steps per frame, and memory-augmented attention to support low-latency persistence. | Medium | SE007 |
| CE017 | The R1 update adds single-photo avatars, removes the earlier five-minute session cap, and introduces multi-user shared worlds. | High | SE007, SE010 |
| CE018 | The R1 partner page says the 720p real-time API provides synchronized audio and mid-stream narrative steering for interactive applications. | Medium | SE011 |
| CE019 | PixVerse packages the R1 API as a selective partner program for gaming studios, streaming platforms, and tool developers rather than as broad self-serve general availability. | Medium | SE011 |
| CE020 | PixVerse positions itself as a cinematic look-dev layer in front of Tripo Studio so teams can validate motion, lighting, and silhouette before committing to 3D modeling. | Medium | SE013 |
| CE021 | KAGAMI Gate makes PixVerse the operating surface for a proof-of-concept that tracks and constrains licensed IP usage inside AI-generated video creation. | Medium | SE014 |
| CE022 | The Captain Tsubasa rollout shows PixVerse translating that licensing layer into concrete user products: templates, challenges, and sanctioned fan-video creation. | Medium | SE014, SE015 |
| CE023 | The Google Play listing markets a broad consumer feature set including text-to-video, image-to-video, transition, 4K upscale, extension, motion control, reference images, and speech integration. | Medium | SE020 |
| CE024 | AppBrain reports about 73 million total PixVerse downloads, roughly 980 thousand downloads in the last 30 days, a 4.49 rating, and more than 4.3 million ratings on the access date. | Medium | SE021 |
| CE025 | The archived Product Hunt page shows PixVerse with 304 followers, 6 reviews, and 4 launches, indicating some maker-community presence beyond company blogs. | Medium | SE022 |
| CE026 | Artificial Analysis ranks PixVerse V6 14th in text-to-video with audio and V5.6 22nd on the accessed leaderboard. | Medium | SE019 |
| CE027 | Artificial Analysis ranks PixVerse V6 10th in image-to-video with audio and V5.6 21st on the accessed leaderboard. | Medium | SE018 |
| CE028 | PixVerse’s own V5.6 ranking post highlights selected leaderboard views, price framing, and “top-tier” language rather than claiming blanket category leadership. | Medium | SE017, SE018, SE019 |
| CE029 | PixVerse’s public marketing emphasizes high Elo and favorable price positioning, but the independent with-audio leaderboards still place V6 in the first tier rather than at number one. | Medium | SE001, SE018, SE019 |
| CE030 | PixVerse’s own V6 review says the model is strongest on camera movement, continuity, short narrative structure, and audio-visual timing, but still needs retries for chaotic action, multilingual dialogue, and brand-accurate product shots. | Medium | SE012 |
| CE031 | AppBrain user comments include complaints about unwanted changes, unnatural renders, and wasted credits even alongside praise for free credits and newer voice-model options. | Medium | SE021 |
| CE032 | Across the reviewed official home, app, blog, and platform pages, no public trust center, SOC 2 page, ISO 27001 page, or public uptime/status page was visible. | Medium | SE001, SE002, SE005, SE008 |
| CE033 | China’s 2023 generative-AI measures apply to public services that generate text, image, audio, video, or other content in China and require lawful data handling, privacy protection, output labeling, and safe stable service. | Medium | SE023 |
| CE034 | China’s 2025 labeling measures require visible labels and metadata-style identifiers for AI-generated content, and distribution platforms must review whether apps providing generative AI comply. | High | SE024, SE025 |
| CE035 | Harris Sliwoski argues that operational compliance now requires workflow rules, metadata retention, partner governance, and fast takedown processes because platform enforcement is tightening. | Medium | SE028 |
| CE036 | BIS guidance in May 2026 confirmed that advanced-computing export licenses remain required for China-linked entities even when the recipient is physically outside China. | High | SE026, SE027 |
| CE037 | For a China-linked AI-video platform, product delivery depends not only on model quality but also on compliant access to advanced compute and auditable content-governance workflows. | Medium | SE023, SE024, SE026, SE027 |
| CE038 | PixVerse’s AI for Good partnership and workshop/film-festival program show the company is trying to frame its product as globally useful creator infrastructure rather than only a consumer effect app. | Medium | SE016 |
| CE039 | PixVerse’s public materials repeat that the platform serves 100 million-plus creators and enterprises across 177-plus countries, but that scale is still company-claimed rather than independently audited product telemetry. | Medium | SE016, SE017 |
| CE040 | Even when creation starts on mobile, PixVerse remains cloud-served and credit-metered rather than on-device inference, so user experience still depends on backend reliability and spend tolerance. | Medium | SE003, SE020, SE021 |
| CE041 | The public product stack can be modeled as four layers: consumer creation surfaces, collaborative workflow surfaces, programmable API surfaces, and an emerging world-model surface. | High | SE002, SE008, SE009, SE011 |
| CE042 | PixVerse mixes proprietary models such as V6, C1, and R1 with selective external-model access, making workflow breadth a more durable differentiator than any single model release alone. | Medium | SE006, SE011, SE013, SE020 |
| CE043 | The selective R1 partner program can improve roadmap fit for high-scale builders, but it also means the newest real-time surface is not yet broadly proven in self-serve production. | Medium | SE011 |
| CE044 | PixVerse’s workflow ownership, IP-licensing experiments, and partner integrations differentiate the product more clearly than raw leaderboard placement does. | Medium | SE009, SE013, SE014, SE018, SE019 |
| CE045 | Public enterprise-readiness evidence is still thinner than product breadth because reviewed surfaces do not disclose API SLA terms, uptime history, incident reporting, or moderation/provenance implementation depth. | Low | SE005, SE008, SE011, SE012 |
| CE046 | OpenAI publicly discloses C2PA metadata, visible watermarks, and deepfake mitigations for Sora, providing a benchmark that PixVerse’s reviewed public safety surfaces do not yet visibly match. | Medium | SE029, SE001, SE002 |
| CE047 | Apptopia lists PixVerse: AI Video Generator on iOS under MOTIVAI PRIVATE LIMITED in Photo & Video and Entertainment, corroborating active iOS distribution beyond company-authored pages. | Medium | SE030 |
| CU001 | PixVerse maintains consumer app, app-download, and platform/API surfaces, implying distinct self-serve creator and developer entry points. | Medium | SU001, SU002, SU009 |
| CU002 | Google Play, Uptodown, APKPure, and AppBrain all distribute or track the Android app, while Apptopia tracks iOS, showing multi-store distribution rather than a single-channel mobile presence. | Medium | SU003, SU004, SU005, SU006, SU007 |
| CU003 | Google Play positions PixVerse as an all-in-one AI video maker for creators and highlights text-to-video, image-to-video, upscale, extension, and selection editing features. | Medium | SU003 |
| CU004 | Uptodown describes PixVerse as beginner-friendly for transforming images or text prompts into animated video with trending effects. | Medium | SU006 |
| CU005 | APKPure explicitly says PixVerse suits creators, marketers, and anyone needing social-friendly videos from prompts or photos. | Medium | SU007 |
| CU006 | PixVerse’s app-download page emphasizes mobile creation, image animation, social clips, and fast generation for creators anywhere. | Medium | SU002 |
| CU007 | PixVerse’s production-platform update says professional creators and enterprises pushed the product toward team workflows, asset management, automation, and developer tools. | Medium | SU011 |
| CU008 | The Team Plan adds shared workspaces, role-based permissions, shared asset libraries, and consolidated billing with pooled credits. | Medium | SU011 |
| CU009 | PixVerse’s platform site and pricing docs show a separate API or developer-platform surface alongside its consumer creation surfaces. | Medium | SU009, SU010 |
| CU010 | PixVerse’s R1 partner program is aimed at studios, platform developers, and tool builders who want to integrate real-time AI video generation into their products. | Medium | SU012 |
| CU011 | The R1 partner program is selective rather than general availability and offers qualified teams early access, favorable pricing, and roadmap influence. | Medium | SU012 |
| CU012 | AppBrain’s PixVerse page displays both 50,000,000+ downloads and a separate 73 million lifetime-download estimate, evidencing very large Android reach even if the exact methodology is opaque. | Medium | SU004 |
| CU013 | AppBrain says PixVerse drew roughly 980 thousand downloads in the last 30 days and ranked #2 in photography at the time of capture. | Medium | SU004 |
| CU014 | AppBrain rates PixVerse 4.49 out of 5 based on roughly 4.3 million ratings. | Medium | SU004 |
| CU015 | The archived Product Hunt page shows 304 followers, six reviews, four launches, and a 4.3 score, indicating some prosumer community interest but a much smaller footprint than the mass-market app stores. | Low | SU008 |
| CU016 | Apptopia shows a PixVerse iOS App Store listing under MOTIVAI PRIVATE LIMITED in the Photo & Video and Entertainment categories. | Medium | SU005 |
| CU017 | PixVerse’s September 2025 PRNewswire release said the platform served more than 100 million users worldwide and had generated over 800 million videos. | Medium | SU023 |
| CU018 | CnTechPost, Yicai, and AI Insider all reported in March 2026 that AIsphere had surpassed 100 million users and more than $40 million ARR. | Medium | SU024, SU025, SU026 |
| CU019 | Yicai and AI Insider also cited more than 16 million monthly active users, while official 2026 company materials claimed reach across 175+ countries and more than 2 billion videos generated. | Medium | SU011, SU025, SU026 |
| CU020 | A16Z’s August 2025 consumer AI ranking said PixVerse moved from the prior mobile Brink List into the core rankings, giving an external adoption proxy beyond company PR. | Medium | SU027 |
| CU021 | PixVerse’s R1 invite guide says paid subscribers automatically receive R1 access and lists Plus ($10/month), Pro ($25/month), and Team ($58/month) plans. | Medium | SU014 |
| CU022 | The same invite guide says PixVerse distributes invite codes through Twitter/X, Discord, YouTube, TikTok, and Instagram, with Discord described as the most active channel. | Medium | SU014 |
| CU023 | PixVerse’s quality guide says R1 supports 360p, 480p, 720p, and 1080p but defaults to lower resolution for smoother real-time streaming. | Medium | SU015 |
| CU024 | The same guide recommends 1080p for final output, implying a prosumer or paid workflow beyond casual preview usage. | Medium | SU015 |
| CU025 | PixVerse’s Dancing Baby page says the trend has gained millions of views across social media and frames template use as a one-click workflow for everyday creators. | Medium | SU016 |
| CU026 | The Winter Sovereign and Fly to the Sun pages show that PixVerse’s template library spans fantasy and cinematic storytelling, not just one meme format. | Medium | SU017, SU018 |
| CU027 | PixVerse’s Captain Tsubasa collaboration lets users generate videos with licensed franchise characters through official templates until July 26, 2026. | Medium | SU019 |
| CU028 | The KAGAMI Gate proof-of-concept positions PixVerse as the AI video platform inside a system for licensing and tracking IP use in generative video. | Medium | SU020 |
| CU029 | Taken together, the Captain Tsubasa and KAGAMI Gate pages show PixVerse pursuing IP/licensing use cases rather than only generic creator tooling. | Medium | SU019, SU020 |
| CU030 | The Tripo Studio integration positions PixVerse as a rapid look-development stage for game teams before they convert a winning frame into a 3D asset. | Medium | SU021 |
| CU031 | The UN AI for Good partnership invites creators worldwide to submit AI video works for a film festival and ties PixVerse to a UN-stage institutional program. | Medium | SU022 |
| CU032 | Google Play also surfaces the Captain Tsubasa collaboration directly in the app-store listing, showing that licensed campaigns are used for acquisition as well as for in-product engagement. | Medium | SU003, SU019 |
| CU033 | AppBrain explicitly notes that some competitors may offer a larger template or motion library and that broad permissions or SDK integrations may raise privacy concerns for sensitive users. | Low | SU004 |
| CU034 | Official R1 and Team Plan materials prove monetization paths and professional workflows, but they do not name specific paying enterprise accounts or contract values. | Medium | SU011, SU012, SU014, SU015 |
| CU035 | No reviewed public source discloses PixVerse’s paying-customer count, paying-team count, or free-to-paid conversion by segment. | Medium | SU003, SU004, SU011, SU014, SU023, SU024, SU025, SU026, SU028 |
| CU036 | No reviewed public source discloses NRR, GRR, customer churn, or logo-retention cohorts for any PixVerse segment. | Medium | SU011, SU012, SU014, SU023, SU024, SU025, SU026, SU028 |
| CU037 | No reviewed public source discloses contract length, renewal timing, or renewal rates for Team Plan, API partners, or named partner programs. | Medium | SU011, SU012, SU019, SU020, SU022 |
| CU038 | Strong consumer ratings are directionally useful, but ratings and reviews are not evidence of enterprise retention, expansion, or revenue durability. | Medium | SU004, SU008 |
| CU039 | No reviewed public source discloses customer concentration, top-account share, or revenue contribution from named partner programs. | Medium | SU011, SU012, SU019, SU020, SU021, SU022, SU023, SU024, SU025, SU026, SU028 |
| CU040 | No reviewed public source discloses the revenue mix between consumer subscriptions or credits and enterprise, API, or partner contracts. | Medium | SU010, SU011, SU012, SU023, SU024, SU025, SU026, SU028 |
| CU041 | PixVerse’s expansion logic runs from self-serve creation and template virality into paid R1 access, team collaboration, and API partnerships. | Medium | SU002, SU011, SU012, SU014, SU016, SU017, SU018 |
| CU042 | The named public proof set is skewed toward partner and use-case proof—Captain Tsubasa, KAGAMI Gate, UN AI for Good, and Tripo Studio—rather than toward named enterprise buyers with contract or outcome disclosure. | Medium | SU019, SU020, SU021, SU022 |
| CU043 | Channel dependence is material because discovery and usage are visibly mediated by app stores, social invite channels, Product Hunt, and partner ecosystems rather than by a disclosed direct-sales base. | Medium | SU003, SU005, SU008, SU014, SU021 |
| CU044 | KrASIA reported founder commentary that subscriptions cover costs, but even that financing story did not disclose customer mix, retention, or concentration. | Low | SU028 |
| CU045 | Production-platform and Canvas pages describe project, campaign, and client organization, which is more consistent with agency or team workflows than with hobby-only usage. | Medium | SU011, SU013 |
| CU046 | PixVerse’s V6 review frames the product as a production tool with repeatable workflows and concrete credit-cost testing, reinforcing appeal to prosumers and team users rather than only hobbyists. | Medium | SU029 |
| CR001 | China's interim generative-AI rules apply to public services in the PRC that generate text, images, audio, video, or other content. | High | SR015, SR016 |
| CR002 | Those rules require lawful training-data sources and prohibit infringement of third-party intellectual-property rights during training and optimization. | High | SR015, SR016 |
| CR003 | China's generative-AI regime links providers to labeling obligations for generated images and video through the deep-synthesis and service rules. | High | SR015, SR017, SR018, SR019 |
| CR004 | China's AI-labeling measures take effect on 2025-09-01 and require both visible labels and metadata-oriented labeling methods. | High | SR017, SR018, SR019 |
| CR005 | Providers also bear user-agreement, complaint-handling, security, and personal-information obligations under the PRC service rules. | High | SR015, SR016 |
| CR006 | Violations of China's generative-AI measures can trigger warnings, orders to correct, or suspension of related services. | Medium | SR015, SR016 |
| CR007 | BIS clarified in May 2026 that advanced-computing items still require export licenses for China-linked entities despite any temporary enforcement pause. | High | SR020, SR021 |
| CR008 | NVIDIA warns that export-control rules can restrict product availability and add cost and operational complexity to advanced-computing supply. | Medium | SR029 |
| CR009 | Generative-AI copyright litigation in 2026 still leaves open questions on training-data infringement, fair use, and ownership of AI outputs. | High | SR026, SR027, SR028 |
| CR010 | For an AI-video company, copyright exposure can arise from both training-data provenance and the licensed or infringing character of generated outputs. | Medium | SR026, SR027, SR028, SR034 |
| CR011 | PixVerse is offered as a public web and mobile product with Chinese and international surfaces rather than a private internal-only tool. | High | SR001, SR008, SR009 |
| CR012 | PixVerse also markets APIs and production workflows, which expands the compliance surface beyond consumer entertainment into enterprise use cases. | High | SR002, SR003, SR005, SR006 |
| CR013 | R1 is marketed as a real-time world model that responds continuously to user input, which raises live-content moderation and labeling complexity beyond static clip generation. | Medium | SR004, SR015, SR017 |
| CR014 | The EU AI Act creates transparency and documentation obligations around general-purpose AI models and downstream use that can matter to API and enterprise workflows. | High | SR022, SR023, SR024 |
| CR015 | NIST's AI Risk Management Framework treats governance, monitoring, testing, and incident response as ongoing controls rather than one-time certifications. | Medium | SR025 |
| CR016 | Public evidence does not show a published PixVerse compliance audit pack, DPA, or detailed China and EU implementation artifacts. | Medium | SR001, SR002, SR005 |
| CR017 | AIsphere has raised a $300 million Series C, but public burn, runway, and audited profitability remain undisclosed. | Medium | SR013, SR001 |
| CR018 | PixVerse's pricing docs show low-cost credit-based video generation, making unit economics sensitive to model mix, duration, resolution, and audio settings. | Medium | SR003 |
| CR019 | Artificial Analysis places PixVerse among leading video-model vendors, proving relevance but raising expectation risk if rankings slip. | Medium | SR007 |
| CR020 | Runway still markets world-model ambitions, illustrating that PixVerse competes against well-funded rivals with similar strategic narratives. | Medium | SR012, SR007 |
| CR021 | OpenAI's Sora discontinuation shows that AI-video product packaging and category leadership can change abruptly even among major incumbents. | Medium | SR011 |
| CR022 | AppBrain shows PixVerse at more than 50 million downloads and over 4 million reviews, proving scale but also dependence on app-store discovery and payments. | Medium | SR009 |
| CR023 | APKPure describes PixVerse as a fast consumer tool for creators and marketers, reinforcing a broad consumer-distribution orientation rather than a narrow enterprise-only model. | Medium | SR010 |
| CR024 | Sina reported that Alibaba Cloud provides AIsphere with full-stack AI support for training, inference, global deployment, and security-compliance capabilities. | Medium | SR014 |
| CR025 | Alibaba Cloud dependence means a cloud-pricing or capacity change can propagate into service availability, latency, and gross margins. | Medium | SR014, SR030, SR032 |
| CR026 | A selective R1 API partner program suggests enterprise monetization is being curated rather than broadly self-serve, which can slow scale and concentrate onboarding risk. | Medium | SR006, SR002 |
| CR027 | KAGAMI Gate is only a proof-of-concept for managing licensed IP in AI video, so AIsphere's rights-management mitigation is promising but immature. | Medium | SR033, SR034 |
| CR028 | The Captain Tsubasa collaboration shows branded IP can expand growth while also tying campaigns to external licensors and renewal risk. | Medium | SR034, SR033 |
| CR029 | The Tripo Studio integration broadens creator workflows but adds ecosystem dependence on external partners to complete the value proposition. | Medium | SR035, SR005 |
| CR030 | Public sources do not disclose top-customer concentration, NRR, or retention cohorts, leaving customer durability unresolved despite strong app-scale evidence. | Medium | SR013, SR009 |
| CR031 | Cloudflare, Datadog, and Snowflake each flag infrastructure outages, security incidents, and service interruptions as material platform risks in their 2025 and 2026 filings. | High | SR030, SR031, SR032 |
| CR032 | AIsphere's public materials emphasize rapid product expansion, APIs, and team workflows, which increases operational complexity even while broadening monetization avenues. | Medium | SR004, SR005, SR006 |
| CR033 | Real-time video features expand the surface for moderation misses, mislabeled outputs, and response-time failures during traffic spikes. | Medium | SR004, SR017, SR025 |
| CR034 | Public evidence shows product breadth and growth claims, but not a verified incident history or enterprise SLA schedule. | Medium | SR002, SR005, SR009 |
| CR035 | NVIDIA supply remains strategically critical because frontier video models depend on advanced computing and export rules can affect China-linked access. | High | SR020, SR021, SR029 |
| CR036 | AIsphere's combination of public consumer scale, API ambitions, and China domicile makes legal and regulatory risk more material than for a private internal AI lab. | Medium | SR001, SR008, SR015, SR017 |
| CR037 | Pricing compression risk is heightened because PixVerse competes in a crowded AI-video field where leaders market rapidly improving capabilities. | Medium | SR003, SR007, SR012 |
| CR038 | The $300 million round reduces near-term financing risk but does not remove capital risk while burn, cloud commitments, and customer payback are undisclosed. | Medium | SR013, SR014 |
| CR039 | Public evidence does not reveal the depth of compliance staffing, solutions engineering, or leadership redundancy needed for global enterprise expansion. | Medium | SR001, SR005, SR006 |
| CR040 | Because AIsphere markets both Chinese and global products, a regulatory incident in China could spill into foreign distribution, enterprise sales, and valuation perception. | Medium | SR015, SR017, SR020 |
| CR041 | The top three ranked risks are China compliance and labeling, GPU and cloud concentration, and unresolved copyright or IP exposure. | Medium | SR015, SR020, SR026 |
| CR042 | Model-quality and consumer-distribution risk sit just below the top tier because app-store traction and benchmark leadership can reverse quickly in AI video. | Medium | SR007, SR009, SR012 |
| CR043 | Capital and execution risk remain mid-high rather than critical because financing is strong but operational and financial disclosures are incomplete. | Medium | SR013, SR014, SR005 |
| CR044 | Visible mitigations include licensed-IP experiments, a selective partner program, production-workflow tools, and governance frameworks rather than any single regulatory moat. | Medium | SR005, SR006, SR025, SR033, SR034 |
| CR045 | The clearest thesis-break events are a China compliance action, inability to secure frontier GPU capacity, or sustained quality and distribution slippage that blocks enterprise conversion. | Medium | SR015, SR020, SR007, SR009 |
| CR046 | Regulatory friction and infrastructure constraints can transmit into enterprise trust, revenue conversion, margin quality, and ultimately valuation in the same downside pathway. | Medium | SR015, SR020, SR014, SR013 |
| CR047 | The dependency map should center on advanced compute, Alibaba Cloud, app stores, API partners, rights licensors, and creator-tool integrations as the main external nodes. | Medium | SR014, SR006, SR033, SR035 |
| CR048 | The most useful monitoring indicators are CAC and labeling artifacts, GPU-capacity lead times, app-store ratings and downloads, benchmark placement, partner conversions, and disclosed runway. | Medium | SR017, SR020, SR009, SR007, SR006, SR013 |
| CR049 | LexisCN's translated text confirms the 2023 generative-AI rules were jointly issued by seven PRC ministries and took effect on 2023-08-15. | Medium | SR036 |
| CR050 | Regulations.AI's summary of the 2025 labeling measures emphasizes both visible labels and machine-readable metadata or watermark-style identifiers for AI-generated content. | Medium | SR037 |
| CR051 | Comparative AI characterizes the PRC generative-AI interim measures as a departmental rule rather than a higher-level State Council or NPC instrument, underscoring that future policy tightening remains possible. | Medium | SR038 |
| CV001 | Multiple March 2026 reports confirm that AIsphere raised a $300 million Series C and frame it as a record financing event for China's AI-video segment. | Medium | SV001, SV002, SV003, SV029 |
| CV002 | The retained public record supports only a directional unicorn-level AIsphere mark around $1 billion rather than an exact reconciled post-money valuation. | Medium | SV001, SV002, SV003, SV029 |
| CV003 | March 2026 coverage repeated that AIsphere had surpassed $40 million in ARR, more than 100 million users, and more than 16 million monthly active users. | Medium | SV001, SV002, SV003 |
| CV004 | KrASIA reported founder Wang Changhu's statement that PixVerse subscription revenue already covers costs, but the claim is founder-reported rather than audited. | Low | SV004 |
| CV005 | Official product surfaces show PixVerse sells through self-serve credits, larger plans, and enterprise-style packaging rather than through a single free consumer channel. | Medium | SV006, SV007 |
| CV006 | The retained public sources do not disclose AIsphere's exact post-money ownership, liquidation preferences, anti-dilution terms, or side-letter economics. | Medium | SV001, SV002, SV003, SV004 |
| CV007 | If AIsphere's headline mark was roughly $1 billion and ARR merely exceeded $40 million, the implied headline multiple is about 25x ARR or lower because the disclosed ARR figure is only a floor. | Low | SV001, SV002, SV003 |
| CV008 | AIsphere's implied ~25x ARR ceiling is below the roughly ~59x revenue multiple implied by Runway's $5.3 billion valuation on Sacra's $90 million annualized-revenue estimate. | Medium | SV012, SV013, SV014 |
| CV009 | Runway's February 2026 financing re-rated the company to $5.3 billion while the product expanded from AI video into world-model and API workflows. | Medium | SV012, SV013, SV014, SV030 |
| CV010 | Runway is a closer business-model comp than broad AI labs because official and third-party sources show both self-serve video plans and enterprise/API monetization. | Medium | SV011, SV013, SV030 |
| CV011 | Sacra and FirmKnow both place Pika's 2024 valuation at about $470 million after its $80 million Series B, providing a lower-end private AI-video comparison point. | Medium | SV016, SV017 |
| CV012 | Pika's public record still lacks a clean audited revenue base, so the company is useful for valuation bracket context but not for a reliable multiple comparison. | Medium | SV015, SV016, SV017 |
| CV013 | TechCrunch and The AI Rankings say Moonshot raised about $2 billion at about a $20 billion valuation in May 2026, and TechCrunch says ARR topped $200 million in April 2026. | Medium | SV021, SV022, SV023 |
| CV014 | Moonshot's reported valuation implies roughly a 100x ARR multiple on the disclosed >$200 million floor, an upper-bound valuation profile far above AIsphere's surface multiple. | Medium | SV021, SV022, SV023 |
| CV015 | Business Day and WinBuzzer put MiniMax around a $6.5 billion IPO valuation in early 2026, while WinBuzzer says it had only $53 million of first-nine-month 2025 revenue and a $512 million loss. | Medium | SV019, SV020 |
| CV016 | Using WinBuzzer's revenue figure, MiniMax floated at roughly 90x-120x sales depending on whether investors annualize the nine-month run rate, showing how narrative-heavy public AI valuations had become. | Medium | SV019, SV020 |
| CV017 | Startup Wired and Business Day say Zhipu targeted roughly $640 million of IPO proceeds at about a $6.7 billion or HK$51.2 billion valuation. | Medium | SV018, SV019 |
| CV018 | TechCrunch later reported that Zhipu traded at roughly a $55.9 billion market cap and MiniMax at roughly $33 billion after model-driven rallies, showing that debut pricing can materially understate immediate speculative appetite. | Medium | SV022 |
| CV019 | Artificial Analysis leaderboards place PixVerse V6 in the competitive first tier but behind Seedance on text-to-video and inside a tight image-to-video pack with Wan, Kling, and Vidu. | Medium | SV008, SV009, SV010 |
| CV020 | Because the benchmark gaps are narrow and the category is crowded, AIsphere lacks clear evidence of a product lead strong enough to warrant Moonshot-like or even Runway-like premium multiples on quality alone. | Medium | SV008, SV009, SV010, SV011, SV015, SV030 |
| CV021 | Adobe's 2025 filing discloses cost of revenue, operating expenses, net income, and operating cash flow while AIsphere provides no comparable public revenue-quality or cash-flow ledger. | Medium | SV024 |
| CV022 | NVIDIA's 2026 filing emphasizes token-throughput and lower cost per token as core AI economics, underscoring that AI-video value creation depends on compute efficiency that AIsphere does not quantify publicly. | Medium | SV025 |
| CV023 | Snowflake's 2026 filing discloses 125% net revenue retention and growth in $1 million product-revenue customers, metrics absent from AIsphere's public record. | Medium | SV026 |
| CV024 | Datadog's 2025 filing discloses free cash flow and the count of customers with ARR above $100,000, again highlighting the quality markers AIsphere does not publish. | Medium | SV027 |
| CV025 | Cloudflare's 2025 filing details hosting, bandwidth, and support-cost drivers inside cost of revenue, giving a public template for economics disclosure that AIsphere lacks. | Medium | SV028 |
| CV026 | AIsphere's surface multiple looks lower than hot AI peers, but that discount mostly compensates for weaker disclosure, smaller scope, and less proven monetization rather than creating an obvious bargain. | Medium | SV001, SV003, SV012, SV013, SV020, SV021, SV022, SV024, SV026 |
| CV027 | Business 2.0 News explicitly argues that high AI valuations face downward pressure if developer traction fails to convert into enterprise revenue within 12 to 18 months; that logic is directly relevant to AIsphere. | Medium | SV023 |
| CV028 | MiniMax's IPO article shows that investors tolerated large losses despite litigation and export-control risk, which proves public appetite existed but also shows how narrative-sensitive AI valuations can be. | Medium | SV020 |
| CV029 | AIsphere has enough real scale signals—major funding, public pricing, global user claims, and independent benchmark presence—to stay investable rather than avoidable. | Medium | SV001, SV003, SV005, SV006, SV007, SV008, SV009, SV010 |
| CV030 | Absent cap-table and revenue-quality disclosure, the supportable current recommendation is research-more rather than buy. | Medium | SV001, SV002, SV004, SV024, SV026 |
| CV031 | Confidence should remain medium because the valuation direction is plausible, but exact pricing mechanics, ARR quality, and security terms remain under-documented. | Medium | SV001, SV002, SV003, SV004, SV024, SV026 |
| CV032 | Risk should remain high because valuation support depends simultaneously on revenue conversion, compute discipline, and a favorable AI capital-markets window. | Medium | SV012, SV020, SV022, SV023, SV025 |
| CV033 | The valuation stance is stretched rather than outright expensive because the implied ~25x ARR ceiling is below hotter comps, but the underlying ARR floor and term sheet are not strong enough to create a clean margin of safety. | Medium | SV001, SV002, SV003, SV012, SV013, SV021, SV022 |
| CV034 | In a bull case, audited recurring revenue quality, cleaner enterprise/API mix, and sustained first-tier product proof could support a roughly $1.4 billion to $1.8 billion valuation band. | Low | SV007, SV008, SV009, SV010, SV012, SV013 |
| CV035 | In a base case, a roughly $0.85 billion to $1.1 billion band is supportable if ARR proves real but revenue quality and terms stay only partly disclosed. | Low | SV001, SV002, SV003, SV012, SV013, SV016, SV017 |
| CV036 | In a bear case, a roughly $0.55 billion to $0.75 billion band is plausible if paid conversion, enterprise quality, or sector scarcity premiums disappoint. | Low | SV015, SV020, SV023 |
| CV037 | A higher AIsphere valuation than the current implied mark would require an audited revenue bridge, better enterprise/API mix disclosure, and cleaner security terms more than another headline funding round. | Medium | SV004, SV024, SV025, SV026, SV027, SV028 |
| CV038 | A lower entry price would be justified if ARR quality looks weaker than the >$40 million headline, if enterprise mix is thin, or if preference terms materially subordinate new money. | Medium | SV001, SV002, SV004, SV023 |
| CV039 | The cleanest bull signal would be evidence that paid ARR is closer to Runway-like software revenue than to creator-heavy promotional or subsidized usage. | Low | SV013, SV016, SV017, SV024, SV026 |
| CV040 | A next round below the implied unicorn mark or with heavy senior preferences would show that the headline valuation overstated external support or overstated security quality. | Medium | SV001, SV002, SV003 |
| CV041 | Evidence that active paid customers, renewals, or API usage lag the user headline would break the thesis that AIsphere's scale signals deserve premium economics. | Medium | SV003, SV005, SV007, SV024, SV026, SV027 |
| CV042 | If Hong Kong or private-market appetite for Chinese AI cools materially, AIsphere could lose external scarcity support even if company execution remains adequate. | Medium | SV019, SV020, SV022, SV023 |
| CV043 | The most important diligence ask is a monthly bridge from bookings to ARR to recognized revenue by consumer, API, and enterprise channels. | Medium | SV001, SV003, SV006, SV007, SV024, SV026, SV027 |
| CV044 | The second critical diligence ask is the March 2026 cap table, liquidation waterfall, anti-dilution terms, and any investor side letters. | Medium | SV001, SV002, SV003 |
| CV045 | The third critical diligence ask is unit-economics disclosure: compute cost per video minute, gross margin by product surface, and cloud commitments. | Medium | SV007, SV025, SV028 |
| CV046 | The fourth critical diligence ask is cohort evidence such as paid customer count, net revenue retention, churn, and concentration because public comps all disclose analogous quality markers. | Medium | SV024, SV026, SV027 |
| CV047 | Taken together, the retained evidence supports AIsphere as a credible but still under-documented AI-video asset whose company quality may be better than current security visibility. | Medium | SV001, SV006, SV008, SV012, SV021, SV024 |