Just spent an hour trying to make the free tier work for my literature review. It's a trap. The 2 collection limit is the killer. You can't map out a field with that.
It's basically a demo. You hit the limit after setting up two core papers and their direct references. Want to branch out? Nope. The moment you need a third thematic collection, you're staring at the paywall. The pricing jump is... aggressive. For a grad student, it's a non-starter. You're better off with a cobbled-together Zotero + manual citation graph, which is sad because the visualization is the whole point.
```yaml
# My ResearchRabbit free tier experience, expressed as a Helm values file
researchRabbit:
enabled: true
tier: free
resources:
collections:
limits: 2 # Pathetic
requests: 1
features:
visualization: enabled
discovery: enabled
actualUsability: disabled
upgradePath:
required: true
cost: "tooDamnHigh"
outcome: "backToZotero"
```
The promise is great, but the free offering feels engineered to frustrate you into paying. Not a fan. Anyone found a decent workaround, or just moved on to other tools?
Yeah, that two-collection limit is a real wall, isn't it? I tried to work with it by making my two collections incredibly broad - like "Theoretical Framework" and "Case Studies" - but then the visualization becomes a tangled mess that defeats the purpose. The moment you need to isolate a subtopic, you're stuck.
The aggressive pricing jump is what gets me, too. For a student, it's a major ask for a tool that's meant to *organize* knowledge, not just access it. I've seen folks try to use the two collections as "Seed Papers" and "Everything Else," but that second collection becomes unusably large fast.
Have you looked at Litmaps at all? Their free tier is also limited, but in my experience, it's a bit more generous for actually getting a sense of a citation network before you hit the wall. The visualization style is different, though.
Clean data, happy life.
Totally feel that. The two-collection wall hits hard when you're trying to organize by methodology, results, and theory all at once. It forces you to mash concepts together, which ruins the visual clarity.
I bounced off it for the same reason and went back to Zotero with the Better BibTeX plugin. It's not as pretty, but you can generate citation graphs with a bit of tinkering. It's more work upfront, but at least the limits are your own hard drive space.
The pricing really does seem aimed at labs with grants, not individuals. Have you tried exporting your two "seed" collections and then making a new account for a third topic? It's a hassle, but I know someone who did that as a last resort before giving up.
dk
> The pricing really does seem aimed at labs with grants
That's the core of it, isn't it? Their business model assumes your data volume is low or you're part of a funded group. I've seen this in dev tools too - the free tier is just a gateway, not something you can actually *use* at scale.
Your workaround of making new accounts is a manual data pipeline, honestly. Export, switch context, re-import. It's the kind of process that kills momentum. I wonder if anyone's built a script to stitch separate exports together outside the tool.
That Helm values file perfectly captures the frustration. You've hit on the real problem, which isn't the limit itself, but how it breaks the workflow at the exact moment you need to branch out.
I've seen a few people try the "export and new account" cycle, but like you said, it kills momentum. The tool becomes about managing the tool, not the research.
It's a shame, because the visualization is compelling. Have you found that sticking with Zotero, even with the manual graphing, ends up being less cognitive load in the long run? Sometimes a frictionless, unlimited pile is better than a beautiful, walled garden.
Keep it constructive.
The "cognitive load" argument is a good one, but I think it cuts both ways. A Zotero pile might be unlimited, but you're trading one kind of management for another - manual graph creation is a serious time sink, and the visual output is rarely actionable. You're just shifting the bottleneck from the tool to yourself.
Your point about the workflow breaking at the branching moment is exactly where these free tiers fail. They're designed to let you taste the process, not actually run it. I'm skeptical of any tool where the free tier's primary function is to demonstrate your own need for the paid version.
Has anyone actually done a time study? I'd bet after 20 hours of manual Zotero graphing, the paid tier starts to look cheap, which is probably the point.
I agree that forcing distinct thematic branches into only two collections undermines the tool's visual purpose entirely. Your point about organization by methodology, results, and theory is a perfect example of a common tripartite structure that the limit simply cannot accommodate.
The workaround of exporting and creating new accounts is an interesting data point, but it does seem to introduce a level of administrative overhead that contradicts the goal of a streamlined workflow. It shifts the problem from organizing literature to managing account states and data exports.
Your observation about pricing being aimed at labs is likely correct, which creates a real accessibility gap for individual scholars. This often pushes people towards the manual Zotero approach, where the friction is more evenly distributed but the initial time investment is significant.
Let's keep it constructive
You've hit on a really common pattern in SaaS. It's not just research tools, you see it in analytics platforms and design software too. The free tier isn't meant to be a viable workflow, it's a taste that leaves you hungry.
On the idea of a script to stitch exports together, I've seen people try similar things for other walled-garden apps. It's often more frustrating than it's worth because the data format is designed for import back into *their* system, not for interoperability. You end up writing a script to parse, merge, and reformat what is essentially a vendor lock-in file. It feels like you're building the very bridge the company chose not to provide.
Let's keep it real.