The codebase behind the pitch

The codebase before the chaos.

A production-minded Next.js SaaS foundation: identity, permissions, billing, CMS, media, localization, feature flags, admin dashboards, and MCP operations in one source-owned system.

View pricing See YaYaw Table

Source-ownedNext.js 16MCP-ready

mcp-control-plane

Own itRead, run, extend, and adapt the source to your product.

Operate itPages, CMS data, media, catalog, and publication are toolable.

Ship on itUse the foundation for product logic instead of rebuilding plumbing.

What is inside

The parts that become hard later are modeled from day one.

Permissions, organization scope, billing state, publication workflows, media ownership, feature gating, admin visibility, and operational control are connected.

Auth + orgsAccounts, sessions, memberships, passkeys, and security patterns.

AuthorizationRBAC with groups, roles, policies, scoped bindings, and server checks.

BillingStripe-oriented payment, customer state, paid access, and admin foundations.

MCPCMS · Stripe · Admin · Media

CMS + mediaReusable sections, global data, page revisions, assets, generated images, and quotas.

Admin + MCPDashboards and typed tools for trusted automation and management.

Localization + flagsEnglish/French UI and feature gates for safer releases.

Control plane included

The codebase is built to be operated, not just admired.

Trusted operators can inspect pages, CMS data, media, tokens, billing catalog, validate drafts, compare revisions, and publish with explicit approval.

mcp-control-plane.run

$list global pages

$get latest revision

$save draft with expected revision

$validate page document

$diff draft against production

$publish after approval

ready_

Draft-first

Optimistic locking and validation before publish.

Auditable

Reasons, actors, targets, and revision IDs are recorded.

Operator-friendly

Content, catalog, media, tokens, and publication live behind tools.

Open-source proof

The table problem is not a component problem. It is a systems problem.

A serious SaaS ends up with dozens of tables, each needing sorting, grouping, search, calculations, filters, row actions, URL state, localization, and behavior per data type. YaYaw Table is the open-source proof that Yayaw understands where admin products really burn time.

Sorting + grouping

Shared table behavior instead of bespoke logic for every dataset.

Search + filters

Typed filtering and global search that survive real admin complexity.

Calculations

Totals, derived values, badges, and row signals without one-off glue every time.

Data-type behavior

Dates, numbers, enums, relations, booleans, and localized text each get appropriate UX.

URL state + i18n

Shareable views, localized labels, and state that behaves like product infrastructure.

Owned code

Shadcn and TanStack patterns in your codebase, not hidden in a grid vendor.

No magic. Better than magic.

Bring your product. Yayaw brings the infrastructure spine.

Yayaw does not replace your product. It removes the operational foundation work blocking it.

Not hosted. You own and run the system.

Not no-code. Engineering judgment still matters.

Not vague AI magic. The page builder lives inside a concrete CMS workflow.

Not a toy starter. The depth is authz, billing state, publishing, media, flags, admin, and MCP.

Ship the thing

Not the admin panel for the thing.

Start from the source-owned SaaS foundation and spend your energy on the product only you can build.

Get codebase access