
CherryPy
Python web frameworks
Web frameworks
- Features
- Ease of use
- Ease of management
- Quality of support
- Affordability
- Market presence
Take the quiz to check if CherryPy and its alternatives fit your requirements.
Completely free
Small
Medium
Large
- Arts, entertainment, and recreation
- Information technology and software
- Retail and wholesale
What is CherryPy
CherryPy is an open-source, minimalist Python web framework for building HTTP-based web applications and APIs. It provides an embedded, production-capable HTTP server and a simple object-publishing approach for mapping URLs to Python code. It is typically used by developers who want a lightweight framework with few required dependencies and who prefer to assemble components (templating, ORM, auth) as needed.
Embedded HTTP server included
CherryPy ships with an integrated HTTP server, so applications can run without requiring a separate web server during development or for some production deployments. This reduces setup steps compared with frameworks that assume an external WSGI server by default. It also supports running behind a reverse proxy when a dedicated front-end server is preferred.
Minimal core and dependencies
The framework keeps a small core and does not mandate a full-stack set of components. Teams can choose their own templating, data access, and authentication libraries rather than adopting a prescribed stack. This can be useful for services and internal tools where a narrow set of features is required.
Straightforward URL-to-code mapping
CherryPy’s object publishing model maps URL paths to Python objects and methods in a direct way. This can make small services easy to structure and reason about without extensive configuration. The approach can be attractive for developers who want a simple request-handling model and explicit control over application flow.
Smaller ecosystem and mindshare
Compared with more widely adopted Python web frameworks, CherryPy has a smaller community footprint and fewer third-party extensions tailored specifically to it. This can increase the amount of integration work needed for common needs like admin interfaces, authentication patterns, or scaffolding. Hiring and onboarding may also be harder if most developers are familiar with other frameworks.
More DIY for full-stack apps
CherryPy does not provide an opinionated, batteries-included stack for ORM, migrations, forms, or templating. For larger web applications, teams often need to select and integrate multiple libraries and establish conventions themselves. This can add architectural overhead and increase variability across projects.
Less built-in modern tooling
Out-of-the-box support for features such as automatic API schema generation, async-first request handling, or integrated background task patterns is limited compared with some newer or more feature-rich frameworks. Teams may need additional components to meet contemporary API and observability expectations. This can lengthen time-to-standardization for production deployments.
Plan & Pricing
| Plan | Price | Key features & notes |
|---|---|---|
| Open-source (Community) | $0 — Free (BSD license) | Full framework source available; installable via pip; no paid tiers listed on official site; enterprise support available via Tidelift (referenced on official site) |