Core Concepts

Understand the philosophy behind Kybernus and how it structures your applications for success.

#1. 100% Free & Open Source

Kybernus is entirely Free and Open Source. We believe every developer should have access to professional-grade tools and industry-standard architectures without artificial paywalls. All stacks, all architectures (including Clean and Hexagonal), and all features are available out-of-the-box.

#2. Architectures

One size does not fit all. Kybernus allows you to choose the architectural pattern that fits your project's complexity.

MVC (Model-View-Controller)

• Structure: Controllers handling requests, Services for logic, Repositories for data.
• Pros: Simple, familiar, fast to build.
• Cons: Can become "spaghetti code" in very large apps. Tight coupling between layers.

Clean Architecture

• Structure: Based on Uncle Bob's principles. Domain-centric.
  • Domain: Entities and Repository Interfaces (No dependencies).
  • UseCases: Application business rules.
  • Infrastructure: Database implementations, external APIs.
  • Presentation: Controllers/Resolvers.
• Pros: Framework independent, highly testable, extremely maintainable.
• Cons: More boilerplate code upfront.

Hexagonal Architecture (Ports & Adapters)

• Structure:
  • Core: Business domain.
  • Ports: Interfaces defining input (Driver) and output (Driven).
  • Adapters: Implementations (API, Database, Messaging).
• Pros: Easy to swap infrastructure (e.g., change Postgres to Mongo without touching logic).
• Cons: Conceptual learning curve.

#3. Project Structure

Regardless of the stack, Kybernus projects share a common DNA:

• Standardized configuration: .env, ESLint, Prettier, TypeScript (where applicable).
• Consistency: A Java Spring project and a NestJS project generated by Kybernus follow similar organizational principles, making it easy for polyglot teams to switch contexts.