From your first prompt to a working change

Develop in a workspace and operate apps with Wodby Agent. Explore common use cases and copy a prompt to try in your own chat.

Dev workspaces →

Choose a development workspace

Select Development workspace in the app settings step when creating an environment. Your checkout and supporting services run together.

Make a change in your running application

Install the Drupal Redis module with Composer and enable it with Drush. Check whether the PHP Redis extension and a Redis-compatible service are available. Leave the changes uncommitted for review.

Open Chats in a Drupal workspace and ask Wodby Agent to install a module. It can check the running services, edit the checkout, and run Composer and Drush.

Inspect the files in your shared checkout

Review the uncommitted changes in this workspace. Explain what each file changes and which checks I should run before committing. Do not modify, commit, or push anything.

Open Status and select a changed file to view its diff. You can review edits made by an agent or through your SSH editor in the same place.

Wodby Agent →

Describe the stack your app needs

Build a new stack for my app. It uses Flask and PostgreSQL. Show me the proposed services and ask before creating it.

Start an organization chat and describe your application. The agent can inspect available services and propose a stack, asking for approval before creating it.

Find service versions that need attention

Check if any of my apps use EOL versions of services. Summarize by service and version, and suggest next steps. Do not change anything.

Ask the agent to check your applications against the service catalog and suggest an upgrade plan without changing anything.

Bring the conversation into a workspace

Inspect this application and suggest the smallest change needed to use its cache service. Explain the files you would change before editing anything.

Open Chats inside a workspace to work on application code. The agent can inspect files, edit the checkout, and run commands against your development environment.

Build and deploy

Build, deploy, and maintain applications through one release model

Connect source code to repeatable releases, reusable stacks, isolated environments, and controlled maintenance.

Run build, deploy, post-deployment, validation, and rollback workflows from the same release history.
Keep stack changes and automatic updates reviewable before they reach production.

Operate and maintain

Configure, observe, protect, and scale running applications

Keep service configuration, runtime visibility, data protection, and capacity decisions close to the application.

Stream logs, inspect metrics, and open a web shell when an incident needs direct investigation.
Protect application data and choose the right database and scaling model for each workload.

Secure and control access

Manage application routing, HTTPS, private access, and team permissions

Keep public endpoints, private applications, certificates, and platform permissions distinct and easier to manage.

Configure technical and custom domains, redirects, authentication, HSTS, and managed or uploaded TLS certificates.
Separate who can reach a running application from who can operate the Wodby project.

Connect services and infrastructure

Connect external services and keep the deployment model portable

Attach integrations without hardcoding credentials, retain configuration in Git, and choose infrastructure separately from application operations.

Reuse approved external service connections across applications and environments.
Keep application and stack configuration based on inspectable, portable building blocks.

Next step

Start with the feature area that matches how your team works today, then grow into the rest of the platform

Start with release automation, application environments, or data workflows. Add the other capabilities as your operational requirements grow.