A100 Compute Box 1ch M.2
The A100 Compute Box 1ch M.2 is a single-channel M.2 module carrying DeepGrid's SoC2 die, the lowest-cost entry point into the platform at ₹85,000, designed to drop into a customer's existing carrier board without requiring them to design hardware around a bare die. At 89% gross margin and a management-projected ₹25.5 Cr by FY2032, it is the widest top of the compute funnel and the cheapest way any customer can adopt DeepGrid perception.
- Listed price
- ₹85,000
- FY2032 revenue
- ₹25.5 Cr
- Share of plan
- 2.3%
- Gross margin
- 89%
- First revenue
- FY2028
- Volume plan
- 3,000 @ FY32
From input to outcome
Proposed product architecture. The scene illustrates its application, not a shipped kit.
One camera feeds the customer's carrier board
The M.2 module runs their model on the SoC2
Results return over the bus to their application
Their product acts on the output
Drag to rotate. Conceptual layout, not a mask.
On the die
The case in brief
- At ₹85,000 and 89% gross margin, the A100 Compute Box 1ch M.2 is the lowest-friction, lowest-cost entry point into DeepGrid's SoC2 platform, designed to convert integrators who cannot design around a bare die into paying customers.
- Management projects ₹25.5 Cr in FY2032 revenue at 89% gross margin from 3,000 units, representing 0.20% capture of a $4.8B (2025) addressable pool, these are management assumptions against third-party pool estimates.
- Every unit depends on the SoC2 tapeout completing on schedule; first revenue is FY2028, and the module shares this single gate with all other FY2028 SKUs across the portfolio.
What it is used for
Integrator prototyping
- Buyer
- Integrators prototyping single-camera products
- The job
- Product teams need to evaluate DeepGrid's SoC2 and toolchain without committing to a full board design around a bare die, which requires hardware engineering resources they may not have.
- What DeepGrid supplies
- An M.2 module carrying the SoC2, an SDK and model toolchain, and reference carrier documentation that lets the integrator self-serve the design-in into their existing enclosure and sensor.
Single-camera product build
- Buyer
- Integrators building genuinely single-camera products
- The job
- Customers building products that require exactly one camera channel of perception need a compute module sized and priced for that scope, not a multi-channel board they cannot fully utilise.
- What DeepGrid supplies
- One camera feeds the customer's carrier board; the M.2 module runs their model on the SoC2; results return over the bus to their application, which then acts on the output.
AEBS forward-path perception
- Buyer
- Tier-1 ADAS system engineer, functional-safety manager, OEM chief engineer
- The job
- AIS-162 / IS 11852:2019 under CMVR Rule 96(12) obliges M2/M3/N2/N3 vehicles to carry AEBS with a warning issued at least 1.4 s before braking and no emergency phase before TTC 3.0 s, a perception budget the Tier-1 must satisfy.
- What DeepGrid supplies
- Detection, classification, tracking and per-target TTC on a documented interface with confidence and sensor-health state; actuation, calibration, homologation and warranty remain with the Tier-1.
The story
The A100 Compute Box 1ch M.2 is an M.2 module carrying the SoC2 die, the cheapest way to adopt DeepGrid perception without designing a board around bare silicon.
Priced at ₹85,000, the module packages the same SoC2 die used across the portfolio into an M.2 form factor that drops into a customer's existing carrier board. It ships with an SDK and model toolchain and reference carrier documentation, so an integrator can complete a design-in without hardware engineering support from DeepGrid. It sits at the widest top of the compute funnel: the entry point for customers who want the platform but not the board-design commitment.
- ₹85,000Unit price
- SystemsSegment
- ComputeOperating domain
- FY2028First revenue
- M.2 SoC2 moduleComponent 1
- SDK & model toolchainComponent 2
One camera in, one perception stream out, the SoC2 runs the customer's model on the M.2 module and returns results over a standard bus interface.
The signal chain has four stages: one camera feeds the customer's carrier board; the M.2 module runs the customer's model on the SoC2; results return over the bus to their application; and their product acts on the output. Because the customer already owns the enclosure and the sensor, the integration surface is narrow, the M.2 interface and the software toolchain. That self-serve model makes toolchain quality and documentation the primary technical dependency, not hands-on hardware support from DeepGrid.
- One camera channelInput
- SoC2 on M.2Compute element
- Standard bus interfaceOutput path
- Customer's carrier boardHost hardware
- Toolchain & documentationKey dependency
Integrators prototyping or building single-camera products buy this module to access the SoC2 platform without forming a hardware team.
The target buyer is a product team that wants the silicon and toolchain but cannot justify designing a board around a bare die, the module converts what would otherwise be a semiconductor sale into a self-serve design-in. The channel is direct and through electronics distribution. The ADAS mandate creates near-term demand pull among Tier-1 integrators seeking perception-capable compute for existing enclosures.
- Integrators & prototypersBuyer
- Direct & distributionChannel
- No board-design teamPurchase trigger
- $4.8B (2025)Pool size (3rd party)
- 0.20% at FY2032Capture rate (mgmt. proj.)
At ₹25.5 Cr and 89% gross margin by FY2032, the module is a modest but high-margin funnel entry that pulls customers toward higher-channel SKUs.
Management projects 3,000 units in FY2032 generating ₹25.5 Cr, equal to 2.3% of group revenue, at an 89% gross margin, these are management projections. Its portfolio role is explicit: the lowest-cost adoption path, designed to bring in customers who would not buy at all without a module option, and to migrate them toward higher-value SKUs over time. The critical gate shared with all FY2028 SKUs is the SoC2 tapeout; no silicon means no module and no first revenue.
- 3,000 unitsFY2032 units (mgmt. proj.)
- ₹25.5 CrFY2032 revenue (mgmt. proj.)
- 2.3% of groupRevenue share (mgmt. proj.)
- 89%Gross margin (mgmt. proj.)
- SoC2 tapeoutGating dependency
- Funnel entry pointPortfolio role
- ₹0 CrFY270 units
- ₹1.6 CrFY28188 units
- ₹3.19 CrFY29375 units
- ₹6.38 CrFY30750 units
- ₹12.75 CrFY311,500 units
- ₹25.5 CrFY323,000 units
What has to go right
The single most critical dependency is the ASIC tapeout: no SoC2 silicon means no module, and all nine FY2028 SKUs share this gate. Because the buyer self-serves, toolchain quality and documentation must be sufficient for an integrator to complete a design-in without hands-on support from DeepGrid, a failure here raises support costs and slows adoption. For the AEBS use case specifically, a braking Tier-1 must accept the perception interface, diagnostics, safety assumptions and validation plan in writing with a recorded go/no-go, and no published ISO 26262 pathway yet exists, meaning an assessor must be engaged before the integrator can compare DeepGrid against a certified incumbent. Capital release is conditioned on partner access, field telemetry and a primary qualification artifact clearing together.
Key dependency ASIC tapeout.
Further reading and viewing
Watch
The A100 Compute Box 1ch M.2 in the narrated walkthroughOne silicon. The full story. From 17:07Read
The A100 ADAS SoC on the SoC2 dieTechnology: six domains, one tapeoutCommercial use case UC-01AEBS forward-path perceptionInvestment memorandum: Use casesWhat Deepgrid sells, and what it does notFinancial Model v3 (Sept 2026), workbookSheet: Revenue BuildPortfolio deck, slide 6The portfolioPortfolio deck, slide 99SequencingAsk DeepGrid about the A100 Compute Box 1ch M.2Any question, answered from the same documentsRelated products
Prices, volumes, revenues and margins are management projections. The text is written from the linked documents, and every figure in it appears in the source it came from.