What we do
Tools
Industries
Department
How we workLet's talk →
Home/Adobe Commerce
Adobe Commerce on cloud infrastructure

Adobe Commerce Cloud After Launch: Environments, Deploys and Extensions

The partner who built the store has handed over the Git repository and a Cloud Console login. Now a pricing rule or an ERP feed has to go live without anyone touching checkout. Adobe Commerce on cloud infrastructure is Adobe-hosted Magento with house rules: environments you can't edit in place, a fixed path from integration to production, and some changes that only Adobe makes. Those rules decide how every integration on the store gets built.

Where Adobe Commerce stops

B2B tools are included, but connecting orders and customers to the ERP and CRM is custom work outside the storefront build.

Stuck on Adobe Commerce? Let's solve it →

Starter and Pro on Adobe Commerce Cloud

Starter

Containers all the way up

  • Up to four environments: master runs production, plus staging and up to two integration environments.
  • Staging branches from master, and integration environments branch from staging.
  • Every environment runs as containers on shared infrastructure. Fastly is on production and staging, not integration.
Pro

Dedicated hardware for staging and production

  • Integration runs on containers with up to two active branches. Staging and production run on dedicated hardware.
  • Production is a three-node cluster behind a load balancer, with Fastly, New Relic and three gateway servers on static IP addresses.
  • Service changes on staging and production go through an Adobe support ticket, with at least two business days' notice for production.

On Pro, any feature that needs a new or upgraded service, such as a different search or queue version, has to fit around that ticket lead time.

How a change reaches the live Adobe Commerce store

The path on Pro. Starter follows the same idea with its own branch names.

  1. 1

    Build it locally

    Remote environments are read-only. Modules, Composer changes and configuration files are written and tested on a developer's machine, then committed to Git.

  2. 2

    Push to an integration branch

    Pushing triggers the build phase, which runs composer install automatically. ece-tools, the package that ships in every cloud project, drives the build and deploy steps.

    Watch for: integration has no Fastly and no New Relic, so caching behavior and performance can't be judged here.

  3. 3

    Move it to staging

    Staging is near-production, with Fastly, backups and cron. This is where a test order should run end to end through any ERP or CRM feed, and where scheduled jobs get their first real run.

  4. 4

    Promote to production

    Code goes from staging to production. You can't branch from either one. Settings in .magento.env.yaml control the build, deploy and post-deploy stages.

    Watch for: a change to .magento/services.yaml alone won't reach Pro staging or production. Adobe applies service changes there after a support ticket.

What an integration on Adobe Commerce Cloud has to settle

  • Does the system on the other side need to allowlist the store?

    Pro production comes with three gateway servers on static IP addresses, which is usually what a partner firewall allowlists. Confirm the addresses for your project with Adobe before the ERP team asks.

  • Should the code live inside Commerce or beside it?

    An in-process PHP module is deployed with the store and retested on every upgrade. An App Builder app runs outside the store, reacts to Adobe I/O Events, and keeps a slow ERP from holding up checkout. Adobe I/O Events needs Adobe Commerce 2.4.4 or later.

  • Do several back-office APIs need to appear as one?

    API Mesh for App Builder combines several APIs, such as Commerce, an ERP and a PIM, behind one GraphQL endpoint, which suits a headless storefront or a staff app.

  • Who runs the queue consumers?

    Bulk imports and async operations wait in the message queue until a consumer processes them. On cloud, the CRON_CONSUMERS_RUNNER setting in .magento.env.yaml decides which consumers cron starts.

  • Will the storefront show what the integration changed?

    Prices and stock written through Commerce's own APIs trigger its reindexing and cache cleanup. Writes made straight to the database skip that, so customers behind Fastly can keep seeing old values.

  • Is a move to Adobe Commerce as a Cloud Service coming?

    Adobe's SaaS edition allows extensions out of process only, through APIs, events and App Builder. Building new integrations that way now means they don't need rewriting later.

Contractor accounts a rep can read before dialing

Building products distributor: Adobe Commerce for contractors, Salesforce for reps

Before

Reps called contractors without knowing they'd placed a large order that morning or had an unpaid balance.

That made for awkward calls, and the store's B2B data never left the storefront admin.

After

Company accounts, pricing and recent orders from Adobe Commerce now show up in Salesforce.

Reps start each call already knowing where the account stands.

Let's talk

Adobe Commerce integrations that pass staging before they go live

n-frames builds the ERP, CRM and multi-site order integrations for stores on Adobe Commerce Cloud, either as modules that follow your integration and staging branches or as App Builder apps that sit outside the store. Your implementation partner keeps the storefront, theme and checkout.

Run the ERP feed through staging →

Questions people ask

What is Adobe Commerce Cloud?

Usually it means Adobe Commerce on cloud infrastructure: Adobe hosts the platform on Pro or Starter plans, with Fastly, Git-based deploys and managed services, while the merchant still owns the application code and upgrades. Adobe now also sells Adobe Commerce as a Cloud Service, a SaaS edition where Adobe runs and updates the core and extensions sit outside it. And some people searching mean Salesforce Commerce Cloud, a different company's product that happens to share the words.

What is Adobe Commerce?

It's Adobe's licensed e-commerce platform, built on the Magento codebase, with B2B tools, merchandising features and Adobe support added. It's sold and usually implemented through Adobe's certified partners.

Is Adobe Commerce the same thing as Magento?

They share a core. Magento Open Source is free and self-hosted. Adobe Commerce is the paid edition, sold as Magento Commerce until Adobe rebranded it after buying Magento in 2018. Different pricing, different support, mostly the same APIs.

How much does Adobe Commerce cost?

Adobe doesn't publish a price. Quotes depend on business size, order volume, features and hosting option, and are usually arranged through an Adobe Solution Partner rather than a self-serve checkout.

Do I need an Adobe Commerce partner or agency?

For building and launching the storefront, yes, that's what Adobe's Solution Partners do. n-frames isn't one of them. Our work starts on a live store: the integrations with the ERP, CRM and other systems the business runs, built to deploy through the same cloud environments.

Does Adobe Commerce have its own marketplace?

Yes, the Adobe Commerce Marketplace, shared with Magento, with extensions for payments, shipping, marketing and common ERP connections. A particular ERP, a custom pricing rule or an in-house system usually needs a custom integration instead.

Can we deploy straight to production on Adobe Commerce Cloud?

Not on Pro: code goes from integration to staging to production, and you can't branch from staging or production. On Starter, production runs from master. Either way, every environment is read-only, so changes arrive through Git rather than edits on the server.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.