What's great
Unblocked has become an indispensable part of our engineering workflow at Drata. What sets it apart is its deep integration with our internal ecosystem - it seamlessly connects our codebase, Slack conversations, Notion docs, Jira tickets, and GitHub activity into a unified knowledge layer.
The real magic happens when you need to understand why something was built a certain way. Instead of hunting through Slack threads, digging through old PRs, and cross-referencing design docs, Unblocked surfaces the context instantly. It's particularly brilliant at:
Following our company-specific coding patterns and suggesting code that matches our style
Tracing decision history across multiple platforms
Understanding code dependencies and architectural relationships
Helping with brainstorming sessions where institutional knowledge matters
We've also noticed it getting smarter over time, which gives us confidence in the product direction.
What needs improvement
Context freshness: Recently we've noticed it sometimes loses track of recent changes or provides slightly outdated information. Stronger temporal awareness would be huge.
Balance internal vs external knowledge: While the internal focus is a superpower, sometimes we need it to pull from broader technical documentation or general programming resources. Finding that balance would make it even more versatile.
Broader technical scope: Expanding beyond our specific codebase to handle more general programming questions would make it a true engineering copilot.
vs Alternatives
We didn't really evaluate alternatives - once we saw what Unblocked could do with our internal knowledge graph, we were sold. It's solving a real pain point for engineering teams with complex, distributed knowledge bases. Excited to see where it goes!
Does it respect repo and team-level permissions by default?
Yes
Is data stored, cached, or retained by third parties?
Nope
Can we self-host or run in a private cloud?
Cloud based