FAQs

MDOQ is both a hosting service and a suite of tools to help you manage Magento Open Source and Adobe Commerce more effectively.

We're here to provide the support you need. Our team is made up of Magento experts with years of experience meaning you know you'll receive the best support possible.

Data sanitisation and user policies are just a couple of the tools available to help you.

MDOQ has a managed deployment pipeline which supports Zero Downtime and Downtime deployments from your development to production infrastructure

By using MDOQ you have a full CI/CD pipeline that enables you to both package up work in to deployments (create builds) and deploy them to production. You do not need any other tools. However if you do want to implement custom steps/actions into your builds MDOQ supports custom build steps for packaging your site, as well as a full Rest API you can use to integrate MDOQ with your systems as mush as you wish.

Yes! When creating an instance you are asked for a "ticket number" this ticket number the name of the branch. If the branch doesn't exist MDOQ will create it as part of the instance creation, if the branch does exist then MDOQ will use the existing branch.

Yes! We have a dedicated documentation site docs.mdoq.io

MDOQ works on a subscription model, you subscribe to reserve a set amount of concurrent instances. You will not be able to exceed your allotted instances, so there are no surprise charges. If you require more instances we would recommended increasing your subscription package.

An instance is a replication of your website, for development, testing or general investigation.

A full backup is a full copy of your production database including customers and orders. A sanitised backup omits all customer/sales information so that instances can be fully protected from risk in a real-world environment. Within MDOQ you can do both. You can even specify "Use sanitized backups for instances" so that development instances don't contain sensitive information.