Deployment scope
Describe the site, intended workloads, users, and evaluation period rather than assuming a standard package covers every use.
RAIN / Software
A starting point for discussing pilot scope, deployment responsibilities, software access, and future commercial arrangements.
Commercial scope to define
01 / THE IDEA
RAIN has not published software pricing, license tiers, or production support commitments. A prospective pilot needs an agreed task, deployment boundary, responsibilities, and success criteria before commercial terms can be meaningfully defined.
Describe the site, intended workloads, users, and evaluation period rather than assuming a standard package covers every use.
Identify source ownership, permitted access, operating responsibilities, and how evaluation outputs will be handled.
Discuss assistance during the pilot and what evidence would justify a later production arrangement.
02 / IN PRACTICE
Define the scope, preserve the boundary, and make the outcome something a person can inspect.
Specify the operational question, system boundary, and outcomes the participating team wants to assess.
Identify the access, infrastructure, people, and review effort each participant would provide.
Document any actual engagement separately from the information and planning materials on this website.
03 / A FEW DETAILS
Pricing and license tiers have not been published. Scope, deployment requirements, and support needs would inform a commercial discussion.
No. The website creates a local planning document. It does not submit an order, start a subscription, or establish a deployment agreement.
BUILD WITH RAIN
RAIN is preparing for its first field pilot. Start by defining the environment, the data boundary, and what success should look like.