← All posts
Why we built sedim
The stamp model - install complete features, own every line.
The problem
Every project rebuilds the same infrastructure. Auth, sessions, OAuth, rate limiting: solved problems that developers and AI agents rewrite from scratch every time.
Existing solutions fall into two camps:
- Runtime SDKs - fast to start, hard to customize, vendor lock-in
- DIY from scratch - full control, weeks of work, easy to get security wrong
The stamp model
Sedim is a third option: a CLI that stamps production-ready code into your project. Not a dependency. Not a black box. Files you own forever.
sedim add auth
# → src/sedim/auth/ appears in your repo
# → no @sedim/* imports at runtime
# → edit anything, anytime
What's next
Auth is the first module. Notifications, chat, payments, and WebRTC are on the roadmap, all using the same stamp model.