OPEN SOURCE / AI DEVELOPMENT / ADMIN READY

OPEN-SOURCE AIADMIN SCAFFOLD.

A full-stack enterprise admin scaffold for AI-assisted development with authentication, RBAC, users, roles, menus, and API logs—without losing structure after the first demo.

View source Explore the system

SYSTEM ONLINE / READY TO EXTENDCYBER / 0.1.0

15system tables

ZOD 4runtime contracts

121backend tests

01 / WHY CYBER

Generating code is easy. Keeping a system coherent is not.

The hard part begins after the first prompt: modules drift, APIs diverge, decisions disappear, and every new conversation starts from zero.

A /

AI from zero

Fast first output. Context lives in chat. Foundations are rebuilt, boundaries are guessed, and the project becomes harder to continue.

B /

AI with Cyber

Start from a working full-stack foundation. Structure, contracts, documentation, and verification give every human and AI the same project truth.

“Cyber does not replace AI. It gives AI a reliable place to work.

02 / PRODUCT SURFACES

One foundation. Every surface aligned.

Scroll through the system—from the operator experience to the contracts and documentation that keep it maintainable.

SURFACE_01

Operational workbench

A clear application shell, live system signals, and an extensible home for real business modules.

SURFACE_02

Identity management

Users, departments, positions, and lifecycle state organized as explicit system capabilities.

SURFACE_03

Authorization boundaries

Stable permission keys and data scopes make access decisions visible, testable, and replaceable.

SURFACE_04

Database-driven navigation

Menus become controlled product structure, not scattered route guesses or hard-coded component paths.

SURFACE_05

Inspectable API activity

Filterable request records make backend behavior, retention, and response timing visible to operators.

SURFACE_06

Operator-controlled workspace

Navigation, theme, tabs, and brand visibility can be tuned from one focused settings surface.

SURFACE_01

Operational workbench

A clear application shell, live system signals, and an extensible home for real business modules.

03 / CORE SYSTEM

Built for the work after “generate”.

Cyber turns a capable AI into a reliable project collaborator by making the engineering environment explicit.

STRUCTURE

AI-readable architecture

Stable module names, public files, and one-way dependencies.

New capability has a known home before code is written.

MEMORY

Durable project context

Human and AI documentation describe the same current system.

The repository—not the latest chat—is the source of truth.

CONTRACT

Shared runtime contracts

Zod schemas stay alive at the HTTP boundary.

Types, validation, responses, and OpenAPI evolve together.

FOUNDATION

Enterprise admin foundation

Authentication, users, roles, menus, dictionaries, and API logs for an admin dashboard.

Start with the repetitive foundation already working.

BOUNDARIES

Controlled evolution

Design gates and explicit module ownership resist architecture drift.

Complexity grows inside clear boundaries instead of leaking everywhere.

VERIFY

Verification by design

Contracts and backend rules are backed by automated checks.

Frontend behavior keeps a clear human acceptance boundary.

04 / BUILD FLOW

From a plain-language idea to a maintainable module.

INTENT

Describe the outcome

A human explains the application, users, and business rules in ordinary language.

CONTEXT

Read the blueprint

AI loads the repository rules, current designs, module boundaries, and active plan.

SYSTEM

Build through contracts

Schema, API, backend, database, and interface are implemented as one traceable flow.

EVOLUTION

Verify and preserve

Checks run, human-facing behavior is accepted, and decisions return to repository memory.

05 / ARCHITECTURE

One contract path. No shadow specification.

The stack is familiar. The difference is how deliberately every layer is connected and documented.

01VUE 3Responsive operator interface

02ZOD 4Shared runtime contract

03NESTJSApplication and HTTP boundary

04DRIZZLEExplicit data access

05POSTGRESQLCurrent persistence baseline

RUNTIME CONTRACT

Schema first, everywhere it matters.

Frontend types are inferred. Nest validates requests and responses at runtime. OpenAPI metadata is generated from the same route contracts.

06 / WHO IT IS FOR

A serious starting point for different kinds of builders.

01 / IDEA → PRODUCT

Product makers

Bring the idea and make product decisions. Let AI handle more of the full-stack implementation without requiring you to first become a professional developer.

02 / SYSTEM → SCALE

Professional developers

Reuse the enterprise foundation, keep frontend and backend aligned, and let AI work inside explicit architecture instead of improvising around it.

07 / QUICK START

Clone. Configure. Start building.

Node.js, pnpm, and a fresh PostgreSQL database are all you need for the local foundation.

$ pnpm install

$ Copy-Item apps/backend/.env.example apps/backend/.env

$ pnpm db:migrate
$ pnpm dev

http://localhost:5173 READY

OPEN SOURCE / READY TO FORGE

Give your next AI-built system a structure worth keeping.

Start from a full-stack foundation designed for clear growth, shared truth, and continuous work.

Explore Cyber AI Forge on GitHub