ShippedMicronaut hosting
on Shipped.
Take your Micronaut service from a checked build to a live endpoint. Keep its application structure and let Shipped handle the infrastructure.
Deploy the result of your compile-time setup
Micronaut uses compile-time processing for parts of its application infrastructure, including dependency injection. Keep the build configuration and processors your project requires, then package the resulting app with its runtime. Shipped runs the service without changing how your controllers, clients, and application components are assembled.
Separate the artifact from private settings
Database URLs, credentials, and integration endpoints should come from deployment configuration rather than being embedded in the build. Connect the application to the data services it uses and provide sensitive values through secrets. Staging can then run against test resources while production uses customer-facing systems.
Check service behavior where it will run
Use a staging deployment to test request handling, configuration binding, and outgoing client calls. If your application uses a native build, validate that actual artifact rather than relying only on JVM tests. Logs and deployment history give you context for failures after a release reaches the live service.
A little more detail
Questions about Micronaut?
Can Micronaut deploy as a regular containerized service?
Yes. Package the application with the runtime and dependencies its production build needs, then run it as a web service or worker.
Can runtime secrets replace build-time configuration?
Only for settings the application reads at runtime. Build-time decisions must be supplied during the build. Check the Micronaut modules your application uses before deciding where each value belongs.
Java
Run Java applications on Shipped with your JVM and build tooling, private configuration, data services, and dedicated capacity options.
Explore JavaSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore SecretsStaging 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
Docker
Deploy containerized applications on Shipped with your runtime and system dependencies, connected services, domains, secrets, and rollbacks.
Explore DockerFrom your workspace to the web