Loading video...
Video Failed to Load
Week 3 of YC. We just made semantic search serverless. Until now, semantic search meant embedding every document, every row and every chunk up front, and paying for it before anyone ran a single search. We flipped that. With Polygres (YC F26) you connect your data, choose what's searchable,... show more
21,992 views • 11 days ago •via X (Twitter)
45 Comments

Sign up for a free account:

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Wtf crazzyy!!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Hehehe

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Week 3 and you flipped the embedding bill. Intern searches refund and that is the whole demo.

@polygres @daltonmeon @damienhe @ycombinator @fdotinc check dms @daleverett

@polygres @daltonmeon @damienhe @ycombinator @fdotinc What’s up?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc sent something 🫡

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Interesting...have a technical write-up somewhere?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Full launch coming in the next few days.

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Looking forward to it!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Fireee

@polygres @daltonmeon @damienhe @ycombinator @fdotinc 🔥 🔥

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Actually insane

@polygres @daltonmeon @damienhe @ycombinator @fdotinc I’m as suprised as you are

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Let's goooo legend

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Lfggg

@polygres @daltonmeon @damienhe @ycombinator @fdotinc how do you handle deltas and do you think it can be used in, for example, notion's semantic search?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc hella good work, Dale. Keep going.

@polygres @daltonmeon @damienhe @ycombinator @fdotinc I have something really interesting to share regarding Polygres

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Dm me!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Dm'ed you

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Turning semantic search into a pay‑per‑query model cuts the upfront barrier. Nice work

@polygres @daltonmeon @damienhe @ycombinator @fdotinc nice seeing a founder from asia!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Hehehe I’m from Singapore!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc i want to use it

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Dm me your polygres email

@polygres @daltonmeon @damienhe @ycombinator @fdotinc sent

@polygres @daltonmeon @damienhe @ycombinator @fdotinc pgGraph 🤯 intriguing, huge utility to a certain size i'd wager then, lose dual benefit of building proper KG for ML of underserved relationships >

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Serverless semantic search: finally, the database bills you only when someone actually asks a question.

Hi Dale! I think flipping semantic search so you pay for tokens only when someone actually searches is the part that changes the economics for sparse corpora. In my opinion, matching embedding-model recall without a neural ingestion pass is the claim that will get stress tested first on messy tables. Where does recall drop first in your internal benchmarks, short fields or long documents?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc looks solid, serverless semantic search could cut costs a lot. how does latency compare on bigger datasets?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc This is awesome, Dale. I’ve already seen Polygres retrieve my past posts, project notes, and visual concepts by meaning. Then help my AI agent connect them into something new. Making that experience serverless, and usage based lowers a huge barrier for builders like me. 🧠

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Thank you! Will give you access asap

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Bullish

@polygres @daltonmeon @damienhe @ycombinator @fdotinc get it brooo

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Heheh

@polygres @daltonmeon @damienhe @ycombinator @fdotinc without embedding anything up front, what does the model actually read when a search comes? If it goes through every row each time, does latency and token cost grow with table size, or is there some cheap index narrowing it down first?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc would love to benchmark this on real world tasks in comparison to our hyrid rag solution! if you arent embedding it upfront based on what are you searching then?

@polygres @daltonmeon @damienhe @ycombinator @fdotinc coming out in about 30 mins :) keep your eyes peeled for our launch video!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Dale lemme try this!!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc I will! Dm me what ur thinking of using it for!

@polygres @daltonmeon @damienhe @ycombinator @fdotinc good stuff

@polygres @daltonmeon @damienhe @ycombinator @fdotinc Hehe

@polygres @daltonmeon @damienhe @ycombinator @fdotinc

@polygres @daltonmeon @damienhe @ycombinator @fdotinc the flip is real, with one inversion: embeddings paid once amortize across every future query, while query-time pays full price on the thousandth search too. right for cold corpora, wrong for the docs your agents hit all day. those queries should materialize, not recompute.
