Signal volume
Count the measurements a use case actually requires and describe their cadence. Equipment count alone is not a capacity estimate.
RAIN / Hardware
Choose the scope before the specification.
RAIN Node, Mini, and MAX describe intended deployment directions. Use the comparison to frame a workload discussion, not to select a shipping SKU.
Proposed lineup
INTELLIGENCE BELONGS WHERE THE DATA LIVES.
01 / THE IDEA
An honest starting point for sizing.
There are no finalized specifications or published benchmarks for these configurations. The comparison below separates intended scope from decisions that still need measured evidence. Every direction preserves the same principle: local intelligence with a read-only operational boundary.
Model workload
Distinguish routine inference from retraining and evaluation. These jobs can have different timing and resource demands.
Site constraints
Installation, maintenance access, network boundaries, and retention policies can shape the configuration as much as computation.
02 / IN PRACTICE
Put the thinking into practice.
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
- 01
Describe the job
Write down the operational question, relevant signals, and the person who will use the output.
- 02
Measure the demands
Use representative data and model workloads to establish compute and storage requirements.
- 03
Agree the pilot scope
Choose equipment only after the workload and site constraints are understood, with explicit validation criteria.
| Planning question | RAIN Node Mini | RAIN Node | RAIN Node MAX |
|---|---|---|---|
| Intended scope | A focused signal set and question | A scoped site learning loop | A broader combination of local workloads |
| Workload to characterize | A narrowly defined model task | Inference, learning, and operator review | Concurrent model jobs and retained history |
| Compute and storage | To be defined from measurements | To be defined from measurements | To be defined from measurements |
| Physical configuration | Not finalized | Not finalized | Not finalized |
| Availability and pricing | Not announced | Pilot scope to discuss | Not announced |
03 / A FEW DETAILS
Worth understanding.
Which model should I buy?
These are proposed configurations, not an available catalog. The useful next step is to establish your workload and discuss a pilot.
Will all three configurations become products?
The lineup remains a product direction. Pilot evidence will inform the final configurations and any availability decisions.
BUILD WITH RAIN
One site. One question.
A useful next step.
RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.