Vyriy is built around one simple idea

Software should be understandable

• Calm means
  Architecture should be calm.
  Processes should be calm.
  Releases should be calm.

  Readable by humans
  A developer should be able to look at a project, a component, a script, or a deployment flow and read it almost like a story.

• Avoid
  No hidden magic.
  No unnecessary cleverness.
  No black boxes pretending to be simplicity.

  Prefer
  Just small explicit pieces.
  Clear boundaries.
  Readable flows.
  Predictable behavior.

That is what Vyriy is about

calm architecture · calm processes · calm releases

Principles

Calm architecture favors understandable systems over clever ones.

• explicit flow
  over hidden magic
• small modules
  over large frameworks
• boring deployment
  over complex runtime infrastructure
• clear boundaries
  over accidental coupling
• predictable behavior
  over surprising abstractions
• readable code
  over impressive code
• operational simplicity
  over architectural theater

Start with the CLI

Create a ready Vyriy project in seconds:

npm create vyriy@latest

Pick a preset for a library, API, SSR app, SSG site, SPA, GraphQL service, micro-frontend, MCP server, or fullstack React app — and start with shared tooling, predictable structure, and calm Vyriy conventions already wired in.

Use it when you want a calm starting point instead of wiring the same structure, configs, scripts, and conventions again by hand.

Calm Architecture is agent-readable architecture

A calm codebase is not only easy for humans to understand.

It is also easy for AI agents to navigate, modify, test, and validate — because the rules are written down as contracts.