Private Beta

# Why Apodeixis is still in beta

The product is real, but the operating envelope is still intentionally small. We are keeping the demo cohort tight, keeping infrastructure costs tight, and only exposing the surfaces we can actually support well.

That means fewer teams, less ceremony, and less polish than a general release. It also means the core loop is visible: import a project, run verification, open theorem work, and inspect the evidence behind each handoff.

Open projects Login with GitHub

What you can use today

GitHub-based project import and repository sync.
Verification runs with queued, running, succeeded, and failed state.
Command-level provenance, artifact visibility, and job inspection.
Theorem pages with claims, intent, and explicit human or agent ownership.

What is still rough

Some onboarding paths still feel more like an operator console than a finished product.
The public site and the dashboard can drift while we tighten the core surfaces.
Animation, copy, and information architecture are still being hardened for the first cohort.
We are not optimizing for broad compatibility or legacy paths yet.

Why the scope is narrow

We want a small demo that proves the actual workflow, not a wide release with fake confidence.
We are keeping runtime and support costs low while we learn where the product boundary really is.
Every new surface has to earn its keep against verification, provenance, and theorem work.