Add to Slack
Install Yasmine from the Slack app directory. It shows up like any new teammate, ready to talk.
An AI coworker that lives in your Slack. It answers email, tracks finances, runs operations, and ships code.
Not advice. Not a to-do list. Real work — finished and handed back to you.
Done. Every reply is drafted and waiting in Gmail.
40 emails waiting? Yasmine reads every one and writes the replies — sitting in your drafts, ready to send.
Went through Stripe and your sheets. One charge looks wrong.
Yasmine goes through your Stripe and spreadsheets and tells you what came in, what went out, and what looks wrong.
Handled in Notion, Gmail, and GitHub — one pass.
Need something done in Notion, Gmail, or GitHub? Yasmine clicks the buttons for you — across 2,000 apps.
Found it, fixed it. Nothing ships until you approve.
Something broken? Yasmine finds it, fixes it, and shows you the change before anything goes live.
Tool actions follow your workspace's Allow, Ask, or Block policy.
Workspace data is tenant-scoped; connected providers receive only the data needed for the action you request.
You don't learn anything new — you just talk to it like a person.
ChatGPT and the rest tell you what to do. Yasmine actually does it.
Writes you a list of 40 emails to answer.
Answers all 40. Drafts waiting in your inbox.
No setup project. No IT ticket. No training videos.
Install Yasmine from the Slack app directory. It shows up like any new teammate, ready to talk.
Your models come included — then link the tools you already use. Each connection lets Yasmine act, not just read.
Give Yasmine its first task and talk to it in the thread like a coworker — no commands, no training videos.
Yasmine reads and writes across your stack through tenant-scoped runtime and credential controls on AWS.
Clear boundaries, enforced in code. Here is exactly where Yasmine acts on your behalf, and where it holds the line.
TLS 1.2+ in transit. AES-256 at rest. Secrets held in tenant-scoped encrypted storage.
Included/platform routes use Yasmine credits and pricing. Eligible connected requests use the supported account or key and are provider-billed without Yasmine token markup.
Free and Starter use separate tenant containers on shared AWS hosts; Dev uses dedicated compute. Storage, secrets, and runtime identity remain tenant-scoped.
Disconnecting an integration or pausing a user blocks new access; an already in-flight request may finish.
Yasmine does not train its own models. Selected model providers process requests under the terms for the route you choose.
API keys and tokens use encrypted tenant-scoped storage and are presented only as needed to the selected provider or tool.
Tool calls follow the workspace's Allow, Ask, or Block policy; actions configured as Ask wait for explicit approval in Slack.
Tenant authorization, runtime identity, and encrypted state enforce workspace boundaries for skills, integrations, and memory.
Compare model and billing routes, tenant controls, and exact Allow, Ask, or Block behavior.
Included routes use Yasmine credits; eligible connected routes are provider-billed with no Yasmine token markup. Free 7-day trial. Start free →
Read the full breakdown in Viktor vs Yasmine vs Claude Tag.
Models included: start free and add credits for premium routes. Eligible plans can connect a supported account or key; connected usage is provider-billed with no Yasmine token markup.
Ideal for onboarding your new coworker.
Ideal for putting your coworker on a first real job.
Ideal for onboarding coworkers in marketing, finance, and ops teams — and more.
Ideal for your new full-stack developer.
SOC 2 Type II is on our roadmap · Yasmine does not train its own models · Selected providers process requests under their terms · Cancel anytime
Add a coworker to Slack with tenant-scoped runtime identity, encrypted state and credentials, and the tools you select.