Skip to main content
Connect accounts and infrastructure you control to a Spitzli Cloud workspace. Your provider continues to bill you directly and apply its own quotas. The connection’s permissions determine what Spitzli Cloud can inspect or manage.

Neon

Connect an API key and view authorized Neon projects.

turboSMTP

Connect your sending account and create separate Mail API keys.

Vercel

Authorize a team and select projects where the integration is activated.

Kubernetes and k3s

Enroll an approved existing cluster and manage permitted workloads.

​
Choose an available connection

Neon uses the workspace’s Connections page and requires an owner, administrator or authorized operator. It currently provides key management and read-only project inventory. Turbo, Vercel and cluster flows depend on separate operator enablement and provider configuration. A documented integration is not a promise that it is activated for every workspace. Ask your operator to confirm the available flow if its controls are missing. Workspace membership does not grant provider access by itself. Provider grants, service permissions, current role and resource scope are checked for each action. Read-only customer preview cannot change connections.

​
Keep ownership and billing clear

Connecting an account does not deploy an application, transfer ownership or allocate a platform free quota. Review provider charges, available capacity and workload regions separately. Disconnecting generally removes Spitzli Cloud’s access without deleting provider resources. Follow the provider-specific guide for retained history and credentials, and revoke keys or installations at the provider when access must end there too. For supported cluster, Vercel and Mail automation, see BYOK automation. Neon Connections uses its own Console workflow.