CSI-NEXTDeployment configuration
Platform:
One product, your platform

Where should we deploy CSI-NEXT?

The same product runs on any of these - one config drives them all. Pick where this deployment lands and we'll tailor the questions to it. You can change it at any time.

Same engine, same adapters, same operator portal on every platform - only the substrate that builds the resources differs. Sources and analytical stores are chosen independently of platform.

Before you fill this in

An account on its own is not enough to deploy into - somebody has to be able to apply the templates we send you. Worth confirming with whoever owns the account, because these are the things that stop a deployment on the day rather than at review:

Configure your deployment

Every deployment is one self-contained stack, shaped entirely by the answers below. Work top to bottom - later questions appear only when they apply. When you're done, download the completed questionnaire and send it back; we generate and synthesize your environment from it.

No credentials here. This form collects connection details only - account ids, endpoints, volumes, choices. They are the non-sensitive half: what a system is and where it lives. Every password, secret and key is entered later, and only ever, through Ground Control after deploy (sealed to the worker tier). If a question here would need one, it is the wrong question and we would like to know.

And if some of this is confidential, you can withhold it.
Nothing you enter here leaves your device. This page has nowhere to send it: there is no server behind it, no form submission, no analytics, and no request of any kind to CSI or anyone else - the page is a single file that runs entirely in your browser. Your answers stay in this tab, the download is written locally, and the copy button uses your clipboard. Close the tab and they are gone. The only thing that ever reaches us is the file you choose to send us yourself.