Aurix CMS

Small studios juggle three tools to publish one page — a CMS, a design tool, and a deploy pipeline that never talk to each other.

Interviewed five studio operators and audited eight existing CMS platforms. Every workflow broke at the same seam: preview-to-publish. Editors distrusted staging, engineers distrusted the CMS.

1. 01Next.js frontend served from the edge\nNestJS API with typed content contracts\nPostgreSQL primary with Supabase for auth & realtime\nOpenAI + retrieval layer for drafting assistance\nVercel deploy hooks for preview → production

Built the schema engine first, then the editor and AI drafting side-panel. Preview parity was the north star — the editor and production render from the same components.

Streaming AI drafts into a rich-text editor without losing cursor position. Rebuilt the editor around a granular event log that AI patches could apply as diffs.

Cut publishing time roughly 70% for internal clients. Editors ship without pinging engineers; engineers stop being asked to fix typos.