ShippedWeb services
Run the application server your product needs. Shipped takes care of deploying it and connecting it to the world.
Run your application’s server
Deploy a dynamic website, server-rendered frontend, or full-stack application with its own start command and runtime configuration. Shipped builds the application and checks that the service is ready before sending it traffic. Your app keeps its framework and routing, while Shipped handles the surrounding deployment and public endpoint.
Connect more than a web process
A useful application often needs a database, uploaded files, or work that happens outside a request. Add those resources to the same project and connect them to the appropriate service. Keep durable data in a database or object storage, so replacing an application release does not depend on preserving its temporary local filesystem.
Match capacity to the application
Choose resources that fit your application’s memory, CPU, startup, and traffic needs. Use logs and resource usage to understand whether the app needs more capacity or a code change. You can grow application compute independently from its database and storage, and choose a dedicated server when you want customer-exclusive runtime capacity.
A little more detail
Questions about Web services?
How is a web service different from a static site?
A web service runs application code on the server to handle requests. A static site serves prebuilt files. Use a web service when your application needs server rendering, private backend logic, or dynamic request handling.
Where should my application store uploaded files?
Use object storage for durable uploads and a database for structured records. Application-local files are temporary unless you have explicitly configured a supported persistent storage solution.
Static sites
Deploy static websites and frontend builds on Shipped with custom domains, HTTPS, CDN delivery, and release history for your published assets.
Explore Static sitesPostgreSQL
Connect a managed PostgreSQL database to your Shipped application, with private access, backups, and capacity that grows independently from compute.
Explore PostgreSQLBackground workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workers
Next.js
Ship Next.js pages, server routes, and app services together. Deploy from your agent or GitHub with domains, secrets, logs, and rollbacks.
Explore Next.jsFrom your workspace to the web