Roadmap

Future feature planning, new feature release schedule, and todo list.

Release Strategy

Pigsty uses semantic versioning: <major>.<minor>.<patch>. Alpha/Beta/RC versions will have suffixes like -a1, -b1, -c1 appended to the version number.

Major version updates signify incompatible foundational changes and major new features; minor version updates typically indicate regular feature updates and small API changes; patch version updates mean bug fixes and package version updates.

Pigsty plans to release one major version update per year. Minor version updates usually follow PostgreSQL’s minor version update rhythm, catching up within a month at the latest after a new PostgreSQL version is released. Pigsty typically plans 4-6 minor versions per year. For complete release history, please refer to Release Notes.


Features Under Consideration

  • A sufficiently good command-line management tool
  • ARM architecture support for infrastructure components
  • Add more extensions for PostgreSQL
  • More preset scenario-based configuration templates
  • Fully migrate software repository and installation download sources to Cloudflare
  • Deploy and monitor highly available Kubernetes clusters using SealOS!
  • Use VictoriaMetrics to replace Prometheus for time-series data storage
  • Monitor and deploy MySQL databases
  • Monitor databases in Kubernetes
  • Provide richer Docker application templates
  • PGLite browser-side support

Here are our Active Issues and Roadmap.


Extensions and Packages

For the extension support roadmap, you can find it here: https://pgext.cloud/e/roadmap

Under Consideration

Not Considering for Now


Last Modified 2026-01-09: add supabase asciinema demo (693cfa8)