Reusable building blocks for app stacks

Services that make up your stack

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

Why teams work from services instead of reinventing every stack

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.

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.

Use versioned services with managed updates

All services are versioned, and Wodby manages their updates so stacks can move to newer revisions in a controlled way.

Build on public charts and images

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.

Create your own services

You can create a custom service from a template and maintain it in the delivery workflow your team already uses.

Service catalog

Browse services by category

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

App services

Application runtimes and primary workload services used inside stacks.

Databases

Databases

Relational database services and cloud database connection services.

Datastores & caches

Datastores & caches

Stateful services used for caching, queues, sessions, and related workloads.

Storage

Storage

Persistent storage services for workloads that need managed data placement.

Networking

Networking

Private networking services for secure connectivity between systems.

Need a different service?

Start from the closest building blocks in the catalog, compose a custom stack, or bring in your own service definition.

FAQ

Common questions about Wodby services

What is a service on Wodby?

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.

Can I build my own stack from services?

Yes. You can compose a custom stack from services, or start from a predefined stack and customize the services it contains.

How do service updates affect stacks and apps?

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.

Can I create my own service?

Yes. Wodby supports service templates, so you can create your own service and manage it alongside the rest of your stack.

Are Wodby services based on public artifacts?

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.