AI-Soda Brain

AI-Soda Brain media kit

AI-Soda Brain is the SODA AI product for understanding enterprise operating data and knowledge. This guide gives the public company and product descriptions, their respective roles and the names to use when referring to them.

How to write the names

Use AI-Soda Brain as the English product name, preserving its hyphen, capitalization and spacing. The Chinese-language site uses the approved Chinese product name. Refer to the company as SODA AI. Distinguish the product from the company when introducing either one.

Short company description

SODA AI focuses on industry applications of AI agents and embodied intelligence. It develops products around enterprise operating data, knowledge and on-site workflows. AI-Soda Brain, inspection robots, AI Employees and OCC each serve a different set of tasks.

Short product description

AI-Soda Brain connects business data and knowledge through natural language. It brings operating questions, metric definitions and sources in text and images into the same inquiry. Evaluation starts with a concrete question and examines the evidence behind the answer, the scope of the data and enterprise deployment conditions.

Quote the evidence accurately

Keep claims about customer numbers, outcomes and certifications within the scope of their supporting evidence. Cite recorded product sessions and synthetic interactive examples according to their respective sources. Neither establishes an unverified customer endorsement. Use official logo files at the original proportions and clarity, preserving their lettering and colors.

Keep the original context with a quotation

An engineering method in a blog post, an example on a scenario page and a formal product specification serve different purposes. Link to the corresponding page so readers can examine the assumptions, scope and verification method and see how the product is described in context.

AI-Soda Brain

Start with your team's first question.

Explore how data becomes an answer, then plan the connections and checks your team needs.

Try “permissions,” “data source,” “manufacturing” or “API.”