Can I use my coding agent with Wodby? Do I need one?

Use built-in Wodby Agent chats for workspace coding and organization operations, or connect a supported coding agent through MCP to plan migrations, prepare staging deployments, and troubleshoot applications using Wodby workflows. An agent is optional: you can continue using the dashboard, CLI, and API.

How do I control what an agent can change?

Wodby Agent organization chats ask before platform changes. Workspace chats offer approval settings and ask before Git pushes by default; file edits do not require approval. For an external agent, use an OAuth connection with read-only permissions to start. OAuth scopes limit the available operations, and your Wodby permissions determine which resources the agent can access. Grant additional scopes only when needed, agree on the changes before execution, and revoke credentials when access is no longer needed. Review MCP-initiated tasks in task history; it is not a record of every read or the complete conversation.

What does using an agent with Wodby cost?

Built-in Wodby Agent chats use your organization’s AI credits. Workspace compute and storage are billed separately. MCP access is included with free and paid Wodby 2 plans. Your plan limits and feature requirements still apply. Agent-created services, builds, storage, and infrastructure follow normal billing. When you connect an external agent, charges from your agent or model provider are separate.

Do I need to have an account on a cloud provider to use Wodby?

You can connect your own managed Kubernetes provider or use one dedicated server for self-hosted Kubernetes. Alternatively, you can use Wodby Cloud when you do not want the cluster in your own cloud account or on your own server.

Can I use Wodby with a dedicated server?

Yes. Wodby supports budget single-server self-hosted Kubernetes setups with K3s, a lightweight open-source Kubernetes distribution, when you do not need Kubernetes scaling.

I couldn't find my specific application stack, how do I start?

Start with the closest pre-configured stack and customize it, or build a stack from managed services. You can also contact Wodby to request a new stack.

Will I be vendor locked-in to Wodby?

No. Wodby is built on open standards like Kubernetes. You can disconnect your cluster and keep running your apps, but Wodby-managed tasks stop.

I have a small website (PHP, MySQL). How much would it cost? What if I deploy 10 of them?

Pricing is based on total app services. One site with Nginx, PHP-FPM, and MySQL is 3 services and falls under the $48/month minimum tier. Ten such sites total 30 services and cost $60/month. Extra CI/CD minutes and registry storage are billed separately.

Deploy Java

Deploy Java applications with Wodby’s managed Java stack. Start from a reusable application setup, keep environments consistent, and ship JVM web services, APIs, and backend applications without rebuilding the delivery platform around each project.

Start with Wodby View Java stack

Start with a managed Java stack

Use a ready-to-run Java stack and boilerplate instead of assembling the runtime, supporting services, and deployment workflow from scratch.

Keep application services organized

Run JVM web services, APIs, and backend applications with clear service boundaries and environment configuration that stays consistent across deployments.

Use one workflow for delivery and operations

Keep CI/CD, routes, certificates, backups, and scaling controls in the same Wodby workflow.

Build and release

What a Java deployment does on Wodby

A Java deployment compiles your repository with Maven or Gradle during the image build and keeps only the runnable jar. The build tool is picked from the files at the root of the repository.

Maven or Gradle, picked from the root

A Maven project file at the repository root selects Maven, through the Maven wrapper when the repository has one. Gradle build files select the Gradle wrapper, which the repository must contain.

Several jars need a hint

Source, javadoc, test, and plain jars are ignored. When the build still leaves more than one jar, as a multi-module project does, a build variable names the jar to run.

Build arguments and a custom command

One build variable adds arguments to the Maven or Gradle run, and another replaces the build command altogether. A Dockerfile in the repository replaces the service's own and must still end by starting the server.

Workspace rebuilds on every change

In a development workspace Wodby rebuilds the checkout after each change and restarts the application, which usually takes seconds. If a build fails, the last good build keeps running and the compiler errors appear in the service logs.

Read the Java stack guide for setup steps, settings, and limits.

Bring an existing application

Plan your Java migration with your agent

Give your coding agent access to your repository and connect Wodby through MCP. Ask it to map your app to maintained services and flag what needs to change before deploying.

Review the plan first, then approve an isolated staging deployment. Production data transfer and cutover need separate approval. MCP access does not itself grant access to your repository.

Connect your agent Read the migration workflow

Java migration planning prompt

Use get_wodby_guidance to load the Wodby migration workflow. Inspect this Java application repository and propose a Wodby deployment plan. Identify the runtime, database, background jobs, persistent files, and required secret names without revealing values. List missing information and plan an isolated staging deployment. Do not create resources, transfer production data, change DNS, or deploy anything yet.

A modern deployment model for Java

Java teams benefit from repeatable builds, predictable environment configuration, and a clean way to operate application and supporting services together.

Wodby packages that model as a managed stack on Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes, so teams can standardize delivery without maintaining a separate platform for every Java project.

A practical fit for Java workloads

Deploy JVM web services, APIs, and backend applications from a reusable stack and boilerplate.
Keep application, worker, database, and cache services separated where the stack needs them.
Use consistent configuration across development, staging, and production environments.
Reduce custom work around releases, routes, certificates, backups, and scaling.

What you get with Wodby

Managed Java stack for modern container-based deployments
Built-in CI/CD with image builds, deployment history, and rollback attempts
Controlled automatic updates for stack services, app environments, and infrastructure
Automated backups and imports for safer releases and migrations
Managed routes, endpoints, and domain setup
App service controls for settings, resources, links, volumes, actions, and terminal access
Open, portable infrastructure via Wodby’s platform model

How Java deployment works on Wodby

1
Choose Wodby Cloud, managed Kubernetes, or a single-server self-hosted Kubernetes setup.
2
Create a new app from the Java stack and its boilerplate, then connect your repository.
3
Configure services, domains, environment variables, persistent volumes, and databases as needed.
4
Deploy through the built-in CI/CD workflow and scale application or worker services when demand changes.

Read more about stack management in our documentation.

Suitable for Java developers, backend teams, and service-based products

This setup is designed for teams that want to ship Java applications with repeatable environments and less platform work around every project.

Wodby provides the managed Java stack and delivery workflow while preserving Kubernetes-based infrastructure choices as requirements grow.

Still choosing where to run it? Compare the options on the Java hosting page.

View pricing Explore infrastructure features

Start deploying

Want to launch Java with less setup overhead?

Start with Wodby's managed Java stack, connect your repo, and handle deployments, environments, and operations in one place.

Start with Wodby View Java stack

Stack-specific feature

Start from the Wodby Java boilerplate

The Java boilerplate is a small web application on the JDK’s built-in HTTP server, with no other dependencies. It is a working project to deploy first and replace with your own code.

It builds with Maven and runs its tests in the pipeline, which shows where the build and the tests of your own project belong.

View the Java boilerplate on GitHub

Hosting options

Choose the hosting model that fits your team

Run Wodby on your own managed Kubernetes, on a budget self-hosted Kubernetes server, or on Wodby Cloud. Wodby maintains the cluster on all three.

Managed Kubernetes in your cloud account

Keep infrastructure in your own cloud account. Wodby provisions the cluster through AWS, GCP, DigitalOcean, Azure, or another supported provider and keeps it up to date.

View managed Kubernetes

Kubernetes on your own server

Use your own dedicated server or VM for the lowest cost. Wodby installs Kubernetes, keeps it up to date, and deploys your apps; you keep the server’s operating system updated.

Explore self-hosted Kubernetes

Wodby Cloud

Use Wodby Cloud when you want the cluster hosted by Wodby instead of in your own cloud account or on your own server.

See Wodby Cloud

Integrations

Keep third-party integrations organized and under control across all of your apps and environments

Connect services once and reuse them across your apps. Keep credentials out of repositories, manage configuration centrally, and override values for each environment.

Connect the services your apps already use

See all integrations

Stack preview

Java stack preview

Stack service	Base service	Role
Java	Java	Primary
PostgreSQL	PostgreSQL	Disabled by default
Valkey	Valkey	Disabled by default
Mailpit	Mailpit	Disabled by default
OpenSMTPD	OpenSMTPD	Disabled by default
Gotenberg	Gotenberg	Disabled by default
Cloud PostgreSQL	Cloud PostgreSQL	Disabled by default
OpenTelemetry Collector	OpenTelemetry Collector	Disabled by default

See full stack service table

Keep moving

Explore the Java setup, then start your own deployment

Once you've reviewed the stack structure, create an account to launch Java, connect your repository, and keep delivery inside the same workflow.

Create account Check pricing

Trusted by developers and businesses worldwide since 2015

Wodby is a reliable cloud infrastructure partner for your business.
See what our customers say about their experience with Wodby.

We moved our Drupal hosting to use Wodby and changed our development workflow to use Docker at the same time. Now we can concentrate on Drupal development and we're not losing time configuring servers etc. When a site needs additional resources or hosting in a different region we can be way more responsive as deploying a new instance takes no time at all.
Tony Miller
Eighty Options
Wodby’s innovative infrastructure helped us to increase the speed and simplify our app deployment, while also leaving us the freedom of handling our hosting and not locking us on a specific pattern. We are now much more robust for future growth and will be able to innovate faster.
Martin Normann Lund
Ramsalt Lab

FAQ

Frequently Asked Questions

Have questions? We've got answers. If you don't see your question here, feel free to reach out.

Get started

Ready to deploy Java?

Choose Wodby Cloud, managed Kubernetes, or your own server, then deploy stacks with CI/CD, backups, SSL, integrations, and environment management in the same platform.

Run the same stack workflow on Wodby Cloud, managed Kubernetes, or your own server
Deploy app environments for production, staging, previews, and development
Use Wodby CI or your existing pipeline with the Wodby CLI
Keep backups, certificates, integrations, and access control in the platform

Start for free

No credit card required

$0/month

10 app services
30 minutes of integrated CI
5 GB of private registry
Stacks & integrations
Technical domains with SSL

Create free account

Upgrade when you need more capacity