
Storia AI
https://storia.aiOpen source AI copilot that knows your company's code and its context
With AI increasingly automating away code generation, software engineers will spend more time reading, judging, and architecting code rather than writing it. Storia is building an open-source copilot that knows a company's codebase and its context. We are starting with Sage, a Perplexity-like agent for helping developers understand, judge, and generate software. Given an existing codebase, developers can ask Sage questions such as: 1) Given my project’s SLA and latency constraints, what is the appropriate underlying vector database to use? How would I incorporate it into my existing codebase? 2) Why should I pick Redis over Milvus as my underlying vector store? 3) Does this codebase in our organization still work and what steps are required for a complex integration with another library? Sage’s answers are directly supported by documentation and external references like GitHub, Stack Overflow, technical design documents, and project management software, preventing hallucinations. Today, Sage has up-to-date knowledge about open-source repositories (indexed daily). Tomorrow it will have a deep understanding of every line of code on the Internet. For teams, Sage will know about your private codebase too. No group has yet solved how to build an AI system that comprehends a codebase and its context and can empower every developer to architect better code, faster. This requires new research advances because vanilla RAG and out-of-the-box LLMs aren’t going to cut it. We have 20+ years of software engineering and AI research experience. Julia worked on precursors of Gemini using contextual neural techniques before they were called “RAG” (and applied it to products like Google Keyboard and Pixel phones). Mihail built the earliest LLMs at Amazon Alexa and launched the first contextual deep learning conversational AI system in production at Alexa.
Total Open and Closed Positions
Total open positions, and positions newly closed since the previous update
Department Headcount Over Time
Open positions per department · top 6 at any point in the window
Newly Opened and Closed Positions
Position Churn Rate
Positions closed within 14 days of opening · a high rate suggests posting instability — duplicates, pulled listings, or roles filled through internal or off-market channels
Time-to-Fill Distribution
Days from open to close · closed positions only
Salary Trend Over Time
Monthly median base salary · USD · annualized · p25/p75 dashed
Salary Range by Department
Employment Type
Technical vs. Non-technical
Open positions · by department
Top Roles by Department
Seniority Mix
Derived from job title keywords
Equity Range by Department
Top Skills
Top Tech Stacks
Skills Trend
Change in share of postings · recent 3 months vs. prior 3 months
Tech Stack Evolution
Positions opened per month · top 5 technologies