How Lucrum works under the hood.
A multi-agent AI system built on AWS, designed for personal, safe and fast conversations at scale.
- AWS
- Amazon Bedrock
- Amazon OpenSearch
- LangGraph
- NeMo Guardrails
- Llama
- Mistral
Architecture
Every message passes through the safety layer before and after the model responds.
Specialized agents, one conversation
Onboarding agent
Runs the first conversation, captures goals and routine, and sets the starting plan.
Conversation agent
Handles everyday chat, using memory and recent check-ins for context.
Program agent
Builds and adjusts programs based on progress, mood and schedule.
Insights agent
Turns check-in data into weekly patterns explained in plain language.
The right model for each job
Production conversations run on foundation models through Amazon Bedrock. In parallel we fine-tune open models (Llama and Mistral, 7B to 13B parameters) on curated wellbeing dialogue for tone, empathy and safety, and route each task to the model with the best quality, speed and cost.
Personal, private memory
Key facts from conversations are summarized and stored as embeddings in an Amazon OpenSearch vector index. The companion retrieves only what is relevant to the current conversation. Users can view and delete their memory at any time.
How did the presentation on Thursday go?
Better than expected. The walk before helped.
Safety pipeline
- 01Message inFrom the app
- 02Safety checkNeMo Guardrails + crisis detection
- 03ModelOrchestrated by LangGraph
- 04Safety check outBefore the reply
During the beta, our team reviews every flagged conversation to improve how Lucrum responds.
Built on AWS
| Layer | What we use | Why |
|---|---|---|
| Models | Amazon Bedrock; fine-tuned Llama and Mistral (7B to 13B parameters) | Managed access to foundation models; open models tuned for tone, empathy and safety |
| Orchestration | LangGraph | Coordinates the specialized agents in one conversation |
| Memory | Amazon OpenSearch Service | Vector memory and search |
| Compute | GPU instances | Fine-tuning and low-latency inference |
| Safety | NeMo Guardrails | Checks every message before and after the model responds |
| Data | HIPAA-eligible services | Encryption by default; infrastructure that scales from beta to public launch |
Our next 12 months
- Fine-tune and evaluate our own wellbeing models on GPU instances
- Cut response latency for a natural chat feel
- Expand safety evaluation with red-teaming and human review
- Launch voice check-ins