Supported stacks

Fiber hosting
on Shipped.

Build with Fiber’s routing and middleware, then deploy the Go service behind them. Shipped handles the infrastructure needed to make it reachable.

Run the server your Fiber app defines

Package your compiled application and the assets it needs, then deploy it as a web service. Keep the routing, middleware, and server settings that match your Fiber application. Shipped supplies the external URL and HTTPS while the Go process handles incoming requests and application responses.

Use state that survives a new process

Session records, saved application data, and job progress need a durable home when they must survive restarts. Connect appropriate database or cache clients and keep their settings in secrets. Store user uploads outside the release image so replacing application code does not also replace customer files.

Check integrations before each release

Middleware and HTTP integrations should be tested against the Fiber version and adapters your project uses. Use a staging deployment to exercise those paths with realistic requests. Ship the checked app through your coding agent or GitHub and inspect service logs when a request needs investigation.

A little more detail

Questions about Fiber?

Can I assume any Go HTTP middleware works with Fiber?

Check the middleware and adapters against your Fiber version. Fiber has its own handler and context APIs, so integration compatibility should be tested rather than assumed.

Can I deploy Fiber with a custom container?

Yes. Package the compiled program and any runtime dependencies in your image, then provide the service start configuration.

From your workspace to the web

Ready to ship your app?

Start shipping