# Introduction

What Zever is, how the compiler and container fit together, and where to go next.

<HeroBanner
  eyebrow="Zever documentation"
  title="One schema. Every backend concern. <em>Zero rewiring.</em>"
  lede="Zever is a schema-driven scaffolding compiler for Go. Describe your domain once in .zen, compile it into validation, ORM, OpenAPI, and DDL, then resolve every backend through one container. Not a web framework: your handlers and business logic stay yours."
/>

## Install

One command installs the `zever` CLI and `zever-lsp` (no sudo, SHA-256 verified):

```sh
curl -fsSL https://raw.githubusercontent.com/zenta-dev/zever/main/install.sh | sh
```

```sh
curl -fsSL https://raw.githubusercontent.com/zenta-dev/zever/main/install.sh | sh
```

```powershell
irm https://raw.githubusercontent.com/zenta-dev/zever/main/install.ps1 | iex
```

Options, upgrade and uninstall are on the [installation page](https://zenta-dev.github.io/zever/start/installation/).

## Where to start

    Go from an empty folder to a running API in five commands.
    Learn by building, from a first schema to a running Booking API.
    Task-focused how-tos for HTTP, data, background work, security, and operations.
    One lazy container, explicit adapter registration, and a defined lifecycle.
    Entities, services, RPCs, and attributes in the `.zen` language.
    CLI commands, configuration keys, adapter matrix, and API index.

## How it fits together

1. **Describe** entities and services in a `.zen` schema ([syntax](https://zenta-dev.github.io/zever/reference/zen-syntax/)).
2. **Compile** with `zever compile` into typed ORM, OpenAPI, and migration DDL ([backends](https://zenta-dev.github.io/zever/concepts/backends/)).
3. **Wire** services through one lazy `container.Container` ([container](https://zenta-dev.github.io/zever/concepts/container/)).
4. **Swap** adapters (sqlite to postgres, memory to redis) by editing config, never call sites ([adapters](https://zenta-dev.github.io/zever/concepts/providers-adapters/)).