Deck
The most capable AI assistant with its own inbox
Start new thread

Deck - The most capable AI assistant with its own inbox

by•
Deck is an always-on AI assistant with its own email inbox. CC it on any thread or hand it a task, and it takes over. It learns your preferences and priorities over time, proactively flags what needs your attention, and can run on a schedule to deliver briefings and status updates automatically. It's built to take ambiguous, multi-step tasks head on, so you can move on with your day.

Add a comment

Replies

Best
Maker
📌
Hey all, I'm Stasia, founder of Deck. Deck is an AI teammate for busy operators, professionals, and teams. You can email it, use it in the app, sign it up for services you use, email alerts/newsletters, or set it up to run recurring work. It can read project files, summarize messy context, generate or edit decks/memos/sheets, answer questions over your knowledge base, and proactively surface things that need attention. Importantly, it doesn't require blanket inbox authorization to be effective and only emails you. We made email a first-class interface because delegation already happens there and it's a decades old, hardened protocol. People forward a thread, CC someone, attach files, subscribe it to email alerts and newsletters and ask for help. We believe Deck fits that behavior instead of asking users to move work into another chat app. But the system underneath is shared with the web app: automations, workflows, project search, document editing, and integrations. To get started, you name your assistant and claim its address and start free. We're letting PH users get in on the action with $15 off the monthly price using the promo code PRODUCTHUNT2026. Happy to answer anything about how it works, the trust model, or what we're learning from early users.

"most capable"... as in? Are there any benchmarks published? :D

Maker

 "most capable" as in end-to-end multi-step work over email, not just chat. benchmarks soon.

The "own inbox" framing is smart — most AI assistants just react to what you send them. Does Deck proactively flag things in that inbox, or is it purely on-demand when you check in?

Maker

 yes, you can set automations for things that hit the inbox immediately (we call these "Actions") and on a schedule (we call these "Scheduled Tasks"). for instance, I use it for reviewing our new customer sign-ups from Loops and send me a bit more about each that might be relevant. this works because the assistant has its own email address, so I can just add my assistant to our Loops team. anything in particular you're thinking about on flagging?

the cc-into-inbox approach is genuinely clever, feels way more natural than opening yet another app to delegate. curious how well it picks up on tone and priority cues over time.

Maker

 great question! we have a memory layer built in to learn more about the way a user wants to comm. additionally, there are configurations for how you'd like your assistant to respond, key persons, etc. anything that comes to mind when you think about priority cues?

The "give it its own inbox instead of blanket access to mine" call is the right instinct. An agent with its own address that only emails me is a far cleaner trust model than yet another tool asking to read my whole mailbox, and leaning on email as the delegation surface is smart since that behavior already exists.

Where my mind goes is the flip side: acting on anything it's CC'd on means inbound email becomes the attack surface. Wondering how Deck tells a real instruction from a spoofed or injected one. If someone emails its address pretending to be me or my boss, does it act with the same authority, or is there a trust boundary around who's actually allowed to make it do things?

Handed Deck a messy client thread to summarize and it pulled out the action items plus flagged two follow-ups I'd have missed. Liked that it just sat in my inbox waiting instead of demanding a chat window.

Congrats on the launch, Stasia. Giving Deck its own inbox instead of building on top of your real one is a cleaner boundary than most agent-inbox tools start with. When Deck signs up for a service on your behalf, does it hold that service's login itself, or hand off to a one-time OAuth flow for that step? That's the design choice I'm most curious about. Skipping blanket inbox authorization by default is a good call — most tools ask for way more access than they need on day one.

Cc'd it on a messy vendor thread and it actually pulled the right context back without me re-explaining anything. The morning briefing landing on its own was the part that sold me.

Been waiting for something like this, the idea of just CCing an agent into a thread and walking away is genuinely useful. One thing that would make me trust it faster is a clear rollback trail, so I can see exactly what it sent on my behalf and undo or edit a message within a short window after it goes out.

Maker

 Hey! As of today, Deck doesn't send on your behalf. Our customers are a mix of prosumer and business and they didn't want carte blanche on sending. Curious if that would be something you would want in an email assistant product>

CC-ing an AI assistant on a thread and having it just take over is a genuinely different interaction model than opening a chat window, that part is clever. what happens when it takes an action based on a misread of an ambiguous email though, does it check with you before actually replying or scheduling something on your behalf, or does it just act and let you catch mistakes after the fact?

Maker

 Hey! It doesn't send outbound to anyone but the assistant owner. Our customers are a mix of independent operators and businesses who (mostly) prefer we don't send outbound on their behalf. It's something we've thought about, but at this point it's just too risky. instead, what it will do is chime in (to you) with an angle, a data point you might have missed, or some other insight given what context it already has in thread. as you can imagine, I use it quite a bit for outbound in which case it comes in handy for logging convos, coaching on objection handling, allowing me to have all our data on hand for any interaction and drafting follow-ups.

12
Next
Last