Deployments

A Ferrite deployment starts from source, not an opaque local binary. The platform validates the app spec and code, builds the artifact, records the desired generation, starts the app, and probes its route before the CLI reports success.

Deploy a preview

ferrite preview

The preview command deploys the current committed revision without the production admission gate. It receives an isolated, auto-expiring URL for unproven work, browser acceptance, and agent evaluation.

Deploy source

ferrite deploy

deploy submits the application source, waits for admission and the attested build, and prints the deployed host only after Ferrite reports it running. If a terminal exits during the build, use the Dashboard deployment record to follow the resident worker; do not resubmit until you know the previous result.

Inspect evidence

ferrite status my-app
ferrite logs my-app

Open the Ferrite Dashboard for deployment history, build evidence, release state, usage, logs, and lifecycle controls.

Keep build acceptance, route readiness, app behavior, and production promotion as separate facts. A green local build is not a live deployment; a 200 health route is not proof that an authenticated workflow works.

Continue with Environments and Scaling & Releases.