Rainfall
Product capabilities

See what Rainfall can do with the context behind your work.

Connect the systems you already use, ask questions against captured evidence, and produce documentation or diagrams another person can actually follow.

Start free Compare plans
01

Bring in context

Connect GitHub or Zoho CRM, upload files, or start from a saved template.

02

Ask with evidence

Rainfall selects relevant captured files and metadata for the question you ask.

03

Create usable output

Turn the answer into documentation, a technical handover, or a system map.

Grounded chat

Ask about the system without explaining it from scratch.

Rainfall brings relevant files, pull requests, CRM metadata, uploads, and previous workspace context into the conversation. Answers can cite the captured evidence and clearly separate what is known from what is inferred.

  • File-aware explanations
  • Pull request change context
  • CRM configuration answers
  • Evidence and inference kept distinct
Grounded conversation
What changed in authentication, and what should the handover mention?

Rainfall

The update adds session validation before protected routes enter the workspace. The handover should cover the middleware boundary, unauthenticated redirect, and the entitlement check that follows.

proxy.tsProtected route boundary
PR #42Authentication update
Answer grounded in the latest captured source
Technical handover
Architecture

Authentication and access flow

Protected requests enter through the route boundary, resolve an authenticated user, then verify workspace entitlements before loading product data.

1Request reaches the protected route boundary
2Session identity is resolved
3Plan entitlements determine feature access

Generate docs

Turn the latest context into a handover, not another blank page.

Choose the output you need, then generate a structured draft from the material available in the workspace. Repository handovers include architecture, source inventory, open changes, and coverage notes.

  • Technical handover
  • Repository overview
  • Implementation plan
  • API and integration notes
  • CRM configuration guide
  • Internal operating guide

Visualize systems

Make architecture and workflows easier to see.

Translate source-backed explanations into readable system maps. Use diagrams to show service boundaries, runtime flow, dependencies, CRM automation, or the path a change takes through the product.

  • Architecture maps
  • Runtime and request flows
  • Dependency relationships
  • CRM workflow diagrams

Runtime flow

Source mapped
Request

Route entry

Session

Identity check

Entitlements

Feature access

Workspace

Product data

Integrations

Connected context

Connect apps

Use the systems where the truth already lives.

Connected apps create controlled snapshots for chat, documentation, and diagrams. Refresh a scan when the source changes; disconnect whenever you no longer want Rainfall to use it.

GitHub

Pro

Repository context

Understand a selected repository and its active pull request context without manually pasting files into chat.

  • Select a public or private repository
  • Capture priority source and configuration files
  • Read open pull requests and changed-file summaries
  • Compare added, modified, and removed files between scans
  • Generate source-backed explanations and handovers
Read and explain today. Rainfall does not silently commit, push, or open pull requests.

Zoho CRM

Pro

CRM metadata

Capture the configuration behind a CRM so implementation and operations knowledge is easier to review.

  • Scan modules, fields, layouts, and relationships
  • Capture workflows, rules, functions, and webhooks
  • Explain how CRM configuration fits together
  • Generate audits, implementation notes, and handovers
  • Refresh the metadata snapshot when the CRM changes
Scans metadata for documentation; your CRM data remains under your control.
Connected-app tokens are encrypted and integration requests run on the server.Review security

Templates

Save the structure that already works.

Reuse a proven format for client handovers, CRM audits, API briefs, implementation plans, or internal guides instead of rebuilding the prompt every time.

Technical handover
CRM audit
API brief
Architecture review

Uploads

Add the material that is not in an integration.

Bring requirements, notes, code samples, process documents, and source material into the same workspace before you ask for an explanation or generate a document.

Project context

Files, snippets, notes, and requirements

Start with your own context

Make the next explanation easier to trust and easier to hand over.

Begin with chat and docs. Add connected systems when you need source-backed answers and repeatable delivery workflows.

Start free View plans