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.
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.
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 self-hosted Kubernetes.
Managed database alternatives
Keep the same database family while moving the server outside the stack.
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.
Good to know
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.
To see which PostGIS and library versions a database has, open a web terminal for the service and query the full PostGIS version.
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.
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
Database model
Versions
Built on top
Source repository
Public Helm chart
Ports and protocols
Data workflows
Keep recent recovery points ready and send database archives to connected cloud storage providers.
Refresh staging, create realistic QA environments, and onboard developers faster with data import workflows.
Handle database users and which databases they can access through the same Wodby workflow instead of ad hoc manual steps.
Deployment
Wodby hosts the cluster, so there is no cloud account or server to set up first.
Run the database in a cluster in your own cloud account, created and kept up to date by Wodby.
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
Stacks
Connectivity
Endpoints
Volumes
Configs