GbunBoard is the community engine we wrote to move 300,000 posts of Noriter — Korean for “playground” — off a legacy stack. On top of it sit Gbun Commerce, for selling and payments, and the Flow family, where AI agents and people build software together. All of them run today on live sites and in our daily development, and we are preparing to release them as open source, one by one.
A community and publishing engine for the edge. One deployment is one site, with no servers to run. The engine owns boards, members, moderation, search, SEO and the admin workspace; a site only carries its configuration and skin.
Legacy self-hosted board software meant servers, patches and dead ends. We needed a modern engine that could take 300k posts, 850k comments, old URLs and search traffic without losing any of it.
Domain code never calls cloud APIs directly; adapters do. Everything that differs per site is expressed as configuration, skins or plugins — and lint rules enforce it.
We moved all of Noriter on October 11, 2026. Sites about phones, parenting, cars, K-culture, webtoons and coding education share the same engine.
Per-board permissions, list layouts and URL rules.
Members get the same cached page as visitors; personalization is layered on after.
Markdown, secret comments, tags, bookmarks and reactions.
Email-verified sign-up, Naver · Kakao · Google · GitHub login, trust levels.
Reports, hiding and suspensions, with every action logged.
Canonical URL rules, sitemaps, RSS · Atom · JSON feeds, structured data.
A dedicated full-text search database and object-storage media.
Resumable XE imports with data, media and SEO parity checks.
Plugin, skin and interaction APIs each carry a version, and a contract checker catches breakage early. Every site exposes an /mcp endpoint so AI agents can use plugin tools with OAuth 2.1 or API keys.
We shaped the engine by moving 17 years of Noriter onto it. Incidents from launch day were written up and became load-soak scenarios.
npm create gbunFour plugins that add product sales, coin top-ups, payments and access passes to GbunBoard. It lived inside the engine until October 2026, when we split it into its own product.
Webtoons, novels, video and character chat all need coin top-ups, per-episode unlocks, rentals and passes, and refunds. Rebuilding that per site is how money bugs happen.
Selling, balances, payment execution and content access are separate plugins. Each one writes only its own books.
Verified on a public demo site. Gbun VOD is the first consumer and Character Chat is next. No revenue-bearing production site yet.
| Plugin | Responsibility | Code | Test files |
|---|---|---|---|
| commerce | Shipped goods, cart, orders, cancellations & returns, coupons, points & tiers, reviews & Q&A, restock alerts, admin | 24k lines | 99 |
| wallet | Coin & point balances, expiry lots, transaction ledger, account merge | 2.1k lines | 14 |
| pay | Payment & refund execution, payment ledger, provider ports | 3.1k lines | 11 |
| paid | Coin products, settlement, refund clawback, access passes (permanent · rental · period) | 2.9k lines | 17 |
Applied exactly once, even if notices arrive twice, late or out of order.
Stored in expiry lots, every change in the ledger.
Unlock episodes as permanent, rental or period passes.
Refund and coin clawback land in the same transaction.
Country rules live in region packs — a Korean pack and a default one.
Payment providers and messaging plug in through ports.
No member-to-member or cross-site coin transfers, in line with Korea's 2024 e-finance amendments.
Playwright user journeys and ~20 persona QA rounds. Five critical order and refund defects fixed in October 2026.
We build with these every day. Rules live in Spec, work in Flow, execution in Deck and on-screen review in Review. This website was made the same way.
Fetch only the sections of the standard the task needs.
Record progress, decisions and failures on the task.
AI coding agent workers pick up the task and build it.
Point at the real page; the note becomes a task again.
Review note → Flow task → changed rules become a Spec revision. Every loop leaves a record.
A kanban issue tracker shared by clients and delivery teams, from request through work, review and sign-off. Start with a simple board and switch features on as you need them. Works for people alone, no AI required.
Keeps standards and designs as numbered sections, so following projects receive only the sections that changed. Agents read just what each task needs.
A desktop app that tiles many AI coding CLIs in one grid and mirrors the same sessions on your phone. It takes Flow tasks, runs them as workers and posts the results back.
Point at a problem on the real page, leave a word, and it becomes a finding — with position and screenshot — sent straight to Flow as a task.
| Product | Where it stands | License |
|---|---|---|
| Gbun Flow | Tracks all of our development work. Not yet run for outside clients | MIT |
| Gbun Spec | Every internal repo reads its rules from it. Not yet deployed to production | To be decided |
| Gbun Deck | Installed on our machines and used daily | To be decided |
| Gbun Review | Verified locally and with persona QA | To be decided |
Every repository is still private. We will release in the order things have been proven in production, after separating internal docs, settling licenses and completing a security pass.
Engine, 9 plugins, skins and the import tool. Public-facing docs already exist.
MITThe issue tracker as a GbunBoard plugin, with MCP tools.
MITShop, wallet, payment and access-pass plugins, after VOD is proven in production.
MIT plannedReleased once licenses are chosen and internal dependencies are cut.
To be decidedOutside eyes on sign-in, payments and plugin boundaries.
Infrastructure to run today's manual checks on every public push.
Install, plugin-authoring and migration guides in English.
Time to review outside contributions and keep versions stable.
We welcome open-source support, co-development and GbunBoard adoption.
dev@noriter.com