ShippedGin hosting
on Shipped.
Keep your Gin routes and middleware. Shipped runs the compiled service and connects it to a public URL and the resources your API needs.
Deploy the router inside a Go service
Build your Gin application for its production environment and package any files it needs at runtime. The service starts your HTTP server while Shipped handles its public address and HTTPS. Your route groups, request binding, and middleware continue to define how clients interact with the API.
Put database access behind your handlers
Use the Go database libraries you prefer to connect Gin handlers to PostgreSQL and other app services. Supply connection details through secrets and return only the data clients need. For file uploads, use persistent storage rather than assuming files written inside the service will survive the next deployment.
Review API behavior at a staging address
Check route parameters, validation failures, and authentication middleware against a separate environment before updating production. Your coding agent can deploy through MCP as you work. Application logs and deployment history help you relate a change in client behavior to the exact service release that is running.
A little more detail
Questions about Gin?
Does Shipped require a particular Gin project layout?
No. Keep your project layout and build command. The deployment needs a working production server entry point and the runtime files your application uses.
Can Gin use an existing PostgreSQL database?
Yes. Configure a compatible Go client with the database connection settings and network access it requires. You can move app hosting and data in separate steps.
APIs
Host application APIs on Shipped with HTTPS endpoints, private service configuration, health checks, logs, and managed database connections.
Explore APIsPostgreSQL
Connect a managed PostgreSQL database to your Shipped application, with private access, backups, and capacity that grows independently from compute.
Explore PostgreSQLStaging and production
Use separate staging and production environments in Shipped, each with its own services, data, secrets, addresses, and resource usage.
Explore Staging and production
Go
Deploy Go web services and workers on Shipped with managed infrastructure, databases, secrets, domains, and deployment logs.
Explore GoFrom your workspace to the web