Database service
Services/PostGIS

PostGIS service

PostGIS service for reusable application and infrastructure workflows inside a Wodby stack.

Use it in stacks that need repeatable data workflows, scheduled backups, and realistic environment refreshes without rebuilding those steps manually.

Overview

Technical profile and packaging

This page shows how PostGIS is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

Database service

Versions

18

Ports and protocols

5432/TCP

Labels

postgis, postgres, postgresql, postgres, postgresql

Persistent volumes

Data

Stacks

Use it inside ready-made stacks or your own

These public stacks already include PostGIS as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Data workflows

Keep recovery points ready and move data between environments

PostGIS supports backup and import workflows, so teams can keep recovery points available, refresh staging, and create realistic working copies for testing or onboarding.

Attach backups to the service model

Keep scheduled backup behavior with the same versioned service definition instead of rebuilding it environment by environment.

Refresh staging and development with working data

Import archives into another environment when teams need realistic copies for testing, review, or onboarding.

Upload archives to cloud storage

Send backup archives to external storage providers instead of keeping them only inside the platform.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

5432/TCP

Volumes

Data

Configs

1 config can be versioned with the service.