Your team, its tools, yoursharedagent

Hops works in the same chats, docs, tables, and apps as your team. It understands the context because it was there when the work happened.
AmazonAlteryBlue InkMerit AmericaPathstone
How it works

Every person gets Hops. And Hops gets the whole team behind it.

Ask like you'd ask a teammate by mentioning an agent and handing it a real task in plain language. No forms, prompting, or separate briefing.

Context comes from where work lives: the spaces, chats, docs, tables, and connected apps surrounding every request.

Memory preserves how you got here by keeping decisions, changes, and conversations connected to the work, where the team can see and edit what's kept.

Work returns to the team in the same space, ready for everyone to review, build on, and add to shared memory.

One place

Work is made of four things

Conversations, documents, tables, and the apps that tie them together. Every tool you pay for today is one of these wearing a logo. Hops puts all four in one place, and the agent is native to each one.
Conversations
Chat that Hops remembers
Spaces, threads, and DMs your whole team already knows how to use. Decisions made here don't evaporate: they become the context Hops starts from.
Documents
Docs both kinds of coworkers can write
Real-time collaborative documents Hops reads, edits, and keeps current while the team talks. And a doc can be more than content: write instructions in one, and it becomes how your agent works.
Tables
Structured data without the spreadsheet sprawl
Orders, inventory, contracts, projects, pipelines: structured data living next to the conversations about it. Hops queries it, updates it, and keeps it honest.
Apps
Interfaces on demand
Describe the view you need (a board over the orders table, a dashboard over your metrics, a client-ready one-pager) and Hops builds it on your data, inside your permissions.
Skills

One agent, a skill for every job

A skill teaches Hops a job. Install skills for yourself, and share the ones that work with your team.
Sales skills
Hops briefs every call, drafts every recap, and keeps the follow-up moving.
Operations skills
Hops watches the pipeline, flags what stalls, and drafts the next email.
Marketing skills
Hops turns shipped work into campaign briefs and keeps battlecards current.
Finance skills
Hops matches receipts, preps the close, and flags every variance early.
Legal skills
Hops redlines every contract against your playbook and cites every edit.
Consulting skills
Hops parses the SOW into a workplan and catches slips before clients do.
Founders skills
Hops posts the morning brief, chases the invoices, and keeps the board update current.
Product & Eng skills
Hops compiles the standup, drafts the release notes, and names the blockers.
HR skills
Hops drafts the JD, preps the interview loops, and packages week one.
Built for companies

One powerful agent. One place to govern it.

A Space holds the conversation, the docs, the tables, and the connected tools for one team or one project. Invite people, and ask @Hops to help out with the routine.
Grid of diverse software application logos, including productivity tools and stylized cartoon characters.
2000+ integrations
Hops reaches the tools you already run, from calendars and CRMs to repos and billing, through one governed catalog.
Browse the integrations
Automations in plain language
Describe the rule the way you'd say it. Hops runs it on a schedule or trigger. Anything sensitive waits as a draft for approval.
How automations work
Sandboxed execution
Hops runs real software like ffmpeg and LibreOffice in isolated sandboxes. A message can come back as a file.
Centralized AI spend
Every skill, model call, and permission in one place. One bill instead of a drawer of AI subscriptions.
How billing works
Your data, scoped
Hops sees what the space sees, nothing more. Access follows the same permissions your people have.
Read about permissions
FAQ

Questions, answered

Hops is a shared workspace for your team and one AI agent. People and Hops work in the same spaces, threads, docs, and tables, so Hops starts from the context your team already has instead of being briefed again in a private chat. You review its drafts and make the calls.

A chat assistant lives in a private window and forgets the project when the tab closes. Hops works inside the team's spaces, reads the same threads and docs, and posts its drafts where the work already happens. Decisions your team makes there become the context Hops starts from next time.

Hops drafts documents, briefs meetings, flags what's slipping, and keeps tables current. It reaches the tools your team already uses, from calendars and CRMs to repos and billing, through one governed catalog. Describe a rule in plain language and Hops picks it up on a schedule or trigger.

Your team does. Hops posts drafts, and anything sensitive waits for a named person's approval before it goes anywhere. Every edit Hops makes in a doc is labeled in version history, so the team can always see what came from Hops and what came from a person.

Hops sees what the space sees and nothing more. Access follows the same permissions your people already have, so there are no shadow permissions. Hops holds SOC 2 Type II, ISO 27001, and ISO 42001 certifications, and sandboxed execution keeps any software it uses isolated from your data.

Still have questions? Contact us

One AI teammate for the whole team

Knows the work. Forgets nothing. Shares with everyone.