FastAPI hosting
on Shipped.
Ship your Python API and let people use it. Keep FastAPI’s request models and endpoint behavior while Shipped runs the service.
Deploy the API with its server
Run FastAPI through a production ASGI server with the dependencies and start command your app needs. Shipped gives that service an HTTPS address and a place behind your custom domain. Your endpoint definitions, validation, and generated API documentation remain part of the application you deploy.
Connect API requests to useful work
Use PostgreSQL to store application records and object storage for uploaded documents or generated results. Add credentials through secrets instead of including them in source. When a request starts substantial processing, hand that work to a separate worker and let clients check its stored progress or result.
Test contracts before changing the live API
A staging deployment lets you check schema changes, authentication, and error responses with the clients that depend on them. Deploy from your coding agent or GitHub, then use logs to follow application behavior. Keep a previous release available when a code change needs to be rolled back.
A little more detail
Questions about FastAPI?
Is an async endpoint enough for heavy computation?
No. CPU-heavy work can still occupy server resources. Put substantial or durable processing in a worker when it should run independently of the request and web service.
Can I keep FastAPI’s generated API documentation?
Yes. The documentation routes are part of your FastAPI app. Decide in your application whether they should be public, protected, or disabled in production.
From your workspace to the web