Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions .github/workflows/docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,12 @@ jobs:
with:
python-version: "3.13"
enable-cache: false
- run: python3 -m unittest discover -s tests
env:
PYTHONDONTWRITEBYTECODE: "1"
- run: python3 scripts/check_evidence.py
- run: python3 scripts/export_compatibility.py --check
- run: python3 scripts/export_profile.py --check
- run: python3 scripts/check_links.py
- run: bash scripts/check_start.sh

Expand Down
7 changes: 7 additions & 0 deletions data/ecosystem.toml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,13 @@ mcp_revision = "2025-11-25"
openapi_revision = "3.1.1"
minimum_python = "3.12"

[profile_evidence]
as_of = "2026-07-28"
commit = "9e27b0191c7fa9f920ad6fe5b126e190268afba2"
benchmark_path = "benchmarks/competitive/results/2026-07-28-hayate-0.15.1-macos-arm64.json"
benchmark_result_commit = "561bcf01874e7777b04917ff84e683afff264180"
capabilities_path = "benchmarks/competitive/capabilities.json"

[sources.golden_app]
label = "golden-app main CI"
url = "https://github.com/hayatepy/golden-app/actions/runs/30315193937"
Expand Down
68 changes: 45 additions & 23 deletions profile/README.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
<!-- Generated by scripts/export_profile.py; edit README.md.in. -->

# hayatepy

**Web-standards-first Python for applications that run across ASGI, Cloudflare
Expand All @@ -11,7 +13,8 @@ logic on a conventional Python server or directly inside Cloudflare workerd.

1. Follow the [single quickstart](https://github.com/hayatepy/.github/blob/main/docs/START.md).
2. Use the [executable production golden app](https://github.com/hayatepy/golden-app)
for Cloudflare Access, OpenAPI, MCP, checked SQL, SQLite/D1, and deployment.
for Cloudflare Access, OpenAPI, MCP, checked SQL, operational administration,
SQLite/D1, and deployment.
3. Check the [generated compatibility evidence](https://github.com/hayatepy/.github/blob/main/docs/COMPATIBILITY.md)
before selecting versions or runtimes.

Expand All @@ -22,35 +25,53 @@ contract through the bounded
## Why Hayate

Hayate is strongest when one Python application must combine typed HTTP,
MCP, authorization, and checked data access across conventional ASGI servers
and native Cloudflare Workers.
MCP, authorization, and checked data access across conventional ASGI servers,
native Cloudflare Workers, and AWS Lambda.

The recorded 2026-07-27 same-workload HTTP baseline measured:
The recorded 2026-07-28 same-workload HTTP baseline measured:

| Boundary | Hayate 0.12.1 | FastAPI 0.140.0 | Django 6.0.7 | Hono 4.12.32 |
| Boundary | Hayate 0.15.1 | FastAPI 0.140.0 | Django 6.0.7 | Hono 4.12.32 |
|---|---:|---:|---:|---:|
| Cold start | 130.3 ms | 220.5 ms | 155.5 ms | **55.0 ms** |
| Cold start | 149.0 ms | 471.4 ms | 392.6 ms | **61.3 ms** |
| Production packages | 5 | 13 | 6 | **2** |
| gzip payload | 287.5 KiB | 2,802.1 KiB | 5,147.1 KiB | **281.5 KiB** |
| Throughput | 13,995 req/s | 10,161 req/s | 2,719 req/s | **63,198 req/s** |
| gzip payload | 298.1 KiB | 2,802.2 KiB | 5,147.2 KiB | **281.5 KiB** |
| Throughput | 14,906 req/s | 10,086 req/s | 2,557 req/s | **59,187 req/s** |
| Common HTTP contract | **14/14** | 12/14 | 12/14 | 12/14 |

On this workload Hayate delivered 1.38x FastAPI's and 5.15x Django's
throughput. Hono delivered 4.52x Hayate's throughput and retained the best
startup result. The 14-point contract is a shared-workload result, not a
universal standards score.

Feature breadth is evaluated separately and without a weighted winner. Hayate
is advantaged for a portable Python agent API; FastAPI remains competitive for
conventional typed Python APIs; Django retains integrated admin, ORM,
migrations, forms, and templates; Hono retains broad JavaScript-runtime
portability and route-inferred TypeScript RPC.
On this workload Hayate delivered 1.48x FastAPI's and 5.83x Django's throughput. Hono
delivered 3.97x Hayate's throughput and retained the best startup, dependency-count, and
deployment-payload results.

The 14-point contract is a shared-workload result, not a universal standards
score. Feature breadth is evaluated separately and without a weighted winner:

- **Portable Python agent API — Hayate advantaged.** Hayate has the clearest first-party
path when one Python application must run on ASGI, native Cloudflare Workers, and
buffered or response-streaming AWS Lambda HTTP payload v2 while combining typed HTTP
contracts, cached dependency graphs, MCP 2025-11-25, authorization, and checked
SQLite/D1 access.
- **Conventional typed Python API — competitive.** Hayate now meets FastAPI's central
typed request/response, OpenAPI, dependency-graph, direct-test, realtime, lifecycle,
and sub-application composition capabilities. FastAPI retains a much larger adoption
ecosystem; that is a material adoption advantage, not a missing Hayate endpoint
feature.
- **Traditional database-backed full stack — competitor advantaged.** Django remains
functionally ahead for its model-driven ORM/migrations, integrated forms/templates,
bundled localization breadth, and mature extension ecosystem. Hayate now has a
first-party explicit operational admin with bounded CRUD, bulk actions, redacted
history, searchable relationships, inline editing, saved views, keyset continuations,
bounded CSV export, application-scoped localization, constrained branding, and a
real-browser accessibility audit on SQLite and native Workers/D1, while retaining a
Django admin/ORM application under an ASGI prefix during incremental migration.
- **JavaScript and TypeScript edge application — competitor advantaged.** Hono remains
functionally ahead for multi-JavaScript-runtime reach and route-inferred TypeScript
RPC, and its JavaScript Workers runtime has materially better startup, memory, CPU,
and upload size than Python Workers.

Read the
[reproducible benchmark](https://github.com/hayatepy/hayate/blob/main/docs/benchmarks.md)
and the dated, source-backed
[capability matrix](https://github.com/hayatepy/hayate/blob/main/docs/capabilities.md)
for methodology, raw artifacts, profile verdicts, and limitations.
[immutable benchmark publication](https://github.com/hayatepy/hayate/blob/9e27b0191c7fa9f920ad6fe5b126e190268afba2/benchmarks/competitive/results/2026-07-28-hayate-0.15.1-macos-arm64.md) and the dated, source-backed
[capability matrix](https://github.com/hayatepy/hayate/blob/9e27b0191c7fa9f920ad6fe5b126e190268afba2/docs/capabilities.md) for methodology, raw artifacts,
profile verdicts, and limitations.

## Choose by outcome

Expand All @@ -67,7 +88,8 @@ for methodology, raw artifacts, profile verdicts, and limitations.
## Evidence, not platform claims

- The golden app runs direct tests, a real Uvicorn/SQLite flow, and a real
workerd/D1 flow. HTTP, identity, OpenAPI, and MCP share one application core.
workerd/D1 flow. HTTP, identity, OpenAPI, MCP, and operational admin share
one application core.
- The core compatibility gate installs an unpublished Hayate wheel into auth,
fetch, MCP, OpenAPI, and generated application repositories before release.
- The feature-complete Workers default is a `WorkerEntrypoint` class. The
Expand Down
76 changes: 76 additions & 0 deletions profile/README.md.in
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
# hayatepy

**Web-standards-first Python for applications that run across ASGI, Cloudflare
Workers, and AWS Lambda.**

Hayate keeps one WHATWG `Request`/`Response` application core while runtime
adapters and optional features are mounted around it. Use the same application
logic on a conventional Python server or directly inside Cloudflare workerd.

## Start here

1. Follow the [single quickstart](https://github.com/hayatepy/.github/blob/main/docs/START.md).
2. Use the [executable production golden app](https://github.com/hayatepy/golden-app)
for Cloudflare Access, OpenAPI, MCP, checked SQL, operational administration,
SQLite/D1, and deployment.
3. Check the [generated compatibility evidence](https://github.com/hayatepy/.github/blob/main/docs/COMPATIBILITY.md)
before selecting versions or runtimes.

Building a real API, MCP backend, or Workers application? Help shape the v1
contract through the bounded
[design-partner program](https://github.com/hayatepy/.github/blob/main/docs/DESIGN_PARTNERS.md).

## Why Hayate

Hayate is strongest when one Python application must combine typed HTTP,
MCP, authorization, and checked data access across conventional ASGI servers,
native Cloudflare Workers, and AWS Lambda.

The recorded ${benchmark_date} same-workload HTTP baseline measured:

${benchmark_table}

${benchmark_summary}

The 14-point contract is a shared-workload result, not a universal standards
score. Feature breadth is evaluated separately and without a weighted winner:

${profile_verdicts}

Read the
[immutable benchmark publication](${benchmark_url}) and the dated, source-backed
[capability matrix](${capabilities_url}) for methodology, raw artifacts,
profile verdicts, and limitations.

## Choose by outcome

| I want to… | Start with |
|---|---|
| Build a web API on ASGI, Workers, or Lambda | [`hayate`](https://github.com/hayatepy/hayate) |
| Generate OpenAPI 3.1 and typed clients | [`hayate-openapi`](https://github.com/hayatepy/hayate-openapi) |
| Expose MCP 2025-11-25 tools | [`hayate-mcp`](https://github.com/hayatepy/hayate-mcp) |
| Add sessions, API keys, OAuth, or an authorization server | [`hayate-auth`](https://github.com/hayatepy/hayate-auth) |
| Use checked SQL with PostgreSQL, SQLite, or D1 | [`hayate-sql`](https://github.com/hayatepy/hayate-sql) |
| Make portable outbound requests | [`hayate-fetch`](https://github.com/hayatepy/hayate-fetch) |
| Generate an integrated application | [`create-hayate`](https://github.com/hayatepy/create-hayate) |

## Evidence, not platform claims

- The golden app runs direct tests, a real Uvicorn/SQLite flow, and a real
workerd/D1 flow. HTTP, identity, OpenAPI, MCP, and operational admin share
one application core.
- The core compatibility gate installs an unpublished Hayate wheel into auth,
fetch, MCP, OpenAPI, and generated application repositories before release.
- The feature-complete Workers default is a `WorkerEntrypoint` class. The
optional global handler is an explicitly HTTP-only compatibility mode.
- Public releases include locked inputs, SPDX SBOMs, and GitHub attestations.

All packages are pre-1.0. Use the compatibility page for the exact evidence
snapshot rather than assuming every pre-1.0 line can be mixed freely.

## Contributing and security

See the organization-wide
[contributing guide](https://github.com/hayatepy/.github/blob/main/CONTRIBUTING.md).
Report vulnerabilities privately through the affected repository's
**Security → Report a vulnerability** flow.
Loading