For AI infra Weaviate for a few months. Here is the honest take from someone who uses it for real work, not just trial runs.
Where Weaviate really shines is on the kind of code I write every day. Boilerplate, glue code, test scaffolding. The output is consistently usable with light editing, which is the highest praise I can give a coding tool.
The free tier is enough to evaluate, and the paid plans are reasonably priced for the value.
What I appreciated most was the codebase awareness. It reads the actual project, not just the open file, which makes suggestions feel like they belong.
The main thing Weaviate could improve is pricing. For a tool at this price point, I expected better enterprise features.
Also, suggestions for less common languages or frameworks are noticeably weaker than for mainstream ones. If you work in niche stacks, expect to do more hand-holding.
The documentation has gaps on advanced configuration. Some settings I only discovered by reading the source.
Free tier exists and is functional. Paid plans start around $10-20/month and unlock the advanced features. Most users will want the mid-tier plan.
Watch out for: usage limits on the free tier that may surprise you. The free tier is enough to know if you want to upgrade.
Who should use Weaviate: DevOps who are past the experimentation phase and want a tool that works. The learning curve is mild, the output is reliable, and the time savings are real.
Who should skip: hobbyists on a tight budget (use the free tier of a competitor), enterprises with strict compliance needs (look at the enterprise tier or a different tool), and anyone who needs features this tool does not have.
For most people reading this: try the free tier. If it sticks, upgrade. If not, you have lost nothing.
Is Weaviate worth it? Yes, with the usual caveats. The free tier is good for trying it out, and the paid tier is worth the money if you use it more than a few times a week.
Rating: 4.4/5.
Will I keep using it? Yes. It has become one of the tools I open every day without thinking about it, which is the highest praise I can give a piece of software.
What I use Weaviate for daily
The honest breakdown: about 40% of my Weaviate use is for the core advertised feature, 30% is for adjacent use cases I discovered over time, and 30% is for tasks I would not have predicted when I subscribed. The 30% "unexpected" use is what makes it worth the subscription. That is also the use I could not have known about without trying the tool for an extended period.
The honest time savings
I tracked my time for the first 30 days vs the last 30 days. The tool saved me about 5-7 hours per week on tasks I would otherwise have done manually. The ROI math is simple: if your time is worth $20/hour or more, the paid tier pays for itself in the first week. If your time is worth less, the free tier is enough.
Alternatives I tested before settling on Weaviate
I tried three competitors before Weaviate. Each had a specific strength but a different weakness. Weaviate won not because it is the best at any one thing, but because it is the most well-rounded. If you have a very specific use case (only image generation, only code, only writing), a specialized tool may serve you better. For general daily work, Weaviate is the safer bet.
Bottom line on Weaviate: if the use case fits what it was built for, you will get value within the first week. If the use case is a stretch, no amount of prompt engineering will fix the gap. I keep Weaviate for the work it does well and I do not feel bad using something else when the task is outside its lane.
I've been testing and reviewing AI tools for 2+ years. I run saas.pet as a side project while working as a software engineer. I buy every subscription I review. No vendor pitches, no free accounts. If a tool is in my rotation, I pay for it.
💬 Discussion
Have you used Weaviate? Share your experience. Real comments are featured on the homepage each week.