Your company's voice, on every keyboard.
Makro Teams puts a shared macro library and a shared writing voice in every member's browser. The server stores encrypted blobs it cannot read; the team key travels only inside the invite link. A new seat is live minutes after the member clicks it.
Makro Teams is in beta. Signup and invites are still rough. Tell us what breaks: support@makroexpander.com
One price, per seat.
Billed monthly through Polar. Cancel anytime; there is no minimum contract.
- Free 3-member trial first: shared macros, team voice, and zero-knowledge team sync from day one, no card. AI credits come with paid seats.
- Every paid seat is the Makro Teams tier: 25,000 AI credits a month per member, cloud sync on up to 3 devices, and every AI feature included - no separate personal subscription needed.
- Self-serve checkout up to 500 seats from the portal, any team size.
- Team macro library, pushed read-only to every member's extension.
- Team voice: a shared writing-style profile that grounds AI rewrites for the whole team.
- Zero-knowledge team sync: AES-256-GCM blobs; decryption keys never reach our servers.
- One admin portal at teams.makroexpander.com: seats, invites, content, billing.
Four steps, no IT project.
Open teams.makroexpander.com, sign in with your Makro license key or generate a new one right there, and name the workspace. You start on a free 3-member trial; the team encryption key is generated in your browser at this moment - our servers never receive it.
Each member opens your invite link and enters their own license key. The team key rides in the link's URL fragment (the part after #), which browsers never transmit to a server. There is no account to create.
Team macros and the team voice appear in every member's extension on its next sync, within about 15 minutes. Publish an update once; every keyboard gets it.
Members keep their own macros and the admin cannot read them. On a hotword conflict, the personal macro always wins.
What the server cannot see.
This section exists for the person who has to approve the vendor. Every claim below is architectural: it holds because of how the keys move, and you can verify the traffic yourself.
Team content is encrypted in the admin's browser with AES-256-GCM before upload. Our servers store the ciphertext and a version number. A breach of our database exposes no readable team content.
The team key moves member to member inside the invite link's URL fragment. Fragments are never sent in HTTP requests, so the key never appears in our request logs or our database.
Members authenticate with the license key they already have, hashed with SHA-256 before any network call. No passwords to rotate and no user directory to manage.
Removing a member deletes their server-side membership records. Deleting a workspace deletes its blobs. Erasure requests go to support@makroexpander.com and are handled under our standard privacy policy.
Asked before the sign-off.
Do team macros override my personal ones?
What can the admin see? What can Makro see?
What happens when someone leaves the team?
How does billing and cancellation work?
Which browsers are supported?
Can we pay by invoice or purchase order?
Rolling out to a bigger team?
Self-serve checkout covers up to 500 seats, so most teams never need this form. If you have a procurement question, a requirement we have not covered, or a deployment you want to talk through first, tell us who you are and we will reply from teams@makroexpander.com.