Welcome to the Thrive Architecture overview.
These pages describe, at a high level, how Thrive’s systems work together:
thrive-fl.org)This site is intentionally overview-focused. For deep technical details (code, schemas, deployment scripts), see the individual project repositories.
Attenders Staff
| |
v v
+----------------+ +-----------------+
| Mobile App | | Admin Tool |
+--------+-------+ +--------+--------+
\ /
\ /
\ HTTPS /
v v
+---------------------+
| Global API |
| (sermons, config) |
+----+-----------+----+
| |
data | | audio
v v
+-----------+ +--------+
| Database | | S3 |
+-----------+ +--------+
|
v
+------------------------+
| AI Processing Pipeline |
| (summary, tags, RSS) |
+------------------------+
|
v
Podcast Platforms
At a glance, here is how a sermon moves from the stage to people’s phones, browsers, and podcast apps:
Sermon is preached
|
v
Audio/Video edited by
production team
|
v
Staff upload via
Admin Tool
|
v
+-------------------+
| Global API |
| (store details & |
| audio location) |
+---------+---------+
|
| triggers / data
v
+---------------------------+
| AI Processing Pipeline |
| • transcript & summary |
| • tags & waveform data |
| • podcast RSS updates |
+-----------+---------------+
|
+---------+-----------------------------+
| |
v v
Mobile App & Website Podcast Platforms
(read enriched data (subscribe to RSS
from Global API) feed)
Use the links below to dive into each part of the system:
Each page is written to be understandable by both technical and non-technical team members.