Kryon is a next‑generation project scaffolding and automation tool. It doesn't just generate starter projects—it intelligently composes, configures, and evolves modern full‑stack applications based on declarative specifications.
- 🚀 Core Capabilities
- 📊 Why Kryon?
- ✨ In One Sentence
- 🛠️ Getting Started
- 🤝 Contributing
- 🗺️ Roadmap
- 💬 Community & Support
- 📄 License
Kryon generates complete project structures across both frontend and backend layers based on user‑defined configurations. It dynamically composes stacks rather than relying on rigid templates.
Example Stacks:
- Modern Web: Next.js + TanStack + Prisma + PostgreSQL + Docker + GitHub Actions
- Enterprise: Next.js + NestJS + Prisma + MongoDB + Docker + Jenkins CI
- Custom: Any combination of frameworks, ORMs, DBs, and deployment tooling.
Describe your desired architecture in a simple declarative configuration file, and Kryon handles the rest:
frontend: nextjs
state: tanstack
backend: nestjs
orm: prisma
db: postgresql
docker: true
ci: github-actionsKryon interprets this to:
- ✅ Select compatible libraries
- ✅ Generate optimized folder structures
- ✅ Create code with best‑practice defaults
- ✅ Wire configurations automatically
Kryon understands the ecosystem. If a requested combination has conflicts (e.g., an ORM that doesn't natively support a chosen backend), Kryon will:
- Suggest compatible alternatives.
- Generate necessary adapter code.
- Explain why the combination needs adjustment.
Kryon scaffolds more than just code; it generates deployable infrastructure:
- Docker: Tailored
Dockerfileanddocker-compose.ymlconfigurations. - CI/CD: Automated workflows (GitHub Actions, Jenkins, etc.) for build, test, and deployment.
Every generated project comes with:
- Sensible, scalable folder structures.
- Language‑appropriate linting and formatting (ESLint, Prettier, etc.).
- Security‑conscious configuration defaults.
- Ready-to-use test skeletons.
Unlike traditional scaffolders, Kryon is built for the long term. As standards evolve, Kryon can:
- Propose safe updates to existing projects.
- Generate migration helpers.
- Add new tooling based on updated intent.
Kryon is fully extensible. Teams can create Blueprints (plugins) for:
- New languages or frameworks.
- Custom architecture patterns.
- Organization‑specific standards.
Most existing project generators are limited to fixed templates and don't handle infrastructure or project evolution. Kryon fills that gap:
| Feature | Traditional Generators | Kryon |
|---|---|---|
| Dynamic Composition | ❌ | ✅ |
| Compatibility Validation | ❌ | ✅ |
| Infrastructure Aware (Docker/CI) | ❌ | ✅ |
| Ongoing Project Evolution | ❌ | ✅ |
| Extensible Plugin System | ❌ | ✅ |
While there are many scaffolding tools, Kryon is designed to be the long-term architect of your project, not just a one-time generator.
Unlike tools built by cloud providers (AWS, Vercel, Google), Kryon is completely agnostic. It doesn't push you toward a specific hosting service or proprietary ecosystem. You own your stack, your infrastructure, and your deployment.
Most generators create code that is "frozen in time." Kryon tracks the blueprints used to generate your project. When best practices change or dependencies update, Kryon can propose migrations and updates to keep your project modern without manual refactoring.
Kryon doesn't stop at src/. It understands that a modern app needs a Dockerfile, a docker-compose.yml, and a CI/CD pipeline. By generating these alongside your code, Kryon ensures your app is "deploy-ready" from minute one.
Kryon acts as a senior architect. It knows that certain ORMs don't play well with certain databases, or that some CI tools have limitations with specific frameworks. It catches these conflicts before you write a single line of code.
Kryon is a smart, configurable project architect that automates full‑stack project scaffolding, deployment setup, and ongoing best‑practice evolution — for any stack you choose.
Note
Kryon is currently in its early architectural phase. We are actively building the core engine and defining the blueprint specification.
- Node.js (v18 or higher)
- npm or yarn
- Docker (optional, for infrastructure testing)
- Clone the repository:
git clone https://github.com/your-org/kryon.git cd kryon - Install dependencies:
npm install
- Run in development mode:
npm run dev
We welcome contributions of all kinds! Whether you're fixing a bug, suggesting a feature, or improving documentation, your help is appreciated.
- Core Engine: Help us build the logic that interprets configurations and generates code.
- Blueprints: Create and share blueprints for your favorite tech stacks.
- Validation Logic: Improve the smart compatibility engine to prevent configuration errors.
- Documentation: Help us make Kryon easier to understand and use.
Please see our Contributing Guidelines for more details.
- Phase 1: Core CLI and basic Next.js/Prisma scaffolding.
- Phase 2: Smart compatibility engine and validation rules.
- Phase 3: Docker and CI/CD workflow generation.
- Phase 4: Plugin system and Blueprint ecosystem.
- Phase 5: Project evolution and migration helpers.
- GitHub Issues: For bug reports and feature requests.
- Discussions: For architectural questions and general talk.
- Twitter/X: Follow us for updates @KryonArchitect.
This project is licensed under the MIT License.