ShippedQuarkus hosting
on Shipped.
Build your Quarkus application the way your project needs, then ship its production artifact as a running service.
Choose your production packaging
Quarkus supports JVM and native application packaging, with different build requirements for each. Put the tested artifact and its runtime dependencies in a suitable container. Shipped runs that service, so choosing Quarkus does not require you to adopt or manage a particular cluster setup for your application.
Make extension configuration explicit
Your Quarkus extensions determine which database, messaging, and application capabilities the service uses. Include the required extensions in the build and supply deployment-specific credentials as secrets. Check which settings are fixed during the build and which can change at runtime before promoting the same artifact between environments.
Validate the artifact you intend to release
Test your chosen JVM or native build in staging with real application flows and representative data. Build success alone does not prove every integration behaves as intended. Deployment logs show startup and request failures, while release history gives you a clear earlier application version to restore if needed.
A little more detail
Questions about Quarkus?
Must Quarkus run on Kubernetes?
No. A Quarkus application can run as a regular process or container. Shipped handles the infrastructure around the service you deploy.
Can I switch between JVM and native builds without testing?
Treat them as different build outputs with their own requirements. Validate the selected output and its integrations before deploying it to production.
Java
Run Java applications on Shipped with your JVM and build tooling, private configuration, data services, and dedicated capacity options.
Explore Java
Docker
Deploy containerized applications on Shipped with your runtime and system dependencies, connected services, domains, secrets, and rollbacks.
Explore DockerStaging and production
Use separate staging and production environments in Shipped, each with its own services, data, secrets, addresses, and resource usage.
Explore Staging and productionSecrets
Manage application secrets in Shipped, connect them to the right services and environments, and keep credentials out of Git and frontend bundles.
Explore SecretsFrom your workspace to the web