Uvicorn
Uvicorn holds place 10 of 14 in our application servers ranking. The catalogue describes it as: ASGI web server for Python async frameworks, run with one command.
Vendors can pay for more visibility on this site; the link to Uvicorn is marked like every other vendor link. How that works.
Visit Uvicorn See it in the application servers ranking
At a glance
| Headquarters | Not stated by the vendor |
|---|---|
| Best for | Teams running async Python frameworks needing WebSockets and HTTP/2 from one server |
| Deployment | Vendor does not say, as far as we read |
| Pricing model | BSD-3-Clause package; the site lists no prices or plans |
| Free plan | None recorded |
| API | Nothing recorded about an API |
What is Uvicorn?
Uvicorn is an ASGI web server implementation for Python, aimed at async frameworks. The project website says it currently supports HTTP/1.1, HTTP/2 and WebSockets, and shows the basic use as uvicorn main:app on the command line.
Beyond the command, the site describes running it from code through uvicorn.run(), through the uvicorn.Config and uvicorn.Server classes, and through an async entry point, uvicorn.Server.serve(), for programs that already have an event loop. The code lives in the Kludex/uvicorn GitHub repository under the BSD-3-Clause licence. The pages we read name no company or country as operator, state Python versions only in a badge image and list no prices or plans.
Uvicorn key features
- ASGI server for async code. The site positions Uvicorn as an ASGI implementation for Python, so it serves applications written against the async interface rather than the older synchronous WSGI one.
- HTTP/1.1, HTTP/2 and WebSockets. The home page says all three are currently supported. For applications that push messages to browsers, WebSocket support in the same server avoids running a second process for that traffic.
- Command-line launch. Running uvicorn main:app starts an application from a module and object name. The site presents this as the standard way in, which keeps a first test to a single line.
- Programmatic control. uvicorn.run() starts a server from Python code, while uvicorn.Config and uvicorn.Server give finer control. This suits scripts, test harnesses and tools that embed the server.
- Async entry point. uvicorn.Server.serve() is described for existing async environments, where another event loop owner needs the server to run as one task rather than taking over the process.
- Factory loading. The --factory flag loads the application from a factory function instead of a ready object. That helps when configuration must be built at start-up rather than at import time.
- Separate worker package. The uvicorn.workers module for Gunicorn is described as deprecated and due for removal, and the site points to the uvicorn-worker package instead, so a Gunicorn pairing has a stated path forward.
Who Uvicorn suits
- Developers of async APIs. A team building on an async Python framework can run the application locally and in production with the same uvicorn main:app command, keeping the development and deployment path short.
- Authors of embedded or test servers. Programmers who need a server inside a script or test suite can call uvicorn.run() or build a Config and Server pair, without shelling out to a separate process.
- Teams migrating a Gunicorn setup. Anyone using the old Gunicorn worker module learns from the site that it is deprecated, and can move to the uvicorn-worker package before the module is removed.
Getting started with Uvicorn
The project website shows the quickest start: write an ASGI application in a module, then run uvicorn main:app, where main is the file and app the object. If the application is built by a function, add the --factory flag. For code-driven launches, call uvicorn.run(), or create a uvicorn.Config and hand it to uvicorn.Server.
Inside a program that already runs an event loop, use the async uvicorn.Server.serve() entry point. The website does not name the supported event loops, and it shows the supported Python versions only in a badge image, so check the repository for compatibility before installing into an older environment. The pages we read give no deployment guide beyond these entry points.
Our verdict on Uvicorn
Uvicorn is an ASGI server for async Python frameworks that supports HTTP/1.1, HTTP/2 and WebSockets, started with uvicorn main:app or driven from code through uvicorn.run and uvicorn.Server.
Its Gunicorn worker module is deprecated in favour of a separate uvicorn-worker package. The site names no company or country and shows Python versions only in a badge image, so confirm compatibility in the repository.
In our application servers ranking Uvicorn stands at #10 of 14: Puma sits directly above it and Open Liberty directly below. From place 4 the established names follow in their ranked order; we publish no numeric score.
The vendor states no country of establishment, so Uvicorn is left out of the regional count for this list.
The case for and against Uvicorn
- Uvicorn is an ASGI server for async Python frameworks that supports HTTP/1.1, HTTP/2 and WebSockets, started with uvicorn main:app or driven from code through uvicorn.run and uvicorn.Server.
- HTTP/2 and WebSockets, one of the three traits the catalogue lists for Uvicorn.
- BSD-3-Clause, one of the three traits the catalogue lists for Uvicorn.
- Where it fits: Teams running async Python frameworks needing WebSockets and HTTP/2 from one server.
- Catalogue tag: ASGI.
- The site names no event loops in text and gives Python versions only in a badge image.
- The uvicorn.workers module for Gunicorn is deprecated and will be removed, so Gunicorn setups need the separate uvicorn-worker package.
- Look elsewhere if you are Synchronous WSGI applications or buyers wanting commercial support.
Uvicorn pros and cons in practice
- One command, uvicorn main:app, starts an application, and the same server can be driven from code.
- HTTP/1.1, HTTP/2 and WebSockets are all named as supported on the home page.
- The BSD-3-Clause licence and the absence of prices keep adoption simple.
- The async entry point fits programs that already own an event loop.
- Supported Python versions appear only in a badge image on the site, so they must be confirmed in the repository.
- The event loops it supports are not named on the pages we read.
- The Gunicorn worker module is deprecated and will be removed, which forces a move to uvicorn-worker for existing pairings.
- No company or country is named, so there is no vendor support desk or contract.
Setup, support and exit with Uvicorn
Beyond the command line, Uvicorn can be embedded: uvicorn.run starts an application, uvicorn.Config and uvicorn.Server give finer control, and the async entry point uvicorn.Server.serve() fits code already running inside an event loop.
A --factory flag loads the application from a factory function.
Paying for Uvicorn
In the catalogue: BSD-3-Clause package; the site lists no prices or plans.
The Uvicorn website lists no prices or plans. The GitHub repository Kludex/uvicorn shows the BSD-3-Clause licence, which means the software itself carries no fee, and the only running cost is the infrastructure you host it on. The pages we read describe no paid support, hosted version or service agreement, and name no company or country as operator. A team that needs a contract, an invoice or a service level has no route to one on these pages. Budget therefore consists of engineering time and hosting rather than any subscription line.
Basis: uvicorn.dev, read for the Best Application Servers in 2026 guide (reviewed 15 November 2026).
Uvicorn: data and security
Uvicorn is a server you run on your own machines, so the requests it handles stay within your infrastructure. The pages we read include no certifications, audit statements, data processing terms or security contact, and no operating company is named.
Anything that matters for compliance, such as TLS termination, header handling and patch cadence, is therefore decided by how you deploy it and which version you run. Review the repository for release notes before relying on specific protocol behaviour in a regulated environment.
Fact sheet: Uvicorn
| Product | Uvicorn |
|---|---|
| Vendor website | uvicorn.dev |
| Head-to-head pages | Not paired so far |
| Rank there | #10 of 14 |
| Catalogue tags | ASGI, HTTP/2 and WebSockets, BSD-3-Clause |
| Primary guide | Best Application Servers in 2026 |
| Price visibility | Model recorded, no figure |
| Headquarters | Not stated by the vendor |
| Alternatives page | Not part of the alternatives set |
| Not in our data | company size and funding |
Uvicorn integrations and ecosystem
Integrations the vendor names (6):
- Gunicorn
- uvicorn-worker
- ASGI frameworks
- WebSockets
- HTTP/2
- Python asyncio programs
Where else Uvicorn is ranked
| Guide | Position |
|---|---|
| Best Application Servers in 2026 | #10 of 14 |
Alternatives to Uvicorn
These are the nearest neighbours of Uvicorn in the same list, picked on shared traits and price model.
- Gunicorn (#8 of 14): Not for: windows servers or teams wanting a commercial support contract. Pre-fork WSGI server for Python, started with a single command.
- Puma (#9 of 14): Threaded Ruby web server for Rack apps, default in Rails.
- Oracle WebLogic Server (#13 of 14): Oracle's Jakarta EE server in three editions, with 30-day cloud access. Best for: Oracle Database and Fusion Middleware shops needing clustering and failover.
- IBM WebSphere Application Server (#14 of 14): Suits: Established IBM estates running mixed on-premises and private-cloud Java workloads.
Questions about Uvicorn
9 answersWho should choose Uvicorn?
Teams running async Python frameworks needing WebSockets and HTTP/2 from one server. Less suited to: synchronous WSGI applications or buyers wanting commercial support.
What else should I look at besides Uvicorn?
The nearest neighbours in our ranking are Gunicorn, Puma, Oracle WebLogic Server and IBM WebSphere Application Server. All of them are reviewed in the same ranking.
Is Uvicorn a European company?
The vendor pages we reviewed state no country of establishment for Uvicorn, so we do not give one.
Is Uvicorn one of the top application servers?
The application servers ranking has Uvicorn at position 10 out of 14.
How much does Uvicorn cost?
The pricing entry for Uvicorn reads: BSD-3-Clause package; the site lists no prices or plans. On free access, nothing is free to use, as far as we recorded.
What does Uvicorn serve?
It is an ASGI server for async Python frameworks, started with a command such as uvicorn main:app.
Does it support HTTP/2?
The website says it currently supports HTTP/1.1, HTTP/2 and WebSockets.
Can I still use it as a Gunicorn worker?
The bundled uvicorn.workers module is deprecated and will be removed. The site recommends the separate uvicorn-worker package.
What licence does it use?
The Kludex/uvicorn repository on GitHub shows the BSD-3-Clause licence.
Uvicorn: sources
Read from the vendor’s own pages on 14 November 2026.
- uvicorn.dev: Description, protocol support, command and programmatic use, factory flag, deprecated worker module, no prices
- uvicorn.dev: No operator named, event loops and Python versions not listed in text
- github.com/Kludex/uvicorn: ASGI description, BSD-3-Clause licence
- uvicorn.dev: Absence of plans or pricing
How we rank
We test for four things rather than for features: setup time, price in practice, exit and audience. That puts Uvicorn at #10 of 14. The editorial process sets out how facts are gathered and how commercial links are handled.