Notes from the Odexy team.
Engineering deep-dives, product decisions, customer patterns, honest industry takes. RSS.
- By Odexy team
Audit log as a product feature
Why the audit log is on Odexy's product page, not its compliance page. What customers actually do with it.
- product
- By Odexy team
Idempotency keys are a contract, not a parameter
Why every state-changing action in Odexy requires an idempotency key — and what it costs us if a caller forgets to send one.
- engineering
- By Odexy team
Hiring for the build year
Open roles and the kind of engineer + designer + operator we're looking for. We dogfood our own Recruitment module.
- company
- By Odexy team
Why we call it a Work OS, not a SaaS
What we mean by Work OS, why we don't say AI-first or all-in-one, and how the AI sits inside the OS not next to it.
- product
- industry
- By Odexy team
The 12-tool tax
Most small teams run 8-12 tools to run a business. The hidden cost isn't the subscriptions. It's the schema drift.
- industry
- By Odexy team
Per-org pricing, explained
Why Odexy charges $49, $99, $199, $399, or Custom per organization — not per seat, not per module, not per AI action.
- product
- industry
- By Odexy team
How we ship a feature to the AI on the same day
There is no AI backlog. When the action ships, the AI can call it. Here's the contract every Odexy PR satisfies.
- engineering
- By Odexy team
Why we built the action layer
Every Work OS gets asked the AI question eventually. Most answers are a chatbot bolted on. Ours is an architectural primitive.
- product
- engineering