Frequently asked questions
What environments can I deploy to?
Common options are development, staging, and production. You can configure as many environments as needed for your workflow. Learn more.
What can I do with the Deployment API?
Deploy code and pipeline changes to various environments
Automate release workflows (CI/CD)
Specify version, branch, environment, and deployment directory
Integrate Mage Pro with your existing DevOps pipelines
What information is needed to create a deployment?
To create a deployment using the API, you need:
Deployment setting name
Source branch and commit version
Target environment (dev, staging, prod)
Deployment directory (path)
OAuth authentication token and API key
What is the Mage Pro Deployment API?
The Mage Pro Deployment API enables you to programmatically create deployments in your Mage Pro environments, automating the release and update of your code and pipelines across development, staging, and production environments. Learn more.
Where is my data stored and can I choose a region?
By default, Mage Pro data is stored on secure AWS infrastructure located in the United States. Regional deployments are available in the US, Canada, Europe, Asia, and Australia for compliance and data residency. See available regions.
What regional deployments are supported?
Mage offers regional deployments in US West, US East, Canada, Europe, Asia, and Australia to ensure optimal performance and data residency compliance.
What deployment options does Mage Pro support?
Mage Pro supports multiple deployment options for your organization’s requirements:
SaaS (fully managed)
Hybrid cloud
Private cloud (VPC)
On-premises
This flexibility enables control over data residency, compliance, and security needs. Details.
Does Mage Pro provide support for migration and setup in these deployment types?
Yes, Mage Pro offers hands-on onboarding, migration assistance, and dedicated support tailored to your chosen deployment model, helping ensure a smooth transition and optimal setup.