Why we built NIMBUS instead of using WordPress
The story behind the block-based + AI Composer platform running nimdigital.vn.
When we set out to build our own website, we faced the familiar choice: reach for WordPress and move fast, or build a leaner platform ourselves. We chose the second path — and named it NIMBUS.
The problem with the default
WordPress is powerful, but it comes at a cost: plugins on plugins, a large attack surface, performance that is hard to control, and a pile of configuration every time you clone it for a new client. With a focus on many small projects, we needed something lighter and safer.
How NIMBUS solves it
The core idea: every page is a JSON block tree. Content is fully separated from presentation and rendered with React Server Components, so pages load fast and rank well. The AI Composer can generate pages from a description — but only ever produces valid JSON against the registry, never free-form HTML, so AI can’t break the layout or inject stray code.
Just as important: the platform is designed to be cloned template-per-client. One repo, one free Supabase, one Vercel project per client — near-zero operating cost for small sites.
The result
The very site you are reading is the first product running on NIMBUS. For us, that is the most honest way to prove the platform works: dogfooding before inviting clients in.