Hops
Hops for the enterprise

One agent for every team, with governance built in.

Every team gets @Hops in its own space, reading only that space's threads, docs, and connections with the access your accounts already have. Anything that leaves Hops, or draws on a private source, waits for a person to approve.
  • Reads with your account's permissions, never elevated
  • Shows what it read and did on every answer
  • Holds external actions for a person's approval
  • All inside Hops, where your team and one agent work together
Try HopsContact sales
On the team

From one team's pilot to every team's teammate

Four controls, the same in every space. Rolling out the tenth team looks exactly like the first.
Team spaces
Sales works in the sales space, finance in finance. Each has its own members, a space manager, and pinned context, and @Hops answers from that space's threads, docs, and connections alone. Invite-only spaces keep sensitive work to the people on them.
Scoped access
@Hops reads a connected tool with the same permissions as the account that authorized it, never more. Workspace connections power it for the whole team. Personal connections stay yours: teammates can't see them, and you can revoke any of them from settings.
Approval cards
Emails, record updates, and doc edits wait on an approval card. So does any answer that might draw on a private source. Hops now checks first: no private source used, the post goes out. One used, you approve. Switch the check off in settings.
Visible work
Every @Hops answer shows what it read, what it did, and which skill shaped it. Docs and tables it creates carry a source trace. Automations keep a run log, and Activity gathers every update in one inbox.
Beyond chat

Not just chat. The actual work.

@Hops works in the same docs and threads your teams already use, and shows its sources on each one.
Collaborative Docs
Collaborative Docs
Real collaborative documents. Hops drafts, edits, and comments next to your team. Every Hops edit labeled in version history.
Collaborative Threads
Collaborative Threads
Conversations that carry the work. @Hops reads along, posts what it finds, and takes the next step right in the thread, next to your team.
Personal Assistant
Personal Assistant
Describe the job in plain language. @Hops runs it with everything it already knows: your context, your tools, your rules.
Integrations

Your stack, with your permissions

A 2K+ connector catalog behind @Hops, connected once for the workspace by an admin or personally by each teammate. Hops reads every tool with the access of the account that connected it.

Workspace connections

An admin connects the tools the whole team shares. They power @Hops in every space, and each tool inside a connection can be switched off on its own.

Personal connections

Your calendar, inbox, or drive stays yours. @Hops reads them only when you're the one asking, and teammates never see them.

Same access, never more

Hops reads with the permissions the authorizing account already has. Revoke a connection any time: past work stays, new reads stop.

Team management

Admin and member roles, seats, and per-person credit caps on one settings page. Sessions list every signed-in device, with sign-out for all of them at once.

Security that's already answered

SOC 2 Type II

Audited controls for security, availability, and confidentiality.

ISO 27001

Certified information security management.

ISO 42001

Certified AI management. Governance for the agent itself.

No training on your data

Hops reads with your account's permissions and doesn't use your data to train AI models.

One AI teammate for the whole team

Knows the work. Forgets nothing. Shares with everyone.
Try HopsContact sales