Skip to content

Atram, Yaya, FSP, and Rada Vocabulary

Atram is a climate-finance company that delivers AI-powered weather alerts and financial guidance to financially vulnerable users in emerging markets, over WhatsApp, SMS, Telegram, and a whitelabel PWA [@business-md]. Yaya is the product name for that experience; Yaya Engine is this repository, the Laravel application that acts as the system of record and central orchestration layer for users, FSPs, and message dispatch, which most other Atram services treat as authoritative [@business-md]. Distribution to end users runs mainly through FSP partner institutions — banks and microfinance lenders that already serve the target population — with "Atram" itself standing in as a fallback FSP for users who have no partner bank [@business-md]. A separate but related system, Rada, owns the weather-detection and alert-composition side of the product and currently lives partly outside this repo [@rada-codebase-md]. Together these five terms — Atram, Yaya, Yaya Engine, FSP, Rada — describe who runs the product, what the product is called, where its code lives, how it reaches users, and how it decides what to alert them about.

Atram and Yaya

Atram is the company. Yaya is the product: the chatbot conversations, the PWA, and the alerting pipeline that Atram's financially vulnerable users interact with directly [@business-md]. The distinction matters because Atram operates more than one system under its umbrella — Rada is a sibling system focused on weather data rather than user conversations — and "Yaya" specifically names the user-facing alert-and-guidance product that this repo implements.

Yaya Engine vs. Yaya Manager

Within this repository, "Yaya Engine" and "Yaya Manager" name two different things, and conflating them causes confusion when reading code or docs:

  • Yaya Engine is the whole repository: a Laravel 12 application that holds users, FSPs, dispatches messages, and orchestrates the AI conversation layer [@business-md].
  • Yaya Manager is the Inertia + React ops console mounted inside this same repo at /manager, used by the ops team (via WorkOS SSO) for workflow-focused tasks such as reviewing verification evidence, distinct from the Filament /admin panel used for direct data management [@project-md].

Both live in the same codebase, but "Yaya Engine" refers to the whole system while "Yaya Manager" refers to one specific frontend inside it.

FSP (Financial Service Provider)

An FSP is a partner institution — typically a bank or microfinance lender — that distributes Yaya to its own customer base, and functions as this repo's multi-tenancy unit: every user belongs to exactly one FSP, and FSP membership drives branding, channel routing, and admin scoping [@business-md]. Fortune Credit (Kenya) and Bancamía (Colombia) are live or piloted FSPs; "Atram" itself is always available as a fallback FSP for direct, partner-less users, such as the FSP-less Ethiopia pilot [@business-md]. The mechanics of FSP scoping — branding, per-FSP channel config, and query filtering — are covered in FSP as a multi-tenancy concept.

Rada

Rada is the weather- and alert-side of the system: it ingests weather data per town or gauge, converts it into severity levels, schedules alerts against affected users, and composes localized messages, historically across a set of sibling repos (rada-weather, rada-message-system, alert-manager) that read and write a separate Supabase Postgres database rather than this repo's own database [@rada-codebase-md]. Yaya Engine's role in that pipeline is to receive composed messages and dispatch them through the channel-agnostic messaging system, and to push user records into Supabase so Rada's downstream consumers can target users for alerts [@rada-codebase-md]. An in-flight migration, referred to as "Rada v2," plans to collapse that separate Supabase database into Yaya Engine's own Postgres database, removing the two-database split described above [@rada-codebase-md].