Who are Chroma's decision-makers?
Chroma is led by Jeff Huber, with technical, product, and go-to-market ownership spread across the leadership team.
- CEO
- Jeff Huber
- CTO/key exec
- Anton Troynikov
- Founded
- 2022
- Employees
- Under 50 estimated
- HQ
- San Francisco, CA
- Notable
- Developer-first embedding database for AI apps
- Jeff HuberCo-founder & CEOCo-founder since 2022Leads company direction and product-market fit for the AI-native database.
- Anton TroynikovCo-founderCo-founder since 2022Works across product, engineering, and the developer community.
- Chroma core teamEngineering leadershipOpen-source maintainersMaintains the Rust, Python, TypeScript, and Go codebase.
- Open-source maintainersCommunity leadershipProject maintainersShape APIs and ecosystem support for RAG builders.
Who leads Chroma?
Jeff Huber is Co-founder & CEO; Anton Troynikov is Co-founder; Chroma core team is Engineering leadership; Open-source maintainers is Community leadership. The founder or CEO usually sets company direction, while technical and product leaders shape build-versus-buy decisions.
Who actually makes buying decisions at Chroma?
Most purchases start with the functional owner rather than the CEO. Engineering owns platform and developer-tool decisions, security reviews risk, finance confirms budget, legal handles terms, and procurement becomes more formal as contract size rises.
How is Chroma organized as it scales?
Chroma is organized around product, engineering, go-to-market, infrastructure, and operations. The right selling motion is to tie the pitch to one team's operating metric instead of sending a generic founder note.
As of June 2026.Sources:Chroma websiteChroma GitHubChroma seed funding release
Chroma — frequently asked questions
