Open platform
An open platform model that protects flexibility as your infrastructure changes
Run on open standards, inspect the building blocks, and keep the option to evolve or migrate without being trapped in proprietary platform behavior.
- Keep application stack configuration in Git
- Inspect publicly available stack components, images, and charts
- Connect external services instead of accepting a forced bundle
Keep application stack configuration in Git
Own the stack template and review changes through the same source-control workflow as application code.
Define a custom application stack in stack.yml, import it into Wodby, and keep the repository as its source of truth. Stack revisions make changes reviewable before environments adopt them, and Git-backed stacks can continue receiving allowed source updates.
Inspect the stack components, images, and charts you rely on
Transparency matters when teams want to understand what is actually running in production.
Wodby stacks are built from recognizable open-source components, and the related Docker images and Helm charts are publicly available. That gives teams more confidence in what is running, and it creates a practical path for customization or reuse outside the hosted platform when needed.
Browse the public stack definitions, service definitions, and Helm charts, or inspect the published images on Docker Hub.
Avoid platform lock-in when infrastructure strategy changes
Portability is easier when the platform uses open building blocks instead of hiding everything behind proprietary behavior.
An open foundation gives teams more room to move if they need to change providers, move workloads, or operate more infrastructure themselves. Wodby does not remove the value of managed workflows, but it keeps the underlying application definition closer to open, inspectable building blocks.
Why open standards matter for long-term platform decisions
Openness is useful because it improves more than one part of the delivery model.
Interoperability
It is easier to connect standard tooling and external services when the platform is not built around proprietary assumptions.
Longevity
Open technologies are less likely to disappear behind a single vendor roadmap change.
Community depth
Teams benefit from broader documentation, examples, and ecosystem support.
Operational flexibility
You can adapt how the platform runs as needs evolve instead of rewriting the delivery model.
Transparency
Understanding the platform internals is easier when the building blocks stay visible.
This openness complements application stacks and reusable integrations rather than competing with managed operations.
Next step
Choose a platform model that stays useful even when your requirements change
Open standards help teams keep optionality around hosting, operations, and platform evolution instead of locking every decision into one narrow path.