Documentation
MidnightDocumentation
Recommended pages

CORE CONCEPTS

A small model for the whole application lifecycle.

Midnight separates what you intend to run from the evidence of what actually happened. Learn these resources first and the console, CLI, and API will read the same way.

One control planeEvidence-first
On this page

RESOURCE MODEL

Move from ownership to a running release.

  1. 1

    Workspace

    The collaboration and access boundary. Users accept invitations into a workspace.

  2. 2

    Project

    Groups one application or system and owns project-scoped automation credentials.

  3. 3

    Environment

    Separates production, staging, preview, or development desired state inside a project.

  4. 4

    Service

    Defines one deployable workload, including its source link, configuration, variables, volumes, and routes.

  5. 5

    Deployment

    An immutable release attempt for one service and environment.

RECONCILIATION

Desired state is not runtime proof.

Configuration, variables, domains, and deployment requests describe intent. Workers and the runtime agent reconcile that intent, then report observed state back to the control plane.

Desired state
The accepted configuration and mutation intent stored by the control plane.
Observed state
What the host, runtime, router, build system, and probes most recently reported.
Resource version
A monotonic version used to prevent a stale editor from overwriting a newer change.
Audit evidence
The durable record of who requested a change, what was admitted, and what followed.

EXECUTION

Deployments are releases; operations are work.

A deployment records the candidate and resulting release. An operation tracks the asynchronous work required to build, publish, start, stop, restart, roll back, or restore it. A 202 Accepted response means the request was durably queued—not that the application is healthy.

Deployment
Immutable input, service/environment target, release state, and runtime evidence.
Operation
Queued or running work with events, logs, terminal state, and a failure reason when applicable.
Redeploy
Replay an existing immutable image with current admitted configuration.
Rollback
Create a new release from an earlier known deployment; history remains intact.

ISOLATION

Use tiers to express intent.

production
The live environment. Treat changes and credentials as production operations.
staging
A persistent pre-production environment for validation.
preview
A short-lived review environment. Automatic pull-request lifecycle remains setup-dependent.
development
A lower-risk environment for iterative work.