ShippedGo hosting
on Shipped.
Bring your Go server or worker from source to a running service. Keep your framework choice and make the deployment part of your development workflow.
Build and run your Go application
Package a Go build for the deployment environment and run the resulting application as a service. Include runtime files and system libraries when your program needs them. Shipped handles the server infrastructure and public endpoint while you control the HTTP handlers, process behavior, and application configuration.
Use the libraries that fit the job
Your service can use the standard HTTP library or a framework such as Gin, Echo, or Fiber. Connect PostgreSQL, Redis, and object storage through compatible clients. Keep connection settings outside the compiled code so staging and production can use the same application with different resources.
Deploy workers as deliberately as APIs
A Go process that consumes a queue does not need a public route. Run it as a background worker, or schedule a command for periodic processing. Use logs to follow results and failures, and keep durable work state in a service that survives application restarts and releases.
A little more detail
Questions about Go?
Can I use Go without a web framework?
Yes. A server built with the standard library can run as a web service. Provide its production configuration and listen on the address and port expected by the deployment.
Is every Go binary completely standalone?
No. Some programs need system libraries, certificates, templates, or other files. Include the runtime requirements of your application in its deployment image.
Gin
Take Gin applications live on Shipped with HTTPS, private configuration, database connections, logs, and independent app deployments.
Explore GinEcho
Deploy Echo services on Shipped with domains, HTTPS, secrets, persistent data services, and a staging environment for API changes.
Explore EchoFiber
Ship Fiber apps on Shipped with a production Go runtime, connected data services, domains, secrets, and deployment logs.
Explore FiberBackground workers
Run background workers on Shipped for queues, imports, notifications, and long-running application tasks, with separate resources and deployment history.
Explore Background workersFrom your workspace to the web