Why Jin

Jin exists because FastAPI teams need business-level monitoring inside the app they already run.

Why We Built It

• to catch business KPI drift before customers do
• to keep setup close to the FastAPI response model
• to let teams review issues without shipping data to a separate hosted tool
• to keep observations, baselines, and checks local to the project

Where We Want To Go

• faster model-first setup
• simpler onboarding for new customer projects
• better issue review and explanation flows
• cleaner reports for product owners and leadership
• more automation around setup and change detection, without hiding the underlying data

Product Promise

Jin should stay:

• local
• explainable
• model-first
• useful to product owners and engineers alike