Hanzo Insights
Product analytics and feature flags
Every event your product emits lands in one place, and the questions you ask of it are the same ones you would ask of a database — funnels and retention when a chart will do, SQL when it will not. The flag that turned a feature on and the recording of someone using it are in that same place, so "did this change work" is one product rather than three.
Autocapture gets you data before you have instrumented anything, and named events get you data you can trust. When a chart cannot express the question, write the query instead — it is the same table underneath.
Paste and ship
Paste this into any agent. It reads the skill manifest and calls Insights from there.
Read https://hanzo.ai/skill.md and use Hanzo Insights in my project.
The flag and the event, in one provider
import { InsightsProvider, useFeatureFlag } from "@hanzo/insights-react"
function App() {
return (
<InsightsProvider
apiKey="ins_proj_xxx"
host="https://insights.hanzo.ai"
>
<MyApp />
</InsightsProvider>
)
}
function MyApp() {
// Feature flags
const showNewUI = useFeatureFlag("new-dashboard")
// Track events
insights.capture("button_clicked", { variant: "primary" })
return showNewUI ? <NewDashboard /> : <OldDashboard />
}20% to the author of the code that runs
Verify that you own a repository, and every org that deploys a project built from it pays you 20% of its metered spend, accrued each period.
Start with autocapture
Drop the provider in and you have data by this afternoon. Name the events that matter once you know which ones those are. There is a free tier, and the whole thing is open source if you would rather run it yourself.