Velozity - The Multiplayer AI Office where your team and agents work
by•
Your team chats in one app, meets in another, and every AI works alone. Velozity brings it all into one place.
Chat, audio and video calls with transcripts, tasks, calendar and files, plus AI agents (Claude, Codex, etc.) on the subscriptions you already pay for. Every agent shares the same context, so work moves between people and agents without having to re-explain.
For startups, teams in dev, product, sales, and ops, or solo users juggling several AIs.
No second AI bill. Free to start.
Replies
Is there a way to see everything an agent did while you were away?
@jasmine_charles Yes. Everything an agent does is posted in the space it worked in, so the full record is there when you come back: what it was asked, what it did, and the result.
If you don't want to scroll, you can just ask "what did I miss?" and get a summary of what happened while you were away, across your spaces. There's also a morning brief that covers the same ground each day.
@jasmine_charles
One thing to add to Ishu's answer: the record is written as the work happens, so it reads like a colleague's update, not a log you have to decode. And anything that needs your say, like sending an email, waits for your approval, so being away never means something went out without you.
How much time does your team spend repeating the same context to different AI tools?
Congrats @ishudarshan & team!
Thanks for sharing @rohanrecommends!
@hamza_afzal_butt Thanks, Hamza. Honestly, it varies, and sometimes it still takes longer than you'd expect. What's changed for us is that there's no back-and-forth anymore.
Everyone works in the same space, so it feels like one ongoing conversation, a bit like a WhatsApp group where the whole team and their agents are talking together. The agents feel like teammates, and everybody stays in the loop the whole time.
@hamza_afzal_butt
Adding to what Ishu said, Hamza: the repeating mostly goes away because the context lives in the Space, not in each person's chat with a tool. The files, the conversation and the call transcripts are already there, so any agent you bring in starts from the same picture as the team. You brief once, and the next person or agent picks up where the last one left off.
The shared AI agents idea is cool… how does the approval step work for things like payments or contracts?
@tery_emilson Thanks, Tery. Short version: agents prepare, a person approves, and money and signatures stay in human hands.
Nothing goes out without an approval card. When an agent wants to send an email, post, or submit a form, it stages the exact text and the exact destination on a card. Nothing happens until that is approved.
Only the agent's owner can approve. Teammates in the shared space can see the card, but their click is refused.
An approval covers one action only. It is tied to those exact words, that recipient, and that page. If anything differs at the moment of sending, it blocks and asks you again.
Payments and contracts are deliberately off limits for agents acting alone. Even a routine you have allowed to run automatically is stopped at any button like Pay, Buy, Checkout, Sign contract or Accept terms. Billing, cards, and subscriptions always need a fresh card, however clearly the agent was told.
Payment apps are read-only. With Stripe connected, an agent can look up invoices and revenue but cannot charge, refund, or pay out.
So today an agent can draft the contract, chase the invoice and set up the follow-up, and you do the paying and signing yourself.
@tery_emilson
Adding to Ishu's point, Tery: keeping payments and signatures with a person is a deliberate choice, not a missing feature. The agent does the legwork (drafts the contract, chases the invoice, lines up the follow-up) and you make the final click. Curious how you handle approvals for these today, that would help us shape what comes next.
Sounds awesome! Also, amazing editing of the video! Congrats!
@lakshya_singh Thank you, Lakshya! 🙌 Not everyone will see the video the same way, and that's fine, but I'm really glad it clicked for you. We wanted it to show real teammates doing real work, and your note tells me it landed.
@lakshya_singh Lakshya: thank you, the video took a lot of care and it's great to hear the editing stood out. If you try Velozity after watching it, tell us whether the product feels the way the video promised. That's the comparison we care about most.
@stormshot Yes, we built on open standards wherever one exists, so nothing here is a proprietary lock-in:
Tools for agents: Model Context Protocol (MCP). Everything an agent can do inside Velozity (read a space, post a message, drive the browser) is offered to it through MCP, the same standard Claude Code and Codex already use.
Talking to agents: Agent Client Protocol (ACP). Gemini, Kimi, OpenCode, and Cursor agents run over ACP. Claude Code and Codex are run through their own official command-line tools, unmodified.
Sign-in and connected apps: OAuth. You log in on the provider's own page, and we never see your password.
Calls and screen sharing: WebRTC.
If you meant a specific standard, such as a security certification or a data regulation, tell me which one and I'll give you a straight answer.
@stormshot
Yes. Data is encrypted in transit (TLS 1.2+) and at rest (AES-256), connected apps sign in through OAuth with limited scopes, and we follow GDPR and CCPA. Your data is never used to train AI models, and the cloud infrastructure we run on is independently audited (SOC 2 Type II, ISO 27001).
Details: velozity.ai/privacy
The shared context between the team and AI agents is what caught my attention. Love it
@shahriardgm Thank you, Shahriar! 🙌 Shared context was the whole reason we built it. When the team and the agents work from the same conversation, files, and tasks, nobody has to explain things twice. What would you want your agents to remember first about your team's work?
@shahriardgm
The context builds up on its own as the team works, so there is no separate step of briefing the agents. A new teammate or a new agent joining later starts from the same history as everyone else, which is where it really starts to pay off.
Hi ,
I want to know how you handle your data security and compliance part
@shailesh88 Hi Shailesh, good question. The short version:
Encryption: everything is encrypted in transit (TLS 1.2+) and at rest (AES-256).
Your data stays yours: we never sell it, never use it to train AI models, and never share it without your consent. You can export or delete it at any time.
Agents act with permission: an agent only reads the accounts you connect, through scoped OAuth access, and anything outward-facing, like sending an email, waits for a human to approve it.
Infrastructure: we run on cloud platforms that are independently audited for SOC 2 Type II and ISO 27001, and we back that with access controls, audit logging and regular security testing.
Compliance: we align with GDPR and CCPA, and we can sign a DPA if your team needs one.
The full details are in our Privacy Policy at velozity.ai/privacy.
If you have a specific requirement (data residency, a security questionnaire, HIPAA), tell me and I'll get you a precise answer.
@shailesh88
Hi Shailesh, thanks for asking! Your data is encrypted in transit and at rest, it is never used to train AI models, and we never sell or share it without your consent. We run on cloud infrastructure that is independently audited (SOC 2 Type II, ISO 27001), we follow GDPR and CCPA, and you can download or delete your data anytime.
Full details: velozity.ai/privacy
Congrats, Akash and Ishu, on the launch. Very interesting space, and I would love to know how you are differentiated from Serval and Atomic work. Congrats on securing #3 for product of the day!
The guest room is clever. Sharing work with a client without exposing everything else is something I always struggle with.
@sanika_gujar Thanks, Sanika. That struggle is exactly why we built it.
A client comes in on a guest pass. They get limited access to your office and can meet you there without becoming a member of your workspace.
You also choose how long the pass lasts, and you can revoke it anytime. When the project ends, their access ends with it, and there's nothing to clean up afterward.
If you try it with a client, I'd love to hear how it goes.
@sanika_gujar
Thanks Sanika, that struggle is exactly why we built it. The client sees only the room you open for them, and everything else stays private.
Very innovative product, and it really defines the future of team collaboration. I am quite curious about how you handle company memory. If different teams have asymmetric information, how does the agent handle that problem?
@llma Thanks, Long- great question, and it's the one we think about most. Memory in Velozity isn't one shared pool. It follows the same boundaries your team already has:
Personal memory stays personal. An agent working for you only draws on what you've connected and approved: your own mail, calendar, meetings and notes. It doesn't quietly pull another person's private context into its answers.
Shared memory lives in Spaces. A Space is where a team's files, notes and decisions sit, and an agent in that Space only sees what's been shared into it. Different teams get different Spaces, so they naturally hold different information.
Nothing crosses over without a person. When an agent wants to save something to memory, or act on someone's behalf, it proposes it and the owner approves it first. Information doesn't leak from one team to another on its own.
Agents say what they don't know. If the answer lives in a Space or source they can't see, they say so and don't guess to fill the gap.
So the "asymmetry" is deliberate: each team keeps its own view, and an agent reflects that view without flattening it. When something needs to be visible to everyone, a person promotes it into a shared Space. Happy to go deeper on any part of this.