Follow the Build Logs: VIDRAFT's Blog and the Founder's Brunch Essays
Notes from inside the build
The VIDRAFT blog is where the work gets explained in plain language. It carries two kinds of writing: editorial notes on where AI is heading, and engineering notes on how we actually built and shipped things. It is aimed at developers, so it favors specifics over announcements -- what we tried, what broke, and what we changed as a result.
Two streams to follow
There are two places to read us.
The blog itself holds engineering write-ups and editorial posts tied to the products: model releases, benchmark methodology, deployment lessons, and the occasional retrospective when something did not go to plan.
Separately, the founder writes long-form essays on Kakao Brunch under the handle @seawolf. Brunch is a Korean long-form publishing platform, and the essays there take a wider lens -- strategy, the Korean AI landscape, and the reasoning behind the bets a small lab makes. If the blog is "here is how we built it," the Brunch essays are "here is why we chose to build it this way."
Why we publish post-mortems
Most company blogs are highlight reels. We would rather publish the honest post-mortem: the merge that regressed, the benchmark that turned out to be measuring the wrong thing, the deployment that failed in a way we did not anticipate. For a lab whose entire pitch is method over scale, the method only earns trust if the failures sit on the record next to the wins. A clean narrative is easy to write and easy to distrust. A post-mortem that names the mistake is harder to fake.
For developers this is also the most useful content we can produce. A write-up of what broke in a real deployment saves you from hitting the same wall. That is the exchange we are after: we share the build logs, you get to skip our mistakes, and the feedback makes the next model better.
What to expect
Cadence over polish. Posts land when there is something real to report -- a release, a result, a lesson -- rather than on a marketing calendar. Expect tables, benchmark numbers with their scope attached, and code where code makes the point better than prose.
Honest scope
This is editorial and engineering writing, not a support channel or a spec sheet. Opinions in the posts are ours and may age badly as the field moves -- that is the nature of writing in public about a fast-moving area. The Brunch essays are the founder's personal long-form writing and reflect an individual viewpoint, not formal company positions or commitments. Nothing in a blog post is a product guarantee; when we describe something as in progress, it is in progress. Follow along for the reasoning and the post-mortems, and hold us to what we ship.
More: https://vidraft.net
Top comments (0)