Draco Dawson

I ve written a few posts about the thinking behind Seamcult: why MCP, why there s no built-in chat, and why it s free during early access. I thought I d bring them together here as a short FAQ, with quick answers below and links to the full posts.
Why MCP, and why no built-in chat?

You already have an assistant with your preferred model, conversation history, and a chat interface you know. MCP lets that assistant work directly with Seamcult s drafting tools while you review the result on the canvas. This lets us focus on the pattern editor, and avoids charging you for another layer of AI usage through our own chat.

More on why Seamcult has no chat of its own

Why does the model you connect matter?

Nitrosend now has its own mail delivery engine, and today it's open source as NitroMTA: a self-hosted engine that speaks the Amazon SES v2 API, built in Rust. It's launching on Product Hunt today, and we'd love your feedback on the launch page: https://www.producthunt.com/prod...

Visual bugs or broken buttons are easy to spot right away, but silent failures are terrifying because everything looks completely normal on the dashboard.

Our scariest silent bug happened when a background worker quietly stopped processing webhook retries due to a silent timeout exception leaving hundreds of user orders stuck in limbo for days without any logs throwing an alert. We ended up setting up an external health ping just to make sure those queues are actually moving every hour. What's your go to way for catching background failures before users notice?