Company-wide AI, on your terms

Used by people at

  • Altery
  • Amazon
  • Blue Ink
  • Capgemini
  • Globant
  • Merit America
  • Microsoft
  • Miro
  • Novartis
  • Pathstone
  • Semrush
  • Kustomer

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

The same four controls apply in every space, so rolling Hops out to your tenth team works just like the first.

Each team works in its own space

Sales works in the sales space and finance works in finance. Hops answers only from that space's threads, docs and connected tools, and invite-only spaces stay private.

Same permissions as your people, never more

Hops works within the permissions each person has been granted, never more.

Nothing leaves Hops without approval

Before Hops sends an email, updates a record or edits a doc, you get an approval card. Answers that use a private source need approval too, and you can post, edit or discard each one.

See every source and step behind each answer

Every answer shows what Hops read and what Hops did. Docs and tables link back to their sources, and automations keep a log of every run.

The workspace that gets better the more your teams use it

Threads, docs, tables, decks, dashboards and apps all live in Hops, so each team works with Hops in one place and within its own permissions. When one team teaches Hops a process, any team with access can use it.

Ask @Hops in the thread. It answers from what your team already shared.

Set the rules once, for every team

Company-wide controls that every new team inherits.
SSO and SCIM
Sign in with your identity provider and add or remove seats automatically.
Roles and seats
Manage admin and member roles and seats in one place.
Credit caps
Set per-person credit caps so usage never surprises finance.
Tool access
Decide which tools Hops can use, and switch off any single action inside a connection.
Signed-in devices
See every device signed in to your workspace and sign them all out at once.
Security and compliance
SOC 2 Type II, ISO 27001 and ISO 42001 certified, with a security review, DPA and custom terms on the Enterprise plan.

Questions, answered

Still have questions? Contact us

Every team gets Hops in its own space. Sales works in the sales space and finance works in finance, and Hops answers only from that space's threads, docs and connected tools. You roll Hops out team by team, each space with its own owner and its own instructions, instead of switching the whole company on at once.

Keep them for individual work. Hops is for team work. It answers from each team's own space, works within the permissions each person has been granted, and shows what it read and did. Teams brief Hops in shared docs, threads and dashboards, where everyone can see the work.

Hops works within the permissions each person has been granted. Admins decide which shared connections each team can use, and can limit them to read-only. Personal connections stay with the person who made them: teammates can't see them, and anyone can disconnect their own in settings at any time.

Not on anything that leaves Hops. Emails, record updates and doc edits wait on an approval card, and so does any answer that might draw on a private source. A person approves, edits or declines. Admins can switch the private-source check off in settings if the team prefers.

Every Hops answer shows what Hops read and what Hops did. Docs and tables Hops creates link back to their sources, and automations keep a log of every run. Activity collects every update in one inbox, so nothing Hops does in a space is hidden from the people in it.

Your company-wide rollout starts with one small hop

Start with one team. Add the next when it's ready.