Nishkarsh

2.4K posts

Nishkarsh banner
Nishkarsh

Nishkarsh

@contextkingceo

Founder @Hydra_DB

San Francisco Katılım Ağustos 2020
1.9K Takip Edilen7.1K Takipçiler
Sabitlenmiş Tweet
Nishkarsh
Nishkarsh@contextkingceo·
We've raised $6.5M to kill vector databases. Every system today retrieves context the same way: vector search that stores everything as flat embeddings and returns whatever "feels" closest. Similar, sure. Relevant? Almost never. Embeddings can’t tell a Q3 renewal clause from a Q1 termination notice if the language is close enough. A friend of mine asked his AI about a contract last week, and it returned a detailed, perfectly crafted answer pulled from a completely different client’s file. Once you’re dealing with 10M+ documents, these mix-ups happen all the time. VectorDB accuracy goes to shit. We built @hydra_db for exactly this. HydraDB builds an ontology-first context graph over your data, maps relationships between entities, understands the 'why' behind documents, and tracks how information evolves over time. So when you ask about 'Apple,' it knows you mean the company you're serving as a customer. Not the fruit. Even when a vector DB's similarity score says 0.94. More below ⬇️
English
620
641
6K
3.8M
Nishkarsh retweetledi
Composio
Composio@composio·
Your AI agent is only as good as the tools it can actually reach. "If you're building a deep research agent that needs to pull from Notion, we want to make sure all your integrations are sorted first. We loop in the Composio team directly. Shared channels between the customer, us, and Composio." @contextkingceo (founder of @hydra_db) on why the integration layer has to come before the retrieval layer and why @Composio is the first call they make. Full conversation below + on YT and Spotify!
Julia Fedorin@juliafedorin

Vector databases are a scam. Not technically, they do exactly what they say. Return the most cosine-similar string to your query. The scam is the entire industry pretending that's the same thing as relevance. It isn't. Search "Apple." You get the fruit, the company, the watch, and a recipe blog. Your agent picks one at random and calls it retrieval. Your customer calls it broken. Most AI agents shipping right now are duct-taped on top of this. They demo well because demos are easy. They die in production because production is real. @Hydra_db's Founder Nish (@contextkingceo) said the quiet part out loud — "vector databases suck, similarity is not relevance" — and the demo signups haven't stopped since. He raised $6.5M because he was the first to name what everyone in the room already knew. If your retrieval layer is a flat embedding index, you're not building infrastructure. You're building a liability with a prettier name. 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) AI Needs Context (01:30) HydraDB Explained (07:41) Vector Search Breaks (09:32) Messaging That Converts (13:41) Writing the Viral Tweet (16:07) Similarity Not Relevance (20:46) POC to Production Gap (35:35) Raising 6.5 Million Fast (39:33) Founder Lesson on Messaging This is a @Composio "Agents at Work" podcast, where I chat with founders building the next leap of AI. Follow for more:)

English
4
3
14
1.5K
Nishkarsh retweetledi
Julia Fedorin
Julia Fedorin@juliafedorin·
Vector databases are a scam. Not technically, they do exactly what they say. Return the most cosine-similar string to your query. The scam is the entire industry pretending that's the same thing as relevance. It isn't. Search "Apple." You get the fruit, the company, the watch, and a recipe blog. Your agent picks one at random and calls it retrieval. Your customer calls it broken. Most AI agents shipping right now are duct-taped on top of this. They demo well because demos are easy. They die in production because production is real. @Hydra_db's Founder Nish (@contextkingceo) said the quiet part out loud — "vector databases suck, similarity is not relevance" — and the demo signups haven't stopped since. He raised $6.5M because he was the first to name what everyone in the room already knew. If your retrieval layer is a flat embedding index, you're not building infrastructure. You're building a liability with a prettier name. 𝐓𝐈𝐌𝐄𝐒𝐓𝐀𝐌𝐏𝐒 (00:00) AI Needs Context (01:30) HydraDB Explained (07:41) Vector Search Breaks (09:32) Messaging That Converts (13:41) Writing the Viral Tweet (16:07) Similarity Not Relevance (20:46) POC to Production Gap (35:35) Raising 6.5 Million Fast (39:33) Founder Lesson on Messaging This is a @Composio "Agents at Work" podcast, where I chat with founders building the next leap of AI. Follow for more:)
English
47
146
562
169.6K
Harnoor Singh
Harnoor Singh@iHarnoorSingh·
something is cooking when scammers keep spinning up new numbers to impersonate @contextkingceo and DM me on repeat. who's spending this much effort and why?
Harnoor Singh tweet media
English
2
0
6
1.3K
Harnoor Singh
Harnoor Singh@iHarnoorSingh·
this is why @mytechceo hires just Forward Deployed Engineer!! Palantir coined the term FDE to give customer, engineering, end to end ownership of the product now, this is industry standard haha!!
English
11
7
203
28.6K
Nishkarsh retweetledi
Martin Tobias (Pre-Seed VC)
Martin Tobias (Pre-Seed VC)@MartinGTobias·
If you want to fix your agent context. Try @hydra_db
Nishkarsh@contextkingceo

We've raised $6.5M to kill vector databases. Every system today retrieves context the same way: vector search that stores everything as flat embeddings and returns whatever "feels" closest. Similar, sure. Relevant? Almost never. Embeddings can’t tell a Q3 renewal clause from a Q1 termination notice if the language is close enough. A friend of mine asked his AI about a contract last week, and it returned a detailed, perfectly crafted answer pulled from a completely different client’s file. Once you’re dealing with 10M+ documents, these mix-ups happen all the time. VectorDB accuracy goes to shit. We built @hydra_db for exactly this. HydraDB builds an ontology-first context graph over your data, maps relationships between entities, understands the 'why' behind documents, and tracks how information evolves over time. So when you ask about 'Apple,' it knows you mean the company you're serving as a customer. Not the fruit. Even when a vector DB's similarity score says 0.94. More below ⬇️

English
3
1
21
6.3K
Nishkarsh retweetledi
Harnoor Singh
Harnoor Singh@iHarnoorSingh·
Welcoming the VP of SoftBank Vision Fund and Arm! He came through with swag built from his own startup @SpiritStAI We talked about the moats he actually looks for in AI startups, hacker houses or waiting in boardrooms! Thanks @byte721 for the incredible insights and for pulling up to @hydra_db.
English
1
2
35
3.5K
Nishkarsh
Nishkarsh@contextkingceo·
@JayanthSanku01 Hi chief, we’re expanding across multiple roles - can’t seem to DM you. Open to chatting?
English
0
0
2
162
Raghav Gupta
Raghav Gupta@ragsgups·
Grateful to everyone who showed up and made it special. And we’ll have a lot more of these so you all can experience Posha!
English
5
2
33
1.4K
sahil
sahil@interface4AGI·
interfacin’ for the past month @agi_interfaces dropping tmrw!
sahil tweet media
English
23
13
79
3.8K
Rounak
Rounak@RounakLenka·
POV: you start talking to your computer and it actually does what you mean.
English
6
5
92
30.1K
Nishkarsh retweetledi
Harnoor Singh
Harnoor Singh@iHarnoorSingh·
inside Smallest AI office, @kamath_sutra on what's the missing piece for voice agents!! why Lightning TTS, ultra-low latency voice models needs @hydra_db the knowledge and context layer for AI Agents!!
English
10
16
304
32K
Nishkarsh retweetledi
Harnoor Singh
Harnoor Singh@iHarnoorSingh·
the hackathon SF deserves! / build matcha / build code best matcha wins best code wins upto $1000 to be won lots of fun creating matcha art!!
Harnoor Singh tweet media
English
7
5
52
4.6K
daniel wintermeyer
daniel wintermeyer@danwintermeyer·
We raised $3M pre-seed and moved to SF. AI is coming for your job. Maybe in 5 years. Maybe in 15. Nobody knows. But we know this: no great career move ever came from a job board. They came from someone saying “you two should meet.” That’s what @getclera does.
English
100
95
385
244.7K