Add spikard to Web Frameworks

[Goldziher]

Add spikard

Category: Web Frameworks → Asynchronous

Single project, per the one-project-per-PR guideline.

Why it qualifies:

• 105+ GitHub stars, MIT-licensed, and actively maintained (commits within the last few days).
• Production-ready release on PyPI with a clear README containing installation and usage examples.
• Distinct value: A non-ASGI web framework — a different architecture from every framework currently listed, which are ASGI-based (Litestar, Starlette) — built on an ultra-fast Rust core with type-safe routing.

It is a Python-first library (installable from PyPI) with a Rust core for performance — the same architecture as the already-listed xberg entry.

[abdullahra634-dotcom]

Add spikard

Category: Web Frameworks → Asynchronous

Single project, per the one-project-per-PR guideline.

Why it qualifies:

• 105+ GitHub stars, MIT-licensed, and actively maintained (commits within the last few days).
• Production-ready release on PyPI with a clear README containing installation and usage examples.
• Distinct value: A non-ASGI web framework — a different architecture from every framework currently listed, which are ASGI-based (Litestar, Starlette) — built on an ultra-fast Rust core with type-safe routing.

It is a Python-first library (installable from PyPI) with a Rust core for performance — the same architecture as the already-listed xberg entry.

[JinyangWang27]

@Goldziher Thanks for the submission. My main concern is: what does Spikard offer Python developers that is meaningfully different from FastAPI?

The proposed description mentions a non-ASGI architecture, a Rust core, performance, and type-safe routing, but it does not clearly explain the practical benefit of choosing Spikard over an established framework such as FastAPI. FastAPI already provides type-based request validation, automatic OpenAPI documentation, security utilities, WebSocket support, dependency injection, and access to the wider Starlette and ASGI ecosystem.

Could you expand the PR description to clarify:

• which Python use cases Spikard handles better than FastAPI;
• which FastAPI or ASGI capabilities are unavailable or work differently;
• examples of real Python projects choosing Spikard for these reasons.

The project may be technically distinct internally, but for inclusion in awesome-python, the PR should establish that it offers Python users a distinct practical value rather than being another typed API framework with a different runtime.