Skip to content
Flask ergonomics, ASGI-native execution

Flasgo

Async-first Python web framework with Flask ergonomics and Django-inspired security defaults.
Current release v0.5.2 GitHub release · May 27, 2026
Deployment baseline

Install with uv, run locally with reload, and deploy under uvicorn behind a production edge or reverse proxy.

Runtime ASGI-native

Async request handling without retrofitting sync-first assumptions.

API shape Flask-like routing

Direct handlers, familiar helpers, and readable application code.

Security Defaults that hold up

Signed sessions, CSRF, host validation, and safer headers built in.

Flasgo is built for developers who want the core web-app path to stay compact and readable while still taking async execution, deployment posture, and security defaults seriously.

Execution model

Built for async from the start

Flasgo is ASGI-native, so concurrency and modern Python server workflows are part of the main path rather than a compatibility layer.

Developer experience

Familiar request and routing ergonomics

Handlers, routes, request helpers, responses, templates, and forms stay close to the Flask mental model without freezing the runtime story in the past.

Security posture

Defaults that assume deployment matters

Signed sessions, CSRF protection, host validation, SSRF guards, request limits, cache controls, and hardened headers are part of the documented baseline.

Small surface area, clear deployment story, no pretend batteries-everywhere pitch.

Flasgo covers the common Python web application path without ballooning into a giant abstraction layer. The docs focus on what the framework does, how to run it, and what assumptions matter when you move toward production.

Package

Install with uv add flasgo

Run locally with reload and keep the development loop close to a normal ASGI workflow.

Python target

>= 3.14

The framework targets current Python and leans into modern tooling instead of carrying old runtime compromises.

01

Routing and request handling

Define handlers directly, work with requests and responses clearly, and keep application flow easy to trace.

02

Templates, forms, and static files

Flasgo covers the common server-rendered application path instead of forcing an immediate jump to another stack.

03

Security-sensitive defaults

Session signing, CSRF, allowed hosts, and header defaults are treated as part of the core framework story.

04

Docs, testing, and deployment guidance

The docs cover optional OpenAPI endpoints, local iteration, production posture, and the deployment assumptions needed for a real service.