How tvolodi/letflow works
Letflow is a multi-tenant BPM platform: users define processes, then run and manage definition-driven instances through an HTTP API and a React SPA. The README says the SPA’s API integration is not yet end-to-end, so the graph keeps it separate from the backend rather than implying a working request path. The backend’s engine, definition, and API surfaces are represented alongside documented capabilities such as identity, entities, exam modules, and webhooks. Mobile behavior is described in the README, but its application sources are absent from the supplied tree; only native shell files are shown.
Main entry points: authorized_router.ex HTTP API · main.tsx React SPA · AuthProvider.tsx Web authentication · engine.ex Instance engine
Components 18
User experience
- React SPA
web/src/main.tsx - Web authentication
web/src/auth/AuthProvider.tsx - Tenant OIDC config
web/src/auth/tenantConfig.ts - Process editor
web/src/components/canvas/ProcessCanvas.tsx - Exam experience
web/src/modules/exam/ExamSessionPage.tsx
Workflow backend
- HTTP API
lib/letflow/api/authorized_router.ex - Process definitions
lib/letflow/definitions/process_definition.ex - Instance engine
lib/letflow/engine.ex
Platform domains
- Tenant identity
lib/letflow/identity.ex - Entity records
lib/letflow/entities/records.ex - Exam module
lib/letflow/modules/exam/router.ex - Webhook delivery
lib/letflow/webhooks.ex - Audit trail
lib/letflow/audit.ex
Runtime infrastructure
- Event store
lib/letflow/event_store.ex - OTP application
lib/letflow/application.ex
Other components
- Tenant user
- PostgreSQL
- OIDC provider
Connections 18
- Tenant user → React SPA: uses
README.md - React SPA → Web authentication: mounts
web/src/main.tsx - React SPA → Process editor: renders
- React SPA → Exam experience: routes to
- Web authentication → Tenant OIDC config: resolves config
web/src/auth/AuthProvider.tsx - Tenant OIDC config → HTTP API: requests config
- Web authentication → OIDC provider: authenticates
- Tenant user → HTTP API: calls
README.md - HTTP API → Process definitions: manages
- HTTP API → Instance engine: starts instances
- Instance engine → Event store: records events
- HTTP API → Tenant identity: authorizes tenants
- HTTP API → Entity records: serves records
- HTTP API → Exam module: routes exam
- HTTP API → Webhook delivery: manages deliveries
- Instance engine → Audit trail: audits actions
- OTP application → HTTP API: starts HTTP
- Event store → PostgreSQL: persists