Open-source nucleus

Nucleify

Ship modules. Not scaffolding.

One installable module carries API, SQL, and UI — ready for Vue, React, Nuxt, Next, Astro, Svelte, and Solid.

  • Typed APIs
  • Shared UI
  • Supabase-ready

Why Nucleify

Stop rebuilding the same platform.

Most teams rewrite auth, entities, and admin for every framework. Nucleify ships that once — as installable modules with API, SQL, and UI already wired.

  1. 01
    Install a moduleOne package. Full surface.
  2. 02
    Keep one contractTypes + API stay shared.
  3. 03
    Ship every shellNuxt, Next, and beyond.
01

Weeks of scaffolding → hours

A module is a product slice

Not a folder of leftovers — each nuc_* module brings routes, SQL, and UI that plug into one gateway.

api · sql · ui in one unit

02

One source of truth

Contracts travel with the feature

Types and request helpers live beside the module, so Vue and React stay aligned without copy-paste drift.

shared types · shared calls

03

One design system

UI that survives framework churn

nucleify-ui (Lit) gives you a premium system once — green for Nuxt, blue for Next, same components everywhere.

nui-* · framework-agnostic

Runtime surface

Pick a shell. Keep the nucleus.

The same modules boot across Vue, React, Nuxt, Next, Astro, Svelte, and Solid — one domain, zero rewrites.

active shell

Vue

Composition API

$make vue

Without forking

Override the surface. Keep the nucleus.

Drop a file in overrides/ — pages, routes, components, or tokens swap in place. The module stays typed, upgradeable, and yours to restyle.

Scale without rewrite

Add shells. Keep the cost flat.

Every new framework usually means another rewrite of the same product surface. Nucleify ships the module once — the rewrite tax stays at ×1 as you grow.

Start from the nucleus.

Clone, install modules, and keep shipping — without rebuilding the same platform twice.

© 2026 NucleifyModular. Typed. Ready.