The best engineers blur the lines between frontend, backend, and infrastructure. With AI systems, this mindset is essential. LLMs introduce new failure modes. You need structured retries and feedback loops. Ship fast, own outcomes. sailhouse.dev/blog/engineeri…
We’ve never thought DevRel was about stickers or talks.
It’s the bug reports, Slack replies, and weird edge cases no one else caught. That’s where trust comes from.
A few thoughts on how we’re doing it at Sailhouse: sailhouse.dev/blog/developer…
The workflow is dead. Long live the agent!
We're shackling intelligent AI agents to 20-year-old orchestrators. The breakthrough: workflow IS the code. Agents should decide their own state transitions, not wait for permission. Event-driven > orchestrated
sailhouse.dev/blog/autonomou…
The AI boom feels like Web 1.0 all over again.
•Lots of demos
•Very little discipline
•Some real potential buried in the mess
Engineers who care about systems and scale still matter. Maybe more than ever.
sailhouse.dev/blog/ai-boom-d…
For those worried, we are definitely still up and running status.sailhouse.dev/
Hugops to those affected though - been there.
Remember when “event-driven” meant 3 events a day and a dead-letter queue someone made in 2019?
Now your AI agents are spawning 50,000 retries and hallucinating tool calls like it’s Burning Man.
Your infra probably wasn’t built for this! sailhouse.dev/blog/event-inf…
Just published: How I built an open-source email confirmation system using @SailhouseDev, @Netlify, and @resend.
No complex state management. No database setup. Events all the way down!
Grab it, hack it, use it!
Send events like never before, now with memory safety. In the US, it’s the law now (kinda definitely not).
crates.io/crates/sailhouse
Reliability is the name of the game.
We've got some exciting things to share very soon, but we're shipping some improvements and fixes to the UI and CLI this week before the really exciting things happen.
Missed this from last week?
Event-driven architecture makes it simple to build, and there’s so much more than just ease of use.
Go back and read @ejsdev and @whitep4nth3r talking about why you should go event-driven.
Why even use event-driven architecture?
We've written some words on why it's the way to go, from not blocking your users to errors that aren't a pain to recover.
sailhouse.dev/blog/dont-bloc…
Why even use event-driven architecture?
We've written some words on why it's the way to go, from not blocking your users to errors that aren't a pain to recover.
sailhouse.dev/blog/dont-bloc…
Sailhouse retweeted
Last week's episode with @edjsdev on how he's building @SailhouseDev is available in case you missed the live version!
Check it out 👇
youtu.be/Uc0y8E4sWJ4
Use @astrodotbuild? Great, we do too!
We've written up a guide on using Sailhouse with Astro, bringing together application tooling that's a breeze to use with a fantastic frontend framework.
Got a framework you'd like to see first-class support for? Let us know on our GitHub discussions!
github.com/orgs/sailhouse/di…





