Release Stages
VeloDB Cloud rolls out features in stages before they become generally available. Each stage carries different commitments for who can use the feature, whether it is meant for production, how stable its interfaces are, and what support it receives. The stages are:
Private Preview → Public Preview → GA
The following table defines each stage.
| Stage | Who can use it | For production | API stable | Support | Notes |
|---|---|---|---|---|---|
| Private Preview | By invitation; contact the VeloDB support team to enable it for your account | No | No | Engineering team, best-effort, lowest priority | Off by default. The earliest stage, for a small set of seed customers validating core functionality. Interfaces can change and known defects may exist. Public documentation may be limited to a brief guide. |
| Public Preview | All customers. Self-serve in the console (Open, the default), or On Request for a few capacity-constrained features (contact the VeloDB support team) | Evaluate against your own scenario | Yes; no breaking changes when the feature reaches GA | Standard support, lower priority than GA | The last stage before GA, for at-scale validation. Full official documentation, with known limitations noted. A security review is completed before this stage, and data-plane features undergo penetration testing. |
| GA | All customers | Yes; production-ready | Yes | Standard support priority | On by default and fully supported. To reach GA, a feature passes availability, disaster-recovery, and monitoring-readiness reviews, with billing and quotas finalized. |
Open vs. On Request
VeloDB separates rollout control from the release stage. A Public Preview feature can start On Request to reach a small audience, then switch to Open for everyone as confidence grows, without changing its release stage. This is why two features both labeled Public Preview can differ: one requires a request, the other works out of the box. The common path is On Request, then Open, then GA.
Support and production readiness
Only GA features are production-ready and receive standard support priority. Preview features (Private Preview and Public Preview) are mainly for evaluation and testing, are handled at lower priority, and are not treated as production-incident response. When troubleshooting, VeloDB may ask you to disable a related preview feature first. Full support-response terms are defined in the VeloDB Cloud support policy.