Database model
Database service
Database service
PostGIS database
PostGIS self-hosted database service for running database workloads inside a Wodby stack.
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.
Why teams use this database
Technical profile
Review versions, runtime packaging, ports, and source.
Backups and data import
Keep recovery points ready and move realistic data between environments.
Deploy it on Wodby infrastructure
Run the database on Wodby Cloud, managed Kubernetes, or K3S.
Stacks that use it
See where this database already fits in public stacks.
Connectivity and runtime defaults
See ports, links, storage, configs, and operational hooks.
Overview
Technical profile and runtime packaging
Review how PostGIS is packaged as a Wodby database service, what it exposes at runtime, and which public artifacts it builds on.
Versions
18
Built on top
Source repository
Public Helm chart
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.
Backup storage providers
Deployment
Run the database wherever the stack runs
Container-based databases can run on Wodby Cloud, managed Kubernetes, or K3S without changing how the database fits inside the stack. Connect your own managed Kubernetes account when you want provider control, or use the more managed Wodby options when you do not.
Wodby Cloud
Use the most managed hosting option when you do not want the cluster in your own account.
Managed Kubernetes
Run the database inside a cluster in your own cloud account while keeping the same Wodby workflow.
K3S on your own server
Use a leaner Kubernetes-based setup on a VM or dedicated server when cost or ownership matters more.
Stacks
Use it inside ready-made stacks or your own
These public stacks already use 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
1 config can be versioned with the service.