BridgeDP launches Cross-Embodiment Whole-Body Motion Data Factory, filling the data vacuum in motion control
BridgeDP has built a Cross-Embodiment Whole-Body Motion Data Factory, establishing a complete pipeline from motion design, synchronized capture, cross-embodiment retargeting, and data augmentation to training feedback

01 Introduction
We have built a Cross-Embodiment Whole-Body Motion Data Factory, establishing a complete pipeline from motion design, synchronized capture, cross-embodiment retargeting, and data augmentation to training feedback. As a continuously operating infrastructure, the data factory provides data fuel for humanoid robot operating systems, enabling the whole-body motion models within the system to continuously acquire cross-embodiment, trainable, and reusable data assets.
The improvement of model capabilities is increasingly constrained by data. With insufficient data scale, models struggle to cover enough motions; with unstable data quality, models learn incorrect contact relationships and body coordination; without cross-embodiment reusability, training assets must be re-produced whenever robot hardware changes.
For general-purpose whole-body motion models, data is no longer just training material but a critical asset that determines the boundaries of capability.
Based on this pilot and our engineering practice with various legged robots over the past two years, we are moving the data factory from internal validation to formal large-scale construction. It must address how to continuously plan motions, synchronously capture multi-source signals, perform cross-embodiment retargeting, conduct physical validation and data augmentation, and feed training results back into the next production cycle.
This article shares our phased thinking on the motion control data factory: what cross-embodiment whole-body motion data is, why we need a dedicated factory for it, and how the factory should operate internally.
02 What data do we need, starting from motion capabilities?
To answer "what data do we need," we must first answer "what motion capabilities do we want."
For general-purpose whole-body motion models, we want a motion capability that is upward compatible with multimodal action intentions, downward compatible with different embodiment hardware, safe and reliable, and able to continuously evolve in complex environments.
This capability places higher demands on data: models need data that simultaneously preserves whole-body coordination, task intent, contact relationships, environmental context, physical feasibility, and cross-embodiment reuse value.
However, existing data formats, when viewed individually, rarely satisfy these requirements naturally:
Motion capture data can accurately and structurally record human motion states but lacks environmental information and precise human-environment interactions;
teleoperation data is strictly tied to a specific robot embodiment, and its reuse value drops significantly when hardware changes;
first-person video focuses on end-effector and object interactions, failing to fully express the whole-body coordination among torso, lower limbs, center of mass, and contacts;
third-person video shows overall motion but makes it difficult to extract accurate and reasonable human motions. Each of these data types has value, but none alone can support the data loop required for general-purpose whole-body motion models.
Based on this judgment, we define data assets truly intended for training general-purpose whole-body motion models as Cross-Embodiment Whole-Body Motion Data (CWM), requiring CWM to satisfy at least the following four properties:
Cross-embodiment retargetability
: The same motion must be able to produce physically consistent training samples on multiple target embodiments with significant differences in link lengths, joint configurations, mass distribution, and actuation capabilities through a unified processing pipeline. This means the raw data itself must carry sufficient topology and kinematic information to support unified configuration mapping across different embodiments, rather than being locked into the joint space of a specific robot. Robot hardware will continue to iterate; if data serves only one generation of embodiments, it will depreciate along with that hardware. CWM ties data value to human whole-body motion semantics and transferable patterns, allowing a single dataset to be repeatedly utilized across multiple hardware generations.
Whole-body coverage
: Data must completely represent the torso, limbs, hands, fingers, and their coordination, rather than only preserving upper-body end-effector trajectories or lower-body gaits. Real tasks are often not simple concatenations of local actions; for example, "squat to pick up an object—hold it—turn and walk" involves lower-limb support, center-of-mass shift, torso posture, arm extension, finger grasping, and contact switching. Only by recording the coupling relationships among these body parts as a whole can the model learn the coordination patterns among locomotion, manipulation, and posture changes.
Physical feasibility
: A valid data sample must not only be kinematically smooth and reasonable but also be dynamically feasible on the target embodiment, without floating, penetration, slipping, instability, or torque limit violations. This is the hard threshold for upgrading CWM assets from candidate trajectories to training samples.
Multi-source augmentability
: CWM data simultaneously captures human motion, semantic labels, first-person video, third-person video, environmental assets, and object assets at the recording stage, endowing the motion with complete body, task, and scene context. Subsequently, we replay and augment the data in simulation, generating multi-view, multi-scene, and multi-physical-state training samples by customizing camera positions, replacing scene and object texture maps, and collecting whole-body contact forces and motion states.
CWM data satisfying these four properties cannot be obtained through simple capture, which is the starting point for building a cross-embodiment whole-body motion data factory.
03 Why build a data factory?
We have defined what CWM data is, but for model training, merely having "correct" data is not enough; data scale is equally crucial, a consensus already reached in the large model field.
Research on Generalist AI indicates that VLA models also exhibit clear data scaling laws; SONIC has systematically verified on humanoid robot whole-body motion tracking that expanding motion data volume significantly improves motion control capabilities. For whole-body motion control, this means data must cover not just a few standard motions but a large number of continuous motion combinations such as walking, turning, squatting, carrying, grasping, supporting, obstacle avoidance, balance recovery, and contact switching.
According to our internal assessment, training a truly general-purpose whole-body motion model ultimately requires hundreds of thousands of hours of high-quality CWM data; at this scale, small amounts of data have little long-term training value; what truly matters is the ability to continuously expand data scale.
At the same time, data diversity is equally important, because no amount of walking data can train a model that does backflips. The complexity of whole-body motion data lies not just in "more motions are better," but in having the correct data recipe and strict data quality control.
The model needs to see enough motion categories, contact states, task semantics, environmental variations, and target embodiment differences; at the same time, each data sample must undergo cleaning, annotation, retargeting, and physical validation. Otherwise, large-scale data can easily become large-scale noise. Problems such as foot slippage, body penetration, floating, instability, and torque violations are data pollution that directly degrades model quality, causing models to learn incorrect contact relationships, incorrect body coordination, and infeasible control patterns.
This standard also means external data cannot serve as the main source: public motion capture and online videos can supplement, but they are insufficient in quantity and quality to support training of general-purpose whole-body motion models.
Therefore, CWM data production must be designed as an industrialized production system, with capture as only one part. From the moment a motion is designed until it enters the training set, it must also undergo quality inspection, cross-embodiment retargeting, dynamics and simulation augmentation, semantic annotation, and a feedback loop from the model training side.
This production line must simultaneously define data recipes, production processes, and quality standards: which motions must be prioritized, which scenes and contact states are most scarce, which target embodiments need validation, which samples should be discarded, and which data yields the highest training returns—all of these need continuous tracking and feedback. The larger the data scale, the less we can rely on manual experience; the more general the model goals, the more we need reproducible, auditable, and iterable production processes.
This is the core value of the CWM data factory: using stable facilities, equipment, pipelines, professional teams, and quality inspection systems to turn general-purpose whole-body motion data into a sustainable production capability.
Professional motion designers define the motion taxonomy, the capture team handles high-quality synchronized recording, the engineering team manages cleaning, formatting, retargeting, and simulation replay, the algorithm team handles physical validation, training feedback, and data filtering, and the quality inspection team keeps unusable samples out of the training set.
Only such a factory-level system can continuously produce CWM data assets that are large enough, accurate enough, and clean enough, and that can be continuously updated alongside model training and robot iteration.
04 The data factory is not a "capture site" but an "infrastructure"
BridgeDP's Cross-Embodiment Whole-Body Motion Data Factory is a full-process infrastructure centered on producing CWM data assets.
It starts with motion design, clarifying motion categories, contact states, and task scenarios; during capture, it synchronously obtains multi-source data including human motion, video, contacts, environment, and objects; then through cross-embodiment retargeting, physical validation, and simulation augmentation, it transforms raw materials into trainable samples; finally, it uses training feedback to continuously revise the data recipe.

Active coverage: enriching motion diversity
The first question the data factory must answer is "what to capture."A general-purpose whole-body motion model needs to see a continuously expanding motion space that covers the ways the body coordinates. This space cannot be just a pile of motion catalogs; it must be continuously filled along several mutually independent main axes:
- Horizontal expansion of capability dimensions
: Capture plans must be organized by how the body is used, not by motion names. Basic dimensions such as locomotion, posture transitions, limb coordination, contact switching, and object manipulation form the foundation for subsequent complex capabilities. We care about how the body is invoked, how different body parts coordinate, and how center of mass and contacts change, rather than whether a specific motion has been captured.
- Complex terrain, multi-person interaction, and environmental interaction
: These three types of scenarios are the most difficult beyond the basic dimensions and closest to real deployment needs, yet they are most easily overlooked and must be explicitly included in capture plans. Complex terrain changes support and foot placement strategies, multi-person interaction introduces rhythm alignment and spatial negotiation, and environmental interaction deeply couples body motion with objects, contact surfaces, and reachable spaces. They cannot be naturally extrapolated from flat-ground single-person motions and must be explicitly scheduled.
- Subconscious behaviors and free expression
: Scripts can only define task boundaries; real motion contains many unwritten parts: individual movement habits, on-the-spot adjustments, and instinctive responses to unexpected events. Professional motion designers provide intent and constraints during recording while allowing performers space to complete motions in their own habitual ways, so that data covers both task goals and real body variations.
- Motion recovery and failure fallback
: Whether a model can be deployed in real environments largely depends on whether it can stabilize during failures. Therefore, motion recovery must be separately included in capture plans, including rebalancing after imbalance, obstacle avoidance retraction after collisions, and recovery from falls or non-ideal postures. Such samples are typically scarce but directly relate to the model's safety boundary.
Capture diversity also needs explicit management at the source. The diversity of capture personnel and equipment directly affects the diversity and richness of CWM data: performers with different body shapes, ages, genders, and physiques bring differentiated motion postures, joint angle ranges, and center-of-mass control methods; different capture devices (inertial motion capture, optical motion capture, electromagnetic motion capture) differ in accuracy, coverage, wearing constraints, and applicable scenarios, which itself becomes a dimension of the data. Only by incorporating diversity of both personnel and equipment into capture plans can the model avoid learning only "the motion patterns of a certain type of person under a certain type of equipment."
These directions are organized and measured through a continuously updated motion coverage map, recording which combinations have been covered, which dimensions remain sparse, and which samples repeatedly fail after cross-embodiment transfer.
In addition to active coverage based on the map, the data factory explicitly receives data type requirement feedback from the model training side: which motion categories are unstable on which embodiments, which contact states yield the lowest training returns, and which samples passed quality inspection but brought no actual gains—all are translated into new data type requirements written back into the capture plan, so that "what to capture" is continuously calibrated by training results.
To truly convert the above requirements into executable capture tasks, we have built an AI-native data design and recording management platform within the factory, managing motion requirements, coverage map, scene assets, recording plans, data status, and training feedback in a single system.
The platform's core users are a group of full-time professional motion designers; they define motion semantics, break down body coordination, assess performability, and convert whole-body interaction, motion recovery, tool use, and scene tasks into recordable motion plans.
With built-in AI capabilities, the platform assists designers in three ways to produce motion plans:
In generating and expanding motion plans, the platform drafts motion descriptions and performs semantic-level generalization based on coverage map gaps and training feedback, deriving numerous variants along dimensions such as speed, body shape, and rhythm;
In visualizing plans, designers can choose to use AI to generate motion examples directly from text descriptions or keyframes, turning abstract descriptions into demonstrable reference motions;
In diversity review and personnel matching, the platform compares the current batch against the coverage map for distribution biases, alerts designers to over-collected or still-sparse dimensions, and assists in assigning each plan to the most suitable performer and capture equipment based on body shape, age, gender, and physique.
This toolchain closes the loop among the coverage map, designer judgment, and model training feedback within the same system, continuously converting "which motions are already learned stably, which motions have high transfer failure rates, and which scenarios still lack coverage" into production tasks that can be captured, tracked, and fed back.
Synchronized capture: multi-source information synchronized and aligned capture
Synchronized capture of CWM is not merely recording a segment of human motion; it must simultaneously answer four things within the same motion segment: motion intent, body movement patterns, interaction targets, and environment. "Whole-body" means that sub-tasks such as locomotion, manipulation, posture control, and contact changes all hold simultaneously within the same motion segment and cannot be reduced to simple concatenation of torso, hand, and leg trajectories. This inherently requires human motion, video, semantics, and scene to be recorded synchronously. Under current capture specifications, a complete record aims to synchronize the following four types of signals as much as possible, with specific availability depending on the capture scenario and target embodiment.
- Human motion (BVH)
: The primary reference signal for cross-embodiment retargeting, carrying motion semantics, body coordination, center-of-mass changes, and posture transitions. We use different devices for different types of motions:
low-dynamic motions and motions on complex terrain are suitable for inertial motion capture, which is insensitive to site, occlusion, and terrain;
high-dynamic motions are suitable for optical motion capture or higher-precision optical-inertial hybrid devices, which can stabilize joint positions during rapid movements;
fine motions of the hands (grasping, tool operation, button pressing, twisting) are suitable for electromagnetic motion capture, which provides high-precision poses in small spaces.
- Raw video
: Not directly entering the retargeting process, but a high-value auxiliary signal in the data factory: it supports video-based motion completion and human motion extraction, allowing massive internet videos to be incorporated into training assets and preparing visual modalities for navigation and manipulation; it is also used for training SLAM and estimating contact states between humans and objects. Equipment-wise, head-mounted cameras and external RGB/RGB-D cameras capture in parallel, providing first-person and third-person perspectives respectively.
- Scene interaction assets
: Provide the environmental and object context in which motion occurs, a prerequisite for placing motion into simulation.
We collect two types: one is terrain and scene assets—room structures, ground undulations, fixed furniture—which determine reachable spaces and contact surfaces; the other is interactable object assets—objects that are carried, pushed, pulled, or used—which determine target geometry for manipulation tasks.
Technically, we use 3D Gaussian splatting + Mesh extraction for overall reconstruction, and for objects requiring precise poses, we further use optical Marker labeling. After entering simulation, these assets support reinforcement learning training and model evaluation.
- Semantic labels
: Generated collaboratively by professional motion designers, on-site recorders, and AI annotation systems, defining motion boundaries, motion categories, scenes, and intent, determining how each sample enters the training set and how it is sampled, weighted, and evaluated during training.
The reason synchronization is necessary is that the value of whole-body motion lies not in any single modality but in the correspondences among different modalities. For the same "squat to pick up an object" motion, human BVH only shows how body posture changes; video shows where the object is and whether the hand actually makes contact; scene assets show the environment and interactive surfaces; semantic labels show motion boundaries and task intent. If these signals are not aligned, we cannot determine which frame's object contact corresponds to a hand trajectory, nor whether foot force matches the current posture, nor verify whether this motion can truly enter the training set.
To this end, the data factory establishes a unified capture clock and timestamp system for all capture devices: all devices complete spatial calibration and time synchronization before capture; during capture, the master control system uniformly manages task IDs, motion IDs, device status, and start/end signals; devices that support hardware synchronization prioritize using trigger signals, frame sync, timecode, or PTP for alignment, while devices that cannot hardware-sync record high-precision local timestamps and perform time synchronization correction through synchronized motions, calibration events, or post-processing algorithms.
After synchronization, each data sample must be organized into an asset that can directly enter the downstream pipeline; this work is also handled by the aforementioned recording management platform.
The platform performs on-site automatic quality inspection—checking time synchronization, calibration, trajectory completeness, bone length stability, keypoint anomalies, and motion segment boundaries, with AI assisting in checking motion semantics, performance consistency, and obvious recording anomalies—and unified ingestion—packaging all modalities under the same motion segment into a unified data package, binding session, device status, calibration version, time offset, frame loss, and quality inspection results, and completing alignment, resampling, and slicing based on the master clock, forming a minimal data contract that can directly enter retargeting and training pipelines.
Cross-embodiment retargeting: retargeting to robots of multiple configurations
The core solution to heterogeneity is motion retargeting: converting a motion in the coordinate system of a human or a reference embodiment into trajectories on a target robot embodiment. In industrialized production, the difficulty is no longer just "can we transfer a motion to a robot," but whether we can do so continuously, stably, and at low cost across a large number of motions and embodiments.
At the algorithm level, our self-developed retargeting engine targets "any motion × any robot model × any terrain."The input side covers arbitrary motions, upper-body/lower-body/whole-body, can process offline motion capture files and real-time motion capture streams, and supports motion signals from different sources such as video; the output side covers legged, humanoid, upper-limb, and composite-configuration robots with significant differences in structure, joint configuration, scale, and actuation capabilities, and can incorporate terrain constraints such as flat ground, slopes, stairs, and uneven ground into unified solving, without needing a separate set of dedicated solving logic for each motion, each robot, or each terrain type. The solver, based on kinematic solving and geometric constraints, integrates contact states, support relationships, spatial constraints, terrain constraints, joint limits, and body interaction relationships into a single solving process, outputting candidate trajectories that are semantically consistent, structurally reachable, and stably high-quality.
At the engineering level, it has three advantages that directly serve factory production.
First, no per-item parameter tuning and no motion templates: the cross-embodiment capability comes from a unified embodiment abstraction layer—when a new robot is integrated, we rely only on its URDF definition; the algorithm can automatically and quickly adapt to multiple configurations on this abstraction layer, without writing dedicated solving logic for each motion or robot, and without manual fine-tuning per motion.
Second, dual modes of streaming and offline: it can digest real-time motion streams from the capture side and batch-process existing motion libraries; this makes retargeting no longer an offline step of "process after capture," but enables retargeting while capturing—as soon as a motion is recorded, candidate trajectories on the target embodiment are already available, and quality inspection and subsequent dynamics augmentation can be connected immediately. In streaming mode, our retargeting tool supports output data from various devices such as Noitom and Xsens.
Third, cross-platform stable distribution: from engineering sites, capture scenes, and training clusters to target robot sides, it can be deployed and replayed consistently, ensuring the motion flow is based on the same algorithm implementation throughout the production chain.
At the capacity level, it is already the factory's main production service. Under current statistics, this retargeting algorithm can exceed 1000 frames per second on a single CPU core, about more than ten times the typical recording frame rate; we have prepared a computing cluster for this pipeline to continuously digest motion streams from the capture side and support parallel distribution of the same motion to robots of multiple configurations. In production terms, it compresses the hidden cost of "manual adaptation per motion" into a one-time engineering calibration when integrating a new embodiment, and reduces the "capture → retargeting → candidate training sample" pipeline time from days to near real-time.
The same human dance motion is retargeted across embodiments and mapped to multiple different robot bodies; some classified embodiments have been blurred. This effect is achieved without manual parameter adjustment or additional configuration of the algorithm.
Data augmentation: dynamics, simulation, and AI annotation augmentation
Cross-embodiment retargeting outputs high-quality candidate trajectories, but candidate trajectories are not yet final training assets. Data augmentation continues to transform these candidate trajectories into data that is more verifiable, more trainable, and easier for models to consume. We proceed along three main lines: dynamics augmentation, simulation diversity augmentation, and semantic annotation.
Dynamics augmentation places the most valuable, most difficult, and most physically demanding samples into the target embodiment's dynamics and contact models, using RL dynamics post-processing to simultaneously control tracking error and physical violations, upgrading candidate trajectories from "kinematically resembling" to "trackable on the target embodiment without penetration, torque violations, or friction cone violations." Samples judged infeasible enter quality feedback with specific failure reasons, rather than being discarded outright.
Simulation diversity augmentation repeatedly executes the same motion in different virtual environments, exponentially amplifying the coverage density of CWM assets.
On one hand, it fills missing modalities: through physical simulation and rendering pipelines, it supplements samples originally captured with only motion and video with modalities such as mechanical signals, depth maps, semantic segmentation, and multi-view images that were not originally captured;
on the other hand, it expands visual and scene diversity: replacing texture assets of objects and environments, adjusting materials and lighting, changing room layouts, introducing new interactive objects and initial states, and applying external force perturbations of different directions and intensities. The same motion can generate a large number of new samples across multiple target embodiments, multiple scene sets, multiple lighting conditions, and multiple perturbation conditions, so that the model sees not "one way to do this motion" but "a distribution of ways to do this motion."
Semantic annotation turns data into assets that can be retrieved, weighted, filtered, and reused by training pipelines. The AI annotation system assists in generating labels such as motion slices, motion categories, contact states, scene objects, task semantics, failure reasons, and capability dimensions, while professional motion designers review semantic boundaries and key samples, converging annotation outputs into a standard format usable for training sampling and evaluation bucketing.
The three types of augmentation share the same version and provenance record: each augmented sample is marked with which original motion it came from, which target embodiment, which dynamics post-processing, which simulation augmentation round, which annotation version, and whether it passed physical validation. This allows the training system to safely reuse, compare, and roll back augmented samples across different versions, and quality feedback can pinpoint specific augmentation stages when problems arise.
After cross-embodiment retargeting (green markers), dynamics augmentation produces dynamics-consistent high-quality data (red markers). Slippage, penetration, and floating are significantly reduced.
Quality feedback: feeding model training results back into the production system
Traditional motion capture quality inspection mostly checks whether trajectories are clean; the CWM data factory's quality management takes two steps: first, layered inspection along the production chain; then closed-loop feedback using model training results.
The first step is layered inspection. A sample, from motion requirements to the training set, must sequentially pass four independent quality inspections. Together, these four layers filter a candidate sample into an asset that can enter the training set, but whether it can truly train general-purpose whole-body motion capabilities can only be told by the model.
- Design layer:
whether the motion requirement truly aligns with capability gaps, covers still-sparse cells in the motion coverage map, and can be translated into on-site executable motion plans. This layer controls "should it be captured."
- Raw data layer:
whether the performer fully expressed the design intent, whether capture was synchronized, calibration was in place, and whether there were basic recording issues such as frame loss/drift/keypoint anomalies/bone length instability. This layer controls "was it captured correctly."
- Retargeted data layer:
whether candidate trajectories are structurally reachable on the target embodiment, joints are within limits, contact relationships hold, and motion semantics remain intact after retargeting. This layer controls "does it still hold after transferring to the target embodiment."
- Augmented data layer:
whether after dynamics post-processing it remains trackable, without penetration, torque violations, or friction cone violations; whether simulation augmentation and semantic annotation carry correct version and provenance records. This layer controls "is it truly effective in the training set."
The second step is result closed-loop. The training side aggregates every model evaluation result—such as which motion categories are stably learned on which embodiments, which transfers failed, which contact states yielded the lowest training returns, and which samples passed all four layers of inspection but brought no actual gains—into a writable failure profile: on which embodiment, which motion category, which contact state, and under which training version the problem occurred, attributing the problem to design, raw capture, retargeting, or augmentation.
The failure profile is directly written back to every upstream layer: the design layer adjusts the motion coverage map priorities and recording plans accordingly; the raw data layer adjusts capture specifications, synchronization strategies, and on-site quality inspection thresholds; the retargeting layer iterates algorithm capabilities; the augmentation layer adjusts dynamics post-processing intensity, simulation diversity configurations, and annotation standards.
Combining the two steps, the data factory forms a continuously iterating closed loop. In actual operation, it advances along two parallel lines: one line is active coverage based on long-term judgment, continuously expanding the human whole-body motion library according to the motion coverage map; the other line is feedback gap-filling from the model training side, backfilling every upstream layer according to the failure profile. With each round, the quality of data assets, cross-embodiment coverage density, and training returns all rise together: more accurate and faster with each round is the core source of compounding returns for the CWM data factory over time.

05 Final words: the current status and future of our data factory
Over the past three months, we have run through the end-to-end chain of the cross-embodiment whole-body motion data factory in an internal pilot. The goal of this phase was not to pursue maximum capacity but to truly operationalize the entire production system: whether motion design can be systematically managed, whether multi-source capture can be stably aligned, whether retargeting can quickly adapt to new embodiments, whether augmentation and quality inspection can turn candidate trajectories into trainable assets, and whether training feedback can return to the next production cycle.
Along this chain, we have cumulatively produced nearly a thousand hours of high-quality CWM data; the whole-body motion model trained with this data ultimately completed key validation on over ten legged robots with significant differences in structure, actuation performance, mass distribution, and inertia distribution.
Now, this solution has completed internal feasibility validation, and the data factory is about to complete formal construction. The focus of the next phase is to shift from pilot validation to large-scale production—simultaneously expanding the site, capture studios, motion capture equipment, motion design team, performer roster, and algorithm/simulation/training computing clusters, so that the production line proven earlier can operate stably at a larger scale.
Our goal after the new factory is operational is to achieve a monthly output capacity of thousands of hours of high-quality CWM data for multi-configuration robots, and to climb in stages from "thousands of hours to tens of thousands of hours"; in this process, data quality, cross-embodiment reuse rate, and training gains will be continuously assessed under the same production standards, so that each new batch of data can answer how many embodiments it can run on and which motion categories it contributed real training gains to, rather than just "how many hours were captured."





界面新闻
深视新闻
深圳特区报
财新
36氪
钛媒体
中国新闻周刊
蓝鲸新闻
Z Finance
投资家网
雷峰网
亿欧
环球网
南方日报
极客公园



