Today everyone uses AI their own way. HQ gets your whole team working as one. A workspace that makes your AI smarter the more you use it, and turns one person's wins into the whole team's default. You get sharper. They get faster.
Free Options
Launch Team
Render Sandboxes: a computer for every agentRun untrusted code safely. Idle sandboxes cost nothing
Promoted
Hey Product Hunt — Corey here, founder of HQ.
I run sixteen companies day-to-day. Every one of them needs me, my team, and our AI tools to share the same context — what we decided last Tuesday, which customer owns which thread, the policy we set six months ago that nobody remembers. I kept rebuilding the same scratch system over and over: a folder of files that Claude could read, a shared way to give every new session the same starting point, a way for my team to all work from the same playbook.
HQ is that system, productized. It's a local workspace your team's AI tools all read from — Claude Code, Cursor, Codex, whatever's next. Knowledge, skills, policies, and per-company workers live in one place and stay in sync across everyone's machines. Every AI session starts informed instead of starting cold.
A few things to know:
• Local-first and open source. The free starter kit is MIT-licensed and runs entirely on your machine. Get it at hqforwork.com. HQ Pro adds an encrypted vault and team sync on top of the same files you already own.
• Agent-agnostic. HQ is the layer underneath. Use whatever AI you trust above it — we don't compete with the model, we compete with the cold start.
• Scales without changing shape. Solo founders, small teams, and enterprises all use the same primitives. Engineers at Adobe and a handful of other teams are running it daily.
A few things I'd love feedback on today:
1. Where does the cold-start problem hurt you most — code, customer, or company-knowledge work?
2. If you've tried building this kind of shared context yourself, what broke first?
3. What's the one feature that would make you put HQ in front of your whole team this week?
I'll be in the comments all day. AMA.
@coreyeps How does HQ handle sensitive or private company information ?
@dipanshu_kushwaha5 Secrets are stored in AWS secrets manager. Files are in encrypted s3 vaults. We have unique KMS keys for each company and personal vault. On enterprise, we can also point HQ cloud towards on prem infrastructure
Hi everyone, I'm of the engineers building HQ.
Before HQ, my day was a row of terminal tabs, each running an AI agent that knew nothing about the others. When a teammate's agent learned something the hard way, mine made the same mistake the next day.
HQ fixed that for us. Our whole team and every agent we run work from one shared company brain. I now run a few teams of agents, one fixing production errors and one shipping releases, and I check on all of them from one place.
Question for anyone running more than one agent at a time: how do you keep track of what each one is doing? Tabs, a board, sticky notes?
I've been a beta user of HQ since earlier in the year, and holy smokes this is next level. All my devices (mac mini, macbook pro), my team, and my harnesses (whether Slack, Codex, Claude Code, GrokBot, Muse, etc) all leverage HQ to stay in sync. It's like dropbox meets memory for your whole team (or multiple devices).
Big ups to the team for also always being so available and helpful. Can't wait to see how HQ continues to grow!
@mrsharma 🔥🤍
@mrsharma Appreciate you, Nik!