Postgres extension for BM25 relevance-ranked full-text search
Last summer we faced a conundrum at my company, Tiger Data, a Postgres cloud vendor whose main business is in timeseries data. We were trying to grow our business towards emerging AI-centric workloads and wanted to provide a state-of-the-art hybrid search stack in Postgres. We'd already built pgvectorscale in house with the goal of scaling semantic search beyond pgvector's main memory limitations. We just needed a scalable ranked keyword search solution too.The problem: core Postgres doesn't provide this; the leading Postgres BM25 extension, ParadeDB, is guarded behind AGPL; developing our own extension appeared daunting. We'd need a small team of sharp engineers and 6-12 months, I figured. And we'd probably still fall short of the performance of a mature system like Parade/Tantivy.Or would we? I'd be experimenting long enough with AI-boosted development at that point to realize that with the latest tools (Claude Code + Opus) and an experienced hand (I've been working in database systems internals for 25 years now), the old time estimates pretty much go out the window.I told our CTO I thought I could solo the project in one quarter. This raised some eyebrows.It did take a little more time than that (two quarters), and we got some real help from the community (amazing!) after open-sourcing the pre-release. But I'm thrilled/exhausted today to share that pg_textsearch v1.0 is freely available via open source (Postgres license), on Tiger Data cloud, and hopefully soon, a hyperscalar near you:https://github.com/timescale/pg_textsearchIn the blog post accompanying the release, I overview the architecture and present benchmark results using MS-MARCO. To my surprise, we were not only able to meet Parade/Tantivy's query performance, but exceed it substantially, measuring a 4.7x advantage on query throughput at scale:https://www.tigerdata.com/blog/pg-textsearch-bm25-fu
FL score
out of 100
Verdict
high confidence
Competition
6
competitors found, emerging market, funded players
Trend
No signal yet
A high-performance, permissively licensed BM25 full-text search extension for Postgres, addressing key pain points of existing complex or restrictively licensed solutions.
The pain
The gap
Build angle
Strengths
- Creator has deep expertise and has already built a highly performant, open-source MVP.
- Addresses a significant and specific pain point with documented user frustrations (Elasticsearch complexity, AGPL licensing).
- Demonstrated superior performance (4.7x query throughput) compared to a leading competitor.
- Clear market gap for a permissively licensed, Postgres-native solution.
- Strong demand signals from internal company needs and general market trends towards simplified data stacks.
- Growing market for AI-centric and hybrid search workloads.
Risks
- Despite performance, convincing users to switch from deeply entrenched systems like Elasticsearch can be challenging.
- Monetization strategy for an open-source project needs careful planning beyond cloud provider partnerships.
- Ongoing maintenance and community management for an open-source database extension can be resource-intensive for a solo builder.
- While the niche is clear, the broader search market is still crowded with well-funded players.
- Dependency on the Postgres ecosystem for adoption and distribution.
Next steps
- Focus on aggressive marketing and education within the Postgres developer community to highlight performance and licensing advantages.
- Explore and formalize various monetization models (e.g., premium support, commercial features, cloud partnerships) beyond just the Tiger Data Cloud offering.
- Actively engage with the open-source community for contributions, feedback, and further validation of features and use cases.
- Create detailed migration guides and comparison benchmarks against more competitors to ease adoption for users currently on other platforms.
Fly Labs Method
Is the pain real, is there a gap, is it the right time, can one person build it.
- Problem clarity
- 28
- Solution gap
- 21
- Willingness to pay
- 20
- Buildability
- 16
Excellent score for a solo builder. The pain is significant and specific, a clear gap exists for a permissively licensed Postgres-native solution, and the founder has already proven buildability and performance superiority.
Value Equation
Dream outcome and how likely it feels, against the time and effort it costs.
High potential for revenue due to strong value proposition, clear differentiation, and a growing market that is actively paying for search solutions.
One-Person Business
Curiosity pull, identity fit, and a path from free value to paid for a solo creator.
Highly suitable for a solo builder given the creator's expertise and the clear problem/solution fit within a reachable niche.
Viral Frameworks
Hook strength, shareability, and how cheaply it can be tested.
Excellent viability as a micro-SaaS, leveraging a strong product, clear value, and existing distribution avenues, with a proven and clear business model.
Builder Lens
Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.
A strong YC candidate with clear demand, a superior solution to a painful status quo, and significant market potential, built by an expert.
Why this verdict
Five lenses, one composite. How scoring works
The angle
This weekend
- Focus on aggressive marketing and education within the Postgres developer community to highlight performance and licensing advantages.
- Explore and formalize various monetization models (e.g., premium support, commercial features, cloud partnerships) beyond just the Tiger Data Cloud offering.
- Actively engage with the open-source community for contributions, feedback, and further validation of features and use cases.
- Create detailed migration guides and comparison benchmarks against more competitors to ease adoption for users currently on other platforms.
Who is already there, emerging market
A distributed, RESTful search and analytics engine capable of solving a growing number of use cases.
Pricing: Elastic Cloud deployments start as low as $16/month for small instances, but production clusters typically run $500-2000+/month. Self-managed deployments have license costs plus infrastructure, often totaling thousands monthly. Enterprise pricing for self-managed solutions can be approximately $12,800 per Enterprise Resource Unit (ERU) per year.
An open-source, typo-tolerant search engine optimized for instant search experiences, designed to be fast, simple, and cost-effective.
Pricing: Typesense Cloud offers hourly pricing, with a minimal setup (0.5 GB RAM) starting around $7/month. A small production setup (4 GB RAM, shared CPU) might cost around $58/month. Larger deployments can exceed $1,000/month.
An open-source, developer-friendly search engine designed for real-time applications, offering speed and relevance without the complexity of Elasticsearch.
Pricing: Meilisearch's transparent pricing starts at $30/month for its Build plan, including 50,000 searches and 100,000 documents. A Pro plan is available at $300/month for 250,000 searches and 1,000,000 documents. It also offers resource-based pricing.
An AI-driven site search platform that enhances user experience with fast, relevant results and machine learning powered ranking.
Pricing: Sajari offers a free plan for up to 20,000 queries and 20,000 records per month on one web domain. Paid plans start from $79/month for 50,000 queries and records, extending to $199/month for 250,000 queries and records with machine learning features and priority support.
A full-text search engine built for Postgres, powered by extensions like pg_search and pg_bm25, embedding a Rust-based Lucene alternative (Tantivy) inside Postgres.
Pricing: Pricing is not explicitly stated on the provided search results, as it's an extension for Postgres. Neon, which offers pg_search, highlights avoiding separate search service costs.
- ZomboDBVisit
A Postgres extension that allows you to create Elasticsearch indexes on your PostgreSQL tables, enabling full-text search and other Elasticsearch features. (Information derived from general knowledge about ZomboDB, as detailed description was not explicit in search results)
Pricing: Not explicitly found in search results. As an open-source extension, core usage is likely free, with potential costs for support or managed services.
What they charge
Recent news
- Top 10 Elasticsearch alternatives and competitors in 2026
Meilisearch Blog, April 09 2025
- Top 10 Typesense Alternatives & Competitors in 2026
G2, April 09 2025
- Elasticsearch Pricing: Worth It or Consider Meilisearch? 2025
Meilisearch Blog, December 10 2025
- Typesense pricing: Is it worth it or consider Meilisearch? October 2025
Meilisearch Blog, December 22 2025
- Comparing Native Postgres, ElasticSearch, and pg_search for Full-Text Search - Neon
Neon Blog, June 13 2025
Market signals
The market for relevance-ranked full-text search, especially within the Postgres ecosystem and for AI-centric workloads, appears to be growing. There's a clear trend towards integrating advanced search capabilities directly into Postgres to simplify architecture and reduce operational overhead, driven by user frustrations with the complexity and cost of external search engines like Elasticsearch. Emerging solutions and recent news indicate an increasing demand for performant, user-friendly, and cost-effective search solutions that can handle modern requirements like hybrid search (combining full-text and vector search).
What frustrates people
- Elasticsearch is complex to set up, administer, scale, and fine-tune, requiring significant effort and specialized knowledge.
- Elasticsearch can have a fragile memory subsystem due to JVM, heap, and garbage collection issues, leading to instability.
- Elasticsearch's schema can be rigid, and dynamic mapping can lead to indexing mistakes and expensive reindex operations.
- Slow queries at scale in Elasticsearch are a common problem without proper optimization and shard distribution.
- Elasticsearch's default security configurations are weak, requiring extra investment and configuration from users.
Semble – Code search for agents that uses 98% fewer tokens than grep
Hey HN! We (Stephan and Thomas) recently open-sourced Semble. We kept running into the same problem while using Claude Code on large codebases: when the agent can't find something directly, it falls back to grep, reading full files or launching subagents. This uses a lot of tokens, and often still misses the relevant code. There are existing tools for this, but they were either too slow to index on demand, needed API keys, or had poor retrieval quality.Semble is our solution for this. It combines static Model2Vec embeddings (using our latest static model: potion-code-16M) with BM25, fused via RRF and reranked with code-aware signals. Everything runs on CPU since there's no transformers involved. On our benchmark of ~1250 query/document pairs across 63 repos and 19 languages, it uses 98% fewer tokens than grep+read and reaches 99% of the retrieval quality of a 137M-parameter code-trained transformer, while being ~200x faster.Main features:- Token-efficient: 98% fewer tokens than grep+read- Fast: ~250ms to index a typical repo on our benchmark, ~1.5ms per query on CPU (very large repos may take longer)- Accurate: 0.854 NDCG@10, 99% of the best transformer setup we tested- MCP server: drop-in for Claude Code, Cursor, Codex, OpenCode- Zero config: no API keys, no GPU, no external servicesInstall in Claude Code with: claude mcp add semble -s user -- uvx --from "semble[mcp]" sembleOr check our README for other installation instructions, benchmarks, and methodology:Semble: https://github.com/MinishLab/sembleBenchmarks: https://github.com/MinishLab/semble/tree/main/benchmarksModel: https://huggingface.co/minishlab/potion-code-16MLet us know if you have any feedback or questions!
AI
Consus (YC F24) – LLM gateway for companies handling sensitive data
Hey Hacker News! I'm Eric, the founder of Consus. We route all AI requests to ITAR restricted and controlled unclassified information (CUI) compliant infrastructure. Consus itself satisfies ITAR restrictions, and we recently completed our FedRAMP equivalency audit against the 410 FedRAMP High controls. FedRAMP High is the U.S. government’s strictest security baseline for cloud services handling sensitive unclassified data. A breach of this data could cause severe or catastrophic harm. Achieving FedRAMP equivalency, or authorization, is required before processing CUI information.Demo: https://youtu.be/6MYxJe6P4oYAerospace and defense is experiencing rapid growth. Unfortunately, most companies are struggling to use AI because of necessary data protections & compliance risk. These companies can move even faster if they could use the AI tools that most other industries take for granted.I spent most of my career prior to Consus in aerospace & defense. I launched national security payloads at SpaceX, and was an early employee at Castelion. I’ve watched first hand how compliance red-tape makes it difficult for companies to adopt new technologies and trust vendors that touch their sensitive data. For example, I worked with a satellite manufacturer that doesn’t allow any AI tools, even for non-sensitive work.Even as AI has become extremely useful over the past 9-12 months, I was surprised by how many aerospace & defense companies refused to touch it. They could see how it could be helpful, but they were scared about model providers training on their data, violating an ITAR rule, or risk losing new business because of a failed cyber assessment. These are all rational fears.There were a lot of ways to solve some/all of these problems, but we focused on building a compliant AI inference layer that can "plug" into any AI tool or workflow. Just as OpenRouter integrates with most tools, Consus can connect to tools like ChatGPT or Clau
AI
GlycemicGPT – Open-source AI-powered diabetes management
I'm a Type 1 diabetic and software engineer. Last year I went months between endocrinologists with no clinician reviewing my data. I'm an engineer, so I built the tool I needed — and now I'm open sourcing it. GlycemicGPT is a self-hosted platform that connects continuous glucose monitors, insulin pumps, and existing Nightscout instances to an AI analysis layer running on your own infrastructure. Data sources:Dexcom G7 (cloud API) Tandem t:slim X2 and Mobi pumps (direct BLE) Nightscout (point it at your existing instance and you're running in minutes)What the AI layer does:Daily briefs summarizing overnight and 24-hour patterns Meal response analysis Conversational chat with RAG-backed clinical knowledge Predictive alerting with configurable thresholds and caregiver escalationImportant: this is monitoring and analysis only. GlycemicGPT does not deliver insulin, does not control your pump, and is not a closed-loop system. It reads your data and gives you insight on top of it. Your clinical decisions stay between you and your care team. Architecture:Self-hosted via Docker or K8S — the GlycemicGPT stack runs entirely on your hardware BYOAI — bring your own AI provider. Use Ollama for fully local operation (no data leaves your hardware), or point it at Claude, OpenAI, or any OpenAI-compatible endpoint if you prefer a hosted model. Data flows directly from your instance to the provider you choose; nothing is routed through any centralized service operated by the project. GPL-3.0, no subscriptions, no vendor lock-inStack:Backend API: FastAPI, Python 3.12, PostgreSQL 16, Redis 7 Web Dashboard: Next.js 15, React 19, Tailwind CSS, shadcn/ui AI Sidecar: TypeScript, Express, multi-provider proxy Android App: Kotlin, Jetpack Compose, BLE Wear OS: Kotlin, Wear Compose, Watch Face Push API Plugin SDK: Kotlin interfaces, capability-based, sandboxedLooking for contributors — especially folks with BLE/Android experience or anyone in the diabetes tech spa
AI
Questions about this idea?
FlyBot reads the scoring and gives you a second opinion on “Postgres extension for BM25 relevance-ranked full-text search”.