Writing
Notes on building support infrastructure in public
Engineering write-ups and product decisions, written as I build Inbxer in the open. No fixed schedule.
FeaturedProduct
Why I built Inbxer
Every B2B helpdesk I tried was built for someone else's problem. Here's the gap that made me start writing Inbxer, and why it had to be open source from day one.
Abdelmjid·1 Sep 2026 · 6 min readlicense MIT
channels email · slack · chat widget
ai agents 6, off by default
docker compose up -d --build
Engineering7 min read
Inside the six AI agents built into Inbxer
Draft, summarize, label, tag urgency, set tone and title threads — none of it on autopilot. Here's what each agent actually does and where a human still has to say yes.
Abdelmjid1 SepProduct5 min read
One queue for email, Slack and your chat widget
Three ways customers reach you, one place your team actually works. Here's how each channel gets into the same thread.
Abdelmjid1 SepSupport craft6 min read
SLAs that don't lie: how breach detection actually works
A countdown that ignores your business hours and doesn't pause while you're waiting on the customer isn't a promise, it's decoration. Here's how SLA tracking works in Inbxer.
Abdelmjid1 SepEngineering6 min read
The rule-based workflow engine, explained
Triggers, conditions and actions in plain language — no model in the loop, no black box, every run logged so you can see exactly why a thread moved.
Abdelmjid1 SepOpen source5 min read
Why MIT, not AGPL
A lot of self-hostable support tools ship AGPL specifically to stop you from competing with their cloud. That wasn't the trade I wanted to make.
Abdelmjid1 SepEngineering7 min read
The stack behind Inbxer
Boring technology, on purpose: Laravel, React, Reverb and MySQL. Here's what runs under the hood and why I picked each piece.
Abdelmjid1 SepGet new posts by email
One email when something ships or when I write up a decision. No newsletter cadence, no marketing sequence.