Spent a year on the free tier, then my team of five got sick of the dashboard shuffle. Upgraded to Pro. Here's the raw take.
The upgrade is 95% about organization and access control, not features. If you're constantly sharing links to specific runs or trying to explain which dashboard is the "source of truth," you need it. The private teams and projects finally let us stop tripping over each other. The increased storage and longer retention are nice, but the real value is not having to manually clean up your colleague's 10k failed experiment logs.
For five engineers? Honestly, it's borderline. If you're a tightly-knit group working on one project, you can probably limp along with the free tier's chaos. The moment you have more than two projects or need to onboard someone new without a mess, Pro becomes a necessity. It's less about the fancy new tools and more about basic sanity.
CRM is a necessary evil
Yeah, the organization piece is exactly what pushed us over the edge too. It's one of those things you don't realize is costing you time until you stop doing it.
I'd add that the real "borderline" factor for a small group is often your future runway. If you're expecting to grow the team or project count in the next 6-12 months, the upgrade becomes a clearer yes. The friction of migrating and restructuring later is a bigger headache than just starting with the proper structure now.
Your point about onboarding is spot on. Handing a new engineer a clean, team-specific project workspace is a night and day difference from the free tier's shared chaos.
You've really nailed the "basic sanity" aspect. The mental tax of that dashboard chaos is real, and it's often a silent drain. Teams will put up with it for a surprisingly long time before admitting how much focus it's costing.
I'd gently push back on it being borderline for five, though. In my experience, that's exactly the size where those organizational cracks start to become actual workflow faults. Five people is often enough for parallel workstreams to emerge, and that's when the free tier's single-project-per-user limit really starts to bite. You're not just managing one project anymore, you're managing the friction between them.
Once you start thinking about the time spent clarifying and cleaning, the cost of Pro often justifies itself pretty quickly.
— isabel
> "that's exactly the size where those organizational cracks start to become actual workflow faults"
This resonates. I've seen the same pattern play out in other tools - the jump from 3-4 people to 5-6 is often where the informal conventions break down. With four, you can still get away with a shared spreadsheet and a Slack thread. With five, someone inevitably starts a separate project and the divergence becomes a mess to reconcile.
One thing I'd add: the free tier's storage limits can be a sleeper issue for a group doing heavy hyperparameter sweeps. It's not just the dashboard chaos - it's also the implicit pressure to prune runs prematurely, which can kill reproducibility. Pro's retention is a small price if it means you don't have to ask "wait, did we delete the logs for that 200-run grid search last week?"
sub-100ms or bust