Shaped

Shaped

The real-time retrieval engine for search, feeds, and agents

5.0
2 reviews

379 followers

Shaped is the real-time retrieval engine for search, feeds, and agents. Connect your data. Train your models. Query text, user or session context and retrieve relevant results in milliseconds. Explore our case studies to see how we’ve helped leading brands drive significant engagement and revenue: https://www.shaped.ai/case-study
This is the 2nd launch from Shaped. View more

ShapedQL

Launching today
The SQL engine for search, feeds, and AI agents
Stop gluing Pinecone, Redis, and Python scripts together. ShapedQL is the SQL engine for relevance - powering "For You" feeds, Search, and RAG memory in minutes. It compiles simple SQL into real-time ranking pipelines that retrieve, filter, score, and reorder results based on live user behavior. Replace thousands of lines of infra with 30 lines of SQL. With native multi-modal embeddings and automated MLOps, ShapedQL helps you build real-time decisions, not just document retrieval.
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
ShapedQL gallery image
Free Options
Launch Team
Anima Playground
AI with an Eye for Design
Promoted

What do you think? …

Tullie Murrell

Hi Product Hunt! 👋

I'm Tullie, the founder and CEO of Shaped. Previously I was a researcher at Meta AI, leading several ML teams including one focused on Instagram Reels and Ads video ranking. I also created PyTorchVideo and was a core contributor to Pytorch Lightning.

We built ShapedQL because we realized that while retrieval has become easier (thanks to Vector DBs), ranking and relevance are still incredibly hard.

Most engineering teams we talk to are stuck maintaining a "Frankenstein" stack. To build a "For You" feed or give an AI Agent personalized memory, they have to glue together a vector database, a feature store (like Redis), a reranking service, and thousands of lines of Python spaghetti code.

We built ShapedQL to turn that "house of cards" into a single interface.

ShapedQL is a domain-specific SQL dialect that compiles down to a high-performance, multi-stage ranking pipeline. With a single query, you can define the four stages of modern relevance:
1. Retrieve: Fetch candidates from multiple sources (Hybrid Search, Collaborative Filtering, Trending).
2. Filter: Apply hard constraints (e.g., "in stock" or "within 50 miles").
3. Score: Rank results using real-time ML models (optimizing for clicks, purchases, or watch time).
4. Reorder: Enforce diversity so your users (or Agents) don't see the same 5 items repeatedly.

We're seeing teams reduce 2,000+ lines of maintenance code down to ~30 lines of ShapedQL, while shipping features like "Cart Upsell" or "Agent Memory" in days instead of months.

If you're not a fan of SQL you can also choose from Python or Typescript SDK's.

I'd love to hear your feedback and answer any questions about the syntax or how it works under the hood! 🚀

mostafa kh

@tullie_murrell the scoring stage. how much control do you have over the ml model? can you bring your own model or is it mostly shaped's built-in ranking?

Yasmeen Collins

@tullie_murrell  @topfuelauto you can choose and configure the ranking/scoring policies, and combine multiple models and objectives into a single score. This includes business logic as well as Shaped’s expansive library of supported model policies (where training, features, and weighting are all configurable). Bring Your Own Model is on the way!

Austin Heaton

@tullie_murrell congrats on the launch. For the retrieve function, can it also rank different sources to decide on the go which source to call? (in cases where you use multiple enrichment providers)

Ryan Thill

Real-time retrieval and ranking tends to break at scale on feature freshness and training serving skew when event volume spikes and backfills happen.

Best practice is strict offline to online feature parity with a streaming fed online feature store plus impression logging for eval and safe shadow or canary rollouts.

How does ShapedQL handle feature definitions and model versioning plus A B testing while keeping low p99 latency across retrieve filter score reorder stages?

Van de Vouchy
Hey Tullie, that Frankenstein stack image is painfully accurate. Was there a specific team you talked to where you saw them drowning in that glue code and thought this is way too complicated for what should be a solved problem?