You mentioned a few use cases both in your post and on the landing page. If you already have paying customers, is there any real use case you can share? I’m curious what people would use it for!
I actually don’t have paying customers yet, all on the free tier currently, as I’ve just launched this a couple days ago. So no complete case studies as of yet. But an example use case off the top of my head:
- A deployment tool founder monitoring for posts like “our CI pipeline is a nightmare.” When we find a matching post, we’d then email him and he can reply to the post with how he can help.
Are you using Fly’s Postgres?
Nope, using Crunchy Data. Crunchy’s pricing worked better for my needs, plus they integrate well with Tailscale, which fits nicely with the rest of the system.
How do you batch comparison jobs?
- All comparison jobs are placed in an Oban queue
- A highly concurrent Oban worker then reads from the queue and then makes RPC calls to the node running Bumblebee
- Nx.Serving is configured to automatically batch all incoming requests that arrive within about the same time
Are you using hybrid search or vector distance?
It’s mostly vector distance currently, but if a user specifies specific keywords then we use those to find matches regardless of the vector distance.
How are you approaching marketing & sales?
Honestly, still figuring this out… Just posted on a couple subreddits so far. Might run a couple ad campaigns.
You mentioned Elixir made it easier than expected, and several positive surprises. What has be the greatest challenge with building/maintaining the system?
Oban made concurrency and scaling easy, but debugging jobs was a bit hard initially when something went wrong. But adding extensive logging/metrics + the oban web dashboard recently becoming open source, really helped in making it easier to investigate issues and finding patterns in failed jobs.
And Thank you! Appreciate the questions and well wishes, wish you a great 2026 too 
