Choose an authoring API¶
Start with Hedron unless you have deliberately chosen the alternate class-oriented facade. Hedron is the primary documentation, examples, extension, and integration target. It exposes the FastAPI-native application model directly.
1.3 is published
Hedron 1.3.0 is available from PyPI. The documentation describes the stable Hedron 1.3 API contract.
The short answer¶
Choose Hedron for new applications, direct FastAPI route functions, explicit component-tree composition, Flask or Django hosts, and framework-extension work.
Choose Edron only when its class-oriented page vocabulary is itself a requirement. It lowers into the same Hedron runtime and remains available as an alternate facade.
Compare the authoring models¶
Decision table¶
| Requirement | Start with |
|---|---|
| Primary learning path and documentation | Hedron |
| New dashboard, CRUD app, or data workflow | Hedron |
| Data workspace, resource, cache, and job contracts | Hedron |
| Direct control over FastAPI dependencies and routes | Hedron |
| Reusable component or integration package | Hedron |
| Flask or Django runtime without FastAPI | Hedron |
| Class-oriented page vocabulary is a hard requirement | Edron |
What stays the same¶
Both layers use server-rendered HTML, HTMX for bounded partial updates, ordinary HTTP fallbacks, explicit trust boundaries, and one native application authority. Neither layer requires Node.js, owns your database, or replaces application authorization.