Khint forteams
The owner shares Packs, members join by a link, and everyone keeps their own plan. A local-first model your security team can actually approve.
How a team runs Khint
One pack, the whole team
Build your Packs and Chains once, hit Share. Every member sees the latest version read-only, and clones what they want to make their own.
Invite by link
Create a team, copy the link, drop it in Slack. Anyone who opens it and signs in is a member. No SSO config, no provisioning run.
Everyone keeps their own plan
Joining a team shares visibility, not quota. Each member runs actions on their own Free or paid plan, so nobody inherits a surprise bill when the team changes.
Own quota each, nothing pooled
The same shortcut in every tool
Shared workflows write to the tools the team already lives in: Jira, Confluence, Linear, Notion, Slack and Gmail. Each member connects with their own credentials, held in their keychain, never on a server.
One member's palette. Their credentials, their keychain.
The security review is short
Khint is local-first: the text members run actions on and the results stay in SQLite on their machine, and Memory sessions never sync. Cloud sync moves Packs and history metadata only. The app needs one macOS permission, Accessibility, and integration credentials live in each member's keychain.
Read the security page →Straight answers for IT
Does Khint support teams?
Yes. The team owner builds Packs and Chains, hits Share, and every team member sees the latest version read-only. Members can clone any shared Pack into their personal library to tweak it for their own workflow.
How does billing work for a Khint team?
Members keep their own plan. Joining a team gives you visibility on shared Packs, not someone else's quota. Every member runs actions against their own Free or paid subscription. No seat-counting traps, no surprise bills when someone leaves.
How do team members join?
The team owner shares a link of the form khint.app/join/<code>. New members sign in via Clerk on that page and are added to the team. No SSO or provisioning: invite by link is the only flow today.
What do team members share?
Shared Packs and Chains. Members see them read-only and can clone them into their personal library. Clones are snapshots: they don't auto-update when the owner edits the original. Action history and Memory sessions are never shared.
Can I get SSO, SCIM, or a custom contract?
Not today. SSO and SCIM aren't built. Auth is Clerk sign-in plus invite links, and every member keeps their own Free or paid plan. If your team needs consolidated invoicing or a volume arrangement, email [email protected]: the founder reads every email and replies within 24 hours on weekdays. No procurement call, no seat-pricing matrix.
One email, direct line
No web form, no contact-sales SDR. The founder reads every email.