Lumaft documentation

What Lumaft is, what it observes, and the objects you will work with.

Run Lumaft on your own machine against a bucket you already have, in about fifteen minutes.

Prerequisites, the container contract, and how to choose a deployment environment.

Declare the state buckets Lumaft observes, grant it read-only access, and verify the connection.

Report deployments to Lumaft from CI or a developer machine with lumaft exec or the ingestion API.

What to do after the first sign-in, what the console shows, and how to know the installation is ready.

What each part of the Operations page means, and what it deliberately refuses to say.

Configure SQLite or PostgreSQL, adopt PostgreSQL from SQLite, and run migrations, backups, and restores.

Bootstrap the first administrator, add accounts, assign roles, issue integration tokens, and secure the installation.

What Lumaft holds, what it refuses to hold, who can reach it, and how to report a problem.

Retire a Lumaft installation cleanly — keep what you must, revoke what you issued, release the license, and know what persists afterwards.

Every setting Lumaft reads, its default, the file rules that apply, and which settings belong to which topology.

Symptoms, causes, and fixes for startup, sign-in, backend, storage, and runner problems.

What the current build does not do, in terms you can check against the running product.

Every term Lumaft uses in the console, the API, and these docs, A to Z, with a link to where it matters.

Short answers to the questions that come up first, each linking to the page with the full story.