Database service
Databases/PostgreSQL (PostGIS)

PostgreSQL (PostGIS) database

Self-hosted PostgreSQL database service with PostGIS extensions for applications that need geospatial data and spatial queries inside the same delivery workflow.

Run this database inside the stack when you want self-hosted data close to the application workflow, with backups, imports, and environment reuse managed through the same Wodby platform.

Good to know

Running PostGIS on Wodby

On Wodby, PostGIS runs as a PostgreSQL server with the PostGIS extensions bundled, as a single service with its data on a volume. Databases, users, backups, and imports work as they do for PostgreSQL.

No extension step in your migrations

The PostGIS extensions are created in a database at the moment Wodby creates the database. Your application and its migrations never have to run the create extension statement.

Check the installed version

To see which PostGIS and library versions a database has, open a web terminal for the service and query the full PostGIS version.

Reach it like PostgreSQL

The server listens on the standard PostgreSQL port and has no public route. Services in the same environment use the service name as the host, and access from outside the cluster needs the port published.

Dumps without roles or grants

A backup is a compressed SQL dump of the environment's database that carries neither role names nor grants. It can therefore be imported into a database with a different name and different users.

Read the PostGIS guide for setup steps, settings, and limits.

Overview

Technical profile and runtime packaging

Review how PostgreSQL (PostGIS) is packaged as a Wodby database service, what it exposes at runtime, and which public artifacts it builds on.

Database model

Database service

Versions

18, 17

Ports and protocols

5432/TCP

Data workflows

Back up data, import realistic copies, and keep access manageable

Container-based database services keep the database inside the same stack workflow as the application, so teams can manage recovery points, refresh other environments with working data, and control database access through Wodby.

Automatic backups with cloud storage uploads

Keep recent recovery points ready and send database archives to connected cloud storage providers.

Import working data into other environments

Refresh staging, create realistic QA environments, and onboard developers faster with data import workflows.

Manage databases, users, and access centrally

Handle database users and which databases they can access through the same Wodby workflow instead of ad hoc manual steps.

Deployment

Run the database wherever the stack runs

Container-based databases can run on Wodby Cloud, managed Kubernetes, or self-hosted Kubernetes without changing how the database fits inside the stack. Wodby maintains the cluster on all three, so choose by where the data should live and what it should cost.
Wodby Cloud

Wodby hosts the cluster, so there is no cloud account or server to set up first.

Managed Kubernetes

Run the database in a cluster in your own cloud account, created and kept up to date by Wodby.

Self-hosted Kubernetes

Use your own VMs or dedicated servers when budget matters more than autoscaling. Wodby checks their packages for vulnerabilities and installs updates when you choose.

Managed alternatives

Keep the same database family while moving the server outside the stack

When you want a provider-managed database server instead of running the database inside the stack, these related connection services keep the app-side database model inside Wodby.

Stacks

Use it inside ready-made stacks or your own

These public stacks already use PostgreSQL (PostGIS) in their database layer. Start from one of them, or build a custom stack around the same database service model.

Connectivity

Reuse connectivity, storage, and operational defaults

Database services can expose ports, connect to application services, attach persistent storage, and define runtime defaults that stay reusable inside stacks rather than being rebuilt by hand.

Endpoints

5432/TCP

Volumes

Data

Configs

2 configs can be versioned with the service.