DeploxaDeploxa/Docs
Back to site
  • Members & Roles
  • Team Variables & Spend
  • SSO (SAML)
  • Audit, Repos & More
  • Infrastructure
  • Billing & Plans
  • Account & Tokens

Workspace & Account

Infrastructure

Choose where your builds and functions run. Deploxa abstracts compute, storage, secrets, and serverless behind one interface, with a migration engine to move between providers.

Provider configuration

In the dashboardWorkspace → Settings → Infrastructure

Configure the provider used for your organization's deployments. Each capability — storage, compute, serverless, secrets — is pluggable, so you can run on Deploxa's managed infrastructure or bring your own cloud account.

CapabilityProviders
StorageAWS S3, GCP GCS, Azure Blob
Compute (builds)AWS ECS Fargate, GCP Cloud Run Jobs, Azure ACI, Kubernetes, Docker
ServerlessAWS Lambda, GCP Cloud Run, Azure Container Apps
SecretsAWS Secrets Manager, GCP Secret Manager, Azure Key Vault, HashiCorp Vault

Bring your own cloud

Provide credentials for your own cloud account and Deploxa will run builds and host functions there, so the infrastructure (and its bill) stays in your account while you keep the Deploxa workflow.

Migration engine

Switch providers without starting over — the migration engine copies storage across providers and redeploys functions on the new target, with rollback if something goes wrong.

Provider maturity

The AWS path is the fully exercised, production-tested implementation. The GCP, Azure, and Kubernetes adapters are reference implementations of the same interface and haven't been validated end-to-end — treat them as a starting point, not turnkey production targets.
Audit, Repos & MoreBilling & Plans