In Parallel
The Shared Context Layer for Enterprise AI
147 followers
The Shared Context Layer for Enterprise AI
147 followers
In Parallel continuously maintains a shared understanding of your organization.
As work happens, it keeps goals, decisions, ownership, risks, and progress up to date, giving both teams and AI a trusted operational picture of what's actually happening. Connect Claude, ChatGPT, Copilot, and other AI tools through MCP, with enterprise-grade security including EU hosting, permission-scoped access, GDPR, ISO 27001, ISO 42001, and SOC 2 Type II.
This is the 2nd launch from In Parallel. View more
In Parallel MCP
Launching today
You've explained your company to ChatGPT. Then to Claude. Then to Copilot.
Every time you open a new chat, you start from scratch. Paste the notes. Upload the document. Copy in the email thread. Summarize what your team decided two weeks ago — to a tool that could've just known it all along.
In Parallel's MCP server ends that. Connect it once, and whichever AI you open already knows your meetings, decisions, and context. Just ask the question. Less prose. More truth.
Free Options
Launch Team / Built With
In Parallel
Okay, as promised, I'll go first 😅
Mine was a weekly "alignment sync" that survived three reorgs. The project it was created for shipped in 2023. Nobody remembered why it existed, but nobody wanted to be the one to kill it — so every Monday, eight people spent 30 minutes confirming there was nothing to align on.
It finally died when someone noticed the original organizer had left the company a year earlier.
That meeting is basically why In Parallel exists. If the decisions and status lived somewhere that updated itself, the meeting would have had nothing left to do.
Your turn — what's yours? 👇
Congrats on the launch, Kristian! The concept of standardizing the shared context layer over MCP is brilliant. A major pain point with centralized team hubs is 'context drift'—a decision is made in Slack, the execution changes in GitHub, but the overarching context file stays static. How does In Parallel natively capture those micro-updates without forcing team members to manually edit the shared state every single day? Is it passively listening to integrations?
In Parallel
@franz_briones Yes, indeed. Passively listening, and analysing, de-duping, and collecting "observations" is the key. We've been inspired greatly by the works of John Boyd (an American fighter-pilot from Korean War who came up with the theory behind "Situational Awareness"). Context drift is such a great term. We use Coordination Tax, but I'm tempted to steal "Context drift". Did you coin it?
@kristian_luoma Haha, feel free to steal it—it’s officially open-source now! It just perfectly describes that silent drift where reality moves forward but the documentation stands still.
Love the John Boyd / OODA loop inspiration. Passively collecting and de-duping 'observations' is definitely the right architecture for this. If an organization can shorten its loop of capturing reality and feeding it to agents, it’s an immediate unfair advantage. Stoked to take this for a spin!
In Parallel
@franz_briones Thank you!
Really interesting approach to the LLM memory bottleneck standard custom instructions are too static, and vector databases get too noisy. Does your self-hosted VPC setup allow us to restrict sensitive context folders so only specific teams (like HR or Finance) can query them?
In Parallel
@priya_kushwaha1 Thanks so much, couldn't agree more. We do not at the moment offer VPC setup, but are working on that option; what is important is that we offer no-training on your data (ISO 42001 certified, and SOC2 compliant).
This bit me two weeks ago, a rule I set at planning stage silently disappeared before the generation step and the output invented a fact. Took a day to find where the context died. So, real question: two agents pull the same context, one updates it mid-task, what happens? Last write wins or something smarter?
In Parallel
@vladimir_iudin yeah, I hate when that happens. Well, we're building and maintaining decisions-based context that is the artefact e.g. something that can work for between people, not just between sessions. But to pull that off it is something smarter: so we save the "graph" of events and relationships, and use that.
@kristian_luoma Saving the graph instead of raw context answers it, yeah. "Between people, not just between sessions" is the part I'm going to sit with, my per-client fact bases are still session-shaped and that's probably a ceiling I haven't hit yet. Thanks Kristian.
SOC 2 Type II for an MCP context layer is exactly the boring enterprise signal I'd look for
In Parallel
@oleksandr_knyga 100%. Not only that, we got also ISO 42001. While not as hot yet, I'd say it'll be the future. If interested, here's some more boring stuff: https://podcasts.apple.com/cz/podcast/episode-1-pioneers-of-the-new-ai-standard-iso-42001/id1790620457?i=1000684062280&l=cs
Calendbook.com v1
As a CPO this hits a nerve 😅 The gap between "what we decided in the room" and "what's actually on the roadmap" is where half my week disappears. Every tool captures something — notes, tickets, docs — but the decision itself always seems to fall through the cracks. Love that In Parallel sits underneath instead of adding yet another surface to babysit. Pricing per workspace instead of per seat is the right call too. Congrats on the launch, upvoted 🚀
One thing that would make this a no-brainer for me is a mobile companion app. Most of my context-switching happens away from my desk, and being able to quickly check on goals, risks, or ownership changes from my phone would keep me aligned even when I'm not at my laptop. A simple read-only view with the ability to flag updates would be enough.
In Parallel
@eyll09641878946 .. did you just read our roadmap? Working on it!