Why we own the motor
Generation runs through a local AI SDK motor with Postgres chats and an esbuild preview. Why we own the render path instead of outsourcing it.
Tomas Laurinavicius
Hosting someone else's generation surface means their latency, their file model, and their lock-in. Growthtyping owns the motor: AI SDK, Postgres persistence, and a browser preview that does not depend on a third-party iframe.
That ownership is what lets export stay honest. If we can render it, we can hand you the files. If we cannot hand you the files, we should not have rendered it.