Deployment Options
Fit your data platform into your environment.
Keep infrastructure choices explicit. Agree where the application runs, where the data lives and who operates it, then validate the complete setup with your team.
Separate the choices that matter.
A cloud database and a cloud-hosted application are different choices. An on-premises setup still needs defined network routes and operational ownership.
Application host
Choose the package and service environment appropriate to the product.
Data destination
Use the database supported by that product and deployment.
Network and identity
Plan HTTPS domains, Salesforce connections, service accounts and user access.
Choose a product-specific deployment.
Archive: the main Windows distribution uses SQL Server; Snowflake is a separate distribution. Backup: SQL Server and PostgreSQL paths have distinct packaging and validation. Own migration: export import has its own adapters and executable. Support in one product does not imply support in the others.
Prepare a setup your team can operate.
Bring the application owner and DBA into the design early. Agree capacity, permissions, DNS, certificate ownership, destination backups and support. Test installation, upgrade, user access and recovery against the exact delivered build.
Questions, answered.
Can we use our own cloud infrastructure?
Yes, customer-controlled infrastructure is part of the deployment approach. The host, database, network and selected product still need a supported, validated combination.
Is every database or operating system supported?
No. Additional adapters and packaging work have different readiness levels. We confirm the current support matrix for the product you are evaluating.
Planning an evaluation
Agree the scope before you start.
Production delivery requires an approved package and matching acceptance evidence. Linux/container recipes, preview adapters and a passing database test alone do not establish a supported production deployment.
Review your deployment