106 points by kingcauchy 4 days ago | 43 comments | View on ycombinator
thefogman 4 days ago |
neilsharma425 3 days ago |
Curious about resource contention though: if a heavy indexing job saturates Termite, does that affect query latency on the Raft side? And how does Termite handle model cold starts in single-process mode?
On the license: the ELv2 framing is honest and the "can't offer as managed service" carve-out is pretty standard at this point. Won't bother most people reading this.
KnowFun 3 days ago |
derodero24 2 days ago |
perfmode 4 days ago |
Comment on the Pause method indicates that waits for in flight Batch operations (by obtaining the lock) but Batch doesn’t appear to hold the lock during the batch operation. Am I missing something?
schmichael 4 days ago |
prosdev 4 days ago |
Linell 4 days ago |
undefined 4 days ago |
SkyPuncher 4 days ago |
I've seen it on a few products and it doesn't click with me how people are using it.
perfmode 4 days ago |
didip 4 days ago |
For fun I am making hybrid search too and would love to see how you merge the two list (semantic and keyword) and rerank the importance score.
mrprincerawat 4 days ago |
jnstrdm05 4 days ago |
Did you build this for yourself?
openinstaclaw 4 days ago |
skwuwu 4 days ago |
Aceshootzxx95 3 days ago |
rigorclaw 4 days ago |
I’ve got a project right now, separate vector DB, Elasticsearch, graph store, all for an agent system.
When you say Antfly combines all three, what does that actually look like at query time? Can I write one query that does semantic similarity + full-text + graph traversal together, or is it more like three separate indexes that happen to live in the same binary?
Does it ship with a CLI that's actually good? I’m pivoting away from MCP. Like can I pipe stuff in, run queries, manage indexes from the terminal without needing to write a client? That matters more to me than the MCP server honestly.
And re: Termite + single binary, is the idea that I can just run `antfly swarm`, throw docs and images at it, and have a working local RAG setup with no API keys? If so, that might save me a lot of docker-compose work.
Who's actually running this distributed vs. single-node? Curious what the typical user experience looks like.