ShippedAPIs
Run the backend for your web app, mobile app, or integration. Keep your API code and let Shipped handle its deployment.
Give your backend an endpoint
Deploy an HTTP API with the framework you already use, from a small service to the backend of a full product. Configure its listening port, start command, and health check. Shipped builds the release and connects it to a public HTTPS endpoint so clients can reach it without your team managing the hosting infrastructure.
Keep private work on the server
Connect the API to its database, cache, and object storage through environment-specific configuration. Use secrets for credentials that must never reach a browser or mobile bundle. Your application remains responsible for authenticating callers, checking permissions, and validating input; Shipped supplies the hosting and service connections that let you implement those rules.
Separate requests from long-running work
Keep slow imports, report generation, and other lengthy jobs in background workers when they do not need to finish inside a request. Your API can accept a job and let a worker process it. Deploy those processes with their own resources, then use logs and release history to investigate failures in the right service.
A little more detail
Questions about APIs?
Does hosting an API add user authentication automatically?
No. Shipped hosts the service and manages its deployment. Your application must implement or integrate the authentication and authorization rules needed by its users and clients.
Can my API and frontend be separate services?
Yes. Use a static site or web service for the frontend and a separate API service for the backend. Give each its own configuration and resources while keeping both in the same project.
Background workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore Secrets
FastAPI
Deploy FastAPI on Shipped with an ASGI runtime, PostgreSQL, workers, private configuration, and logs for your Python API.
Explore FastAPI
Node.js
Run Node.js services on Shipped with databases, background workers, secrets, and deployment logs. Ship from your agent or GitHub.
Explore Node.jsFrom your workspace to the web