Why We Built NAEOS: Engineering Is Fragmented, and That's a Structural Problem
The story behind NAEOS — the fragmentation problem in modern software engineering, the specification-drift trap, and why …
From a single YAML spec, NAEOS generates complete projects — code, CI/CD, docs, deployment manifests, and AI context — across 5 languages and 6 AI platforms. Stop scaffolding. Start shipping.
Hand-writing boilerplate across five languages, keeping READMEs in sync with APIs, re-prompting AI assistants with architecture context — it compounds on every service you ship. Most teams spend weeks wiring projects before writing a single line of business logic.
NAEOS reads a single YAML/JSON specification, builds a canonical internal model (NEIR), and orchestrates the full engineering lifecycle — code, tests, CI/CD, deployment manifests, docs, and AI context — all traceable from intent to implementation.
Three steps between an idea and a production-ready project.
Declare modules, services, architecture, and infrastructure in one YAML file. The spec is the single source of truth — no code yet, just intent.
project: my-app
architecture:
pattern: microservices
services:
- name: gateway
kind: http
port: 8080NAEOS builds the NEIR intermediate representation: dependency graphs, validation, and policy evaluation catch problems before generation.
✓ modules: 4
✓ services: 8
✓ dependencies: 12
✓ architecture: microservices
✓ policies: passedProduction-ready projects in Go, TypeScript, Python, Java, or Rust — plus CI/CD, Docker/K8s manifests, docs, and AI context for 6 assistants.
├── go/ # Go services
├── typescript/ # TS services
├── infra/ # K8s + Terraform
├── ci/ # GitHub Actions
└── ai/ # Context bundlesEvery stage is observable, cacheable, and extensible via plugins — from parsing to artifact output.
67+ CLI commands · 5 languages · 6 AI platforms · 56+ specifications — one unified engineering system.
11-stage DAG pipeline from spec to shipped code. Each stage is observable, cacheable, and extensible via plugins. Inspect every transformation from YAML to artifact.
Feed your architecture directly into coding assistants. AI context bundles give Copilot, Claude, Cursor, Gemini, Codex, and OpenCode full system awareness — no more repeated prompting.
Production-ready code in Go, TypeScript, Python, Java, and Rust. Per-language adapters generate idiomatic project structures, tests, and dependency files out of the box.
A canonical model of your entire system — project structure, architecture, modules, services, APIs, infrastructure, and security policies. NEIR is the bridge between your intent and every generated artifact.
Enforce architecture rules before they hit production. Policy engine with 7 operators, RBAC, full audit trails, and artifact review. Catch violations during generation, not deployment.
Publish, discover, and install industry profiles and plugins. 5 built-in profiles (SaaS, AI Agent, FinTech, Healthcare, Government) plus a growing community registry.
From solo devs to platform teams — NAEOS adapts to how you build.
Define your entire service mesh in one spec. Generate Go and TypeScript services with REST endpoints, Dockerfiles, and production-grade Kubernetes manifests — all from a single YAML.
Go · TypeScriptDescribe event sources and function chains. Generate deployable Python and TypeScript handlers with IAM policies, event mappings, and framework configuration included.
Python · TypeScriptCompile your architecture into AI instruction sets. Your coding assistants start with full context — module structure, dependencies, API contracts — without copying READMEs into every prompt.
6 AI PlatformsPrevent architecture drift across teams. RBAC, audit trails, and a policy engine with 7 operators catch violations during generation — not after deployment.
GovernanceEdit a specification and inspect the resulting NEIR model structure immediately.
From idea to generated project in under 60 seconds.
Install with Go, use Docker, or download a ready-to-run binary.
go install github.com/NAEOS-foundation/naeos/cmd/naeos@latestDescribe your project structure in YAML or JSON.
project: my-app
modules:
- name: auth
path: ./auth
- name: api
path: ./api
dependencies: [auth]
services:
- name: gateway
kind: http
port: 8080
generation:
languages: [go, typescript]Parse, validate, generate, and export the complete project.
naeos run --input spec.yaml --output-dir ./outGenerate instruction sets for Copilot, Claude, Cursor, and other coding assistants.
naeos ai compile --input-file spec.yaml --target opencodeHear from teams that ship with NAEOS every day.
We replaced three code generators and a wiki with one NAEOS spec. Scaffolding a new Go + TypeScript service now takes seconds instead of hours.
The AI context bundles are a game changer. Claude Code understands our full architecture without me pasting README excerpts into every single prompt.
We migrated 12 services to NAEOS. The governance engine flagged three architecture violations during generation — caught them before they ever hit a PR.
News, tutorials, and deep dives from the NAEOS team.
The story behind NAEOS — the fragmentation problem in modern software engineering, the specification-drift trap, and why …
NAEOS v3.1.0 is now available with pipeline caching on naeos run, run-level profiling, new architecture patterns, and …
The official NAEOS whitepaper is now available — a comprehensive technical document covering vision, architecture, the …
5 languages + 6 AI platforms — one unified engineering system.
Install NAEOS with one command and generate your first project in under a minute.
go install github.com/NAEOS-foundation/naeos/cmd/naeos@latest