Compose stacks from reusable building blocks
Services are the parts you combine inside a stack, whether you are starting from scratch or customizing a predefined app setup.
A service is a building block inside a stack. Stacks are what you use to deploy apps, and services are the reusable parts inside those stacks: runtimes, proxies, databases, caches, search, mail, storage, and networking.
All services are versioned, Wodby manages their updates, and you can create your own services from templates. Most services are based on public Helm charts and Docker images, with special external services such as Cloud PostgreSQL as the main exception.
What services help with
Compose custom stacks
Pick the exact runtimes, databases, proxies, and support services an app needs.
Managed and versioned by default
Services are versioned, and Wodby manages service updates so stacks can adopt newer revisions in a controlled way.
Built on public charts and images
Except for special external services such as Cloud PostgreSQL, the service building blocks are based on public Helm charts and Docker images.
Create your own services
Start from a service template and bring custom service definitions into the same workflow as the rest of your stack.
Benefits
The value of the service catalog is that it gives teams reusable building blocks for stacks, rather than forcing every application to start from a blank slate.
Services are the parts you combine inside a stack, whether you are starting from scratch or customizing a predefined app setup.
All services are versioned, and Wodby manages their updates so stacks can move to newer revisions in a controlled way.
With the exception of special external services such as Cloud PostgreSQL and similar connectors, Wodby services are based on public Helm charts and Docker images.
You can create a custom service from a template and maintain it in the delivery workflow your team already uses.
Service catalog
Search for a service by name or related terms, then open it to review its capabilities, the stacks that use it, and the dependencies around it.
Search also works with related terms such as `mysql`, `varnish`, `redis`, `mail`, and `email`.
App services
Application runtimes and primary workload services used inside stacks.
Runtime service for Next.js applications that need a reusable building block inside a stack.
Source repository
wodby/service-nextjsRuntime service for Node.js APIs, workers, and custom application workloads.
Source repository
wodby/service-nodePHP runtime service for custom applications and framework-based workloads.
Source repository
wodby/service-phpWeb server and reverse proxy service for routing HTTP traffic to application runtimes.
Source repository
wodby/service-nginxSMTP service that can send mail directly or integrate with third-party delivery services for reliable outbound email.
Source repository
wodby/service-opensmtpdHTTP caching service built on Vinyl, the new name for Varnish, for accelerating responses in front of web applications.
Source repository
wodby/service-vinylHTTP caching service built on Vinyl, the new name for Varnish, for accelerating responses in front of web applications.
Source repository
wodby/service-varnishEmail testing service for capturing, previewing, and debugging outbound mail in development and staging.
Source repository
wodby/service-mailpitDocument conversion and PDF generation service for applications that need server-side rendering workflows.
Source repository
wodby/service-gotenberg3X UI service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-3xuiApache HTTP server service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-httpdApache HTTP server (PHP) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-php-httpdWorkflow orchestration service for data pipelines, scheduled jobs, and asset-based automation inside a stack.
Source repository
wodby/service-dagsterMatomo 5 service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-matomoNginx (Drupal 10) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-nginxNginx (Drupal 11) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-nginxNginx (Laravel) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-laravel-nginxNginx (Matomo) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-matomo-nginxNginx (PHP) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-php-nginxNginx (WordPress) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-wordpress-nginxOpenClaw service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-openclawPHP (Drupal 10) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-phpPHP (Drupal 11) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-phpPHP (Laravel) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-laravel-phpPHP (WordPress) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-wordpress-phpVarnish (Drupal) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-varnishVarnish (WordPress) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-wordpress-varnishVinyl (Drupal) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-drupal-vinylVinyl (WordPress) service for reusable application and infrastructure workflows on Wodby.
Source repository
wodby/service-wordpress-vinylDatabases
Relational database services and cloud database connection services.
Self-hosted MariaDB database service for applications that keep relational data inside the stack.
Source repository
wodby/service-mariadbSelf-hosted PostgreSQL database service for applications that keep relational data inside the stack.
Source repository
wodby/service-postgresSelf-hosted PostgreSQL database service with PostGIS extensions for geospatial data and spatial queries inside the stack.
Source repository
wodby/service-postgisConnection service for apps that use a managed MariaDB database instead of running it inside the stack.
Source repository
wodby/service-cloud-mariadbConnection service for apps that use managed MySQL databases such as Amazon RDS instead of running MySQL inside the stack.
Source repository
wodby/service-cloud-mysqlConnection service for apps that use managed PostgreSQL databases such as Amazon RDS instead of running PostgreSQL inside the stack.
Source repository
wodby/service-cloud-postgresDatastores & caches
Stateful services used for caching, queues, sessions, and related workloads.
Redis-compatible datastore service for caching, queues, sessions, and other in-memory workloads.
Source repository
wodby/service-valkeyIn-memory datastore service for caching, queues, sessions, and other low-latency workloads.
Source repository
wodby/service-redisCoordination service for distributed systems that need shared metadata and orchestration state.
Source repository
wodby/service-zookeeperSearch & indexing
Indexing and search services for content and application data.
Search indexing service for content-heavy applications that need full-text search.
Source repository
wodby/service-solrStorage
Persistent storage services for workloads that need managed data placement.
Ganesha NFS provisioner storage service for persistent data workflows in Kubernetes-based environments.
Source repository
wodby/service-nfs-provisionerNetworking
Private networking services for secure connectivity between systems.
Private networking service for connecting apps, services, and operators over a secure tailnet.
Source repository
wodby/service-tailscaleStart from the closest building blocks in the catalog, compose a custom stack, or bring in your own service definition.
FAQ
A service is a building block inside a stack. Stacks are what you use to deploy apps, and services are the reusable parts inside those stacks, such as runtimes, proxies, databases, search, mail, and networking.
Yes. You can compose a custom stack from services, or start from a predefined stack and customize the services it contains.
When a service gets updated, stacks that use it can be marked as outdated. Upgrading the stack creates a new stack revision, and apps can move to that revision selectively or through auto-update settings.
Yes. Wodby supports service templates, so you can create your own service and manage it alongside the rest of your stack.
Yes. With the exception of special external services such as Cloud PostgreSQL and similar connectors, Wodby services are based on public Helm charts and Docker images.