Sillo

Python With the Pieces Already in Place.

Sillo is an async Python web framework for APIs, web applications, real-time systems, and business backends. The language does not change. You write the same Python, with the same type hints and the same async/await. What changes is how much is waiting for you when you start: routing, request validation, dependency injection, middleware, sessions, authentication, records, background work, WebSockets, OpenAPI, and testing are first-party modules sharing one configuration model.

Each of those is a solved problem with good packages behind it. The work that remains is the fitting, and that is what Sillo does once so you do not do it per project. One auth= declaration gates a route and writes its securityScheme into the OpenAPI spec. The queue and the scheduler start with the application lifecycle. Range requests, ETags, and content negotiation are middleware rather than something each project rewrites.

None of this is aspirational. The coverage floor fails the build rather than printing a warning, the type check runs on every supported Python, and the badges above read from those same workflows rather than from a number written here by hand.

• Python 3.10+
• uv for project and dependency management

uv add sillo-framework

For optional feature groups:

uv add "sillo-framework[templating]"
uv add "sillo-framework[jwt]"
uv add "sillo-framework[cache]"
uv add "sillo-framework[record]"
uv add "sillo-framework[graphql]"

For a full development setup:

uv add "sillo-framework[all]"

from sillo import SilloApp

app = SilloApp(title="My API")


@app.get("/")
async def home(request, response):
    return response.json({"message": "Hello from Sillo"})

Run it with Sillo's own server:

uv run sillo serve --reload

  ● sillo 0.1.0

    app       main:app
    url       http://127.0.0.1:8000
    routes    4
    inspect   http://127.0.0.1:8000/__sillo/requests
    mode      serving
    pid       5716

    ready in 7ms  ·  press ctrl-c to stop

  22:48:04  GET     200  /                                      409us

No import string is needed. sillo serve looks for app.main:app, main:app and app:app, and you can pin it with the SILLO_APP environment variable or a [tool.sillo] app entry in pyproject.toml. Pass one explicitly when you want something else:

uv run sillo serve api.main:app --port 9000 --workers 4

Each request is logged with the time it took, and the address in the inspect line is a clickable request log you can open while developing. Add --no-inspect to leave it out, or --plain to see the underlying server's own output instead.

sillo serve is built for development. For production, run the application under a process supervisor with a reverse proxy in front of it.

Sillo validates request bodies with Pydantic through request_model.

from pydantic import BaseModel
from sillo import SilloApp

app = SilloApp()


class CreateUser(BaseModel):
    name: str
    email: str


@app.post("/users", request_model=CreateUser)
async def create_user(request, response, user: CreateUser):
    return response.json(user.model_dump(), status_code=201)

The validated model is also available as request.validated_data.

Use Depend to inject request-scoped dependencies into handlers.

from sillo import Depend, SilloApp

app = SilloApp()


async def get_current_user():
    return {"id": "user_1", "name": "Ada"}


@app.get("/me")
async def me(request, response, user=Depend(get_current_user)):
    return response.json(user)

When a dependency needs the current request:

from sillo import Depend


def auth_header(request=Depend(get_request=True)):
    return request.headers.get("Authorization")

from sillo import Router, SilloApp

app = SilloApp()
api = Router(prefix="/api")


@api.get("/users/{user_id:int}")
async def get_user(request, response, user_id: int):
    return response.json({"id": user_id})


app.mount_router(api)

• Async ASGI application core
• HTTP routing, route groups, and mounted routers
• Request and response helpers
• Pydantic request validation
• Dependency injection with nested dependencies
• Query, header, and cookie parameter helpers
• Middleware pipeline
• CORS and CSRF support
• Sessions and authentication utilities
• API keys, JWT helpers, users, permissions, and guards
• OpenAPI generation and interactive docs
• File uploads, streaming responses, static files, and frontend fallback serving
• WebSockets, consumers, channels, groups, events, and history helpers
• Cache abstraction with memory and Redis support
• Event system and background work primitives
• Record layer for database-backed models, transactions, scopes, casting, and pagination
• Mail service utilities
• Sync and async test clients
• Model admin at /admin/ that authenticates against your own user model
• sillo command, and sillo.console for building a project's own

Sillo runs on its own. No hosted service is required to put an application into production.

The framework is opinionated at the defaults and open at the boundaries. Auth backends, middleware, cache drivers, session stores, and hashing algorithms are contracts you can implement yourself, and anything the framework does on your behalf is something you can read, override, or replace.

Sillo ships a sillo command with the framework-level operations, built on sillo.console. Inside a project it also merges in whatever that project's console.py registers, so sillo db:migrate works without the framework owning the command set. The operations underneath stay plain functions in sillo.record.commands, sillo.users.commands and sillo.work.commands, so a project that wants different names writes its own console against them.

The documentation source lives in docs/docs.

Build it locally with:

cd docs/docs
bun run build

Run the core test suite with:

python3 -m pytest -q

Some optional integrations require their extras to be installed before their tests can run.

Sillo prioritizes:

• clear APIs and useful error messages
• strong defaults with replaceable internals
• production-oriented documentation
• compatibility, migration guidance, and honest release notes
• security and reliability before broad platform expansion

BSD-3-Clause