Kwilo Docs¶
The single place to understand how Kwilo works, for a new PM, a new engineer, or anyone who needs the why behind a feature without reading code.
How this hub is organized¶
The hub follows the product's own shape: the system first, then the two kinds of users.
| Section | What it answers | Start here if you are... |
|---|---|---|
| Architecture | What are the moving parts and how do they fit together? | New to Kwilo entirely |
| B2B: Institutions | How does a college / corporate use Kwilo end to end? | Working on faculty, courses, grading, attendance |
| B2C: Consumers | How does an individual learner go from signup to paying? | Working on signup, freemium, pricing, study plan, chat |
| Platform & Compliance | Auth, cookies/DPDP, shared primitives | Working on cross-cutting concerns |
How to read a flow¶
Every section opens with a one-screen diagram and a plain-English walk-through, then links to the detailed feature docs underneath. Read the overview to get the shape; open a feature doc when you need the specifics.
What's a flow vs a feature doc?
An overview/flow page is written for someone seeing it for the first time: short, visual, no jargon without a gloss. A feature doc is the concise working reference: what the feature is, who uses it, and how it works. Both matter; start with the flow.
The one-line model¶
Kwilo is B2B2C: the same product serves institutions (colleges, corporates) and individuals (learners, trainers, parents). One backend, one product app, two go-to-market motions.