Adobe App Builder for Adobe Commerce
Extend your store with custom integrations and automations that run on Adobe's own infrastructure, not inside your Commerce codebase.
What is Adobe App Builder?
Adobe App Builder is Adobe's own framework for building and deploying custom applications that extend Adobe Experience Cloud solutions, including Adobe Commerce. Apps run on Adobe I/O Runtime, Adobe's serverless computing platform, rather than inside your store, and connect back to Commerce through Adobe's APIs and events.
Who App Builder is built for, and who should skip it
Adobe positions App Builder for:
Adobe enterprise customers and the partners who build for them
Businesses that already hold, or can license, an Adobe Experience Cloud product — App Builder isn't sold on its own outside that ecosystem
Adobe Commerce customers specifically, who get App Builder capacity included at no extra cost when running Adobe Commerce on Adobe's cloud infrastructure
Where we'd tell you to wait.
If you only need a one-off data export or a single lightweight script, and you're not already inside the Adobe Experience Cloud ecosystem, a smaller integration may cost less to build and run than standing up an App Builder project and licensing a Pack for it. We'd rather say that on the first call.
How Adobe App Builder works, in plain terms
Four pieces work together, per Adobe's own architecture description:
01
Single-page applications, built with React Spectrum, the same interface toolkit Adobe uses for its own products.
02
Adobe I/O Runtime, the serverless platform that runs your backend logic on demand, in response to HTTP requests or Adobe I/O Events.
03
Developer tooling: the CLI, SDKs, and the Adobe Developer Console, covering authentication, access control, event publishing, and storage.
04
The Adobe Experience Cloud environment itself, so your app runs in the context of your organization's authenticated users, alongside Commerce.
Where you already have App Builder access
| Your situation | What's included | What we build |
|---|---|---|
| Adobe Commerce on Adobe's cloud infrastructure | App Builder capacity included at no extra cost | Integrations built directly, no new license needed |
| Adobe Commerce self-hosted | App Builder available as a purchasable add-on | We help you license and provision it, then build |
| Adobe Experience Manager Sites Cloud Service | 1 Pack of App Builder included | The same platform, reused for Commerce-facing apps if you run both |
| No Adobe Experience Cloud product yet | Not eligible for App Builder on its own | We scope which Adobe product unlocks it, or recommend a non-App-Builder integration instead |
What Evrig does on an App Builder project
Access check.
We confirm what your organization already has through the Adobe Developer Console before proposing anything new.
Architecture and scoping.
Actions, triggers, events, retries, error handling, and the access control App Builder already provides.
Build and test in a sandbox.
Adobe App Builder supports developer sandboxes and staging workspaces, so nothing touches production Commerce untested.
Deployment.
Through the Adobe Developer Console and CLI, on the release model Adobe documents.
Monitoring and support.
Watching logs, activations, and events after go-live.
Proven in Practice: Multi-Brand Professional Beauty Commerce
Client: A professional hair care company operating several brand storefronts on a single Adobe Commerce instance.
Challenge: Orders, inventory, pricing, shipments, refunds, and customer accounts had to stay consistent between Adobe Commerce and NetSuite across multiple brands and a national retail partner, without anyone re-keying data.
Solution: Evrig built, and continues to maintain, an App Builder application made up of more than 15 serverless actions and 11 scheduled automations, running on Adobe I/O Runtime. These run every 10 to 30 minutes, hourly, or overnight, and cover the entire journey from order to refund.
Results:
- Orders, inventory, prices, shipments, and credit memos sync with no manual steps
- Staging and production workspaces are kept separate, with ticket-based, controlled releases
- New brands and retail channels are added without touching core Commerce code
- Automatic failure alerts let the team fix issues before customers notice
Also built: Evrig has shipped App Builder integrations connecting Adobe Commerce to HubSpot and MuleSoft, alongside the NetSuite work above.
What we check before building
These come straight from Adobe's own system settings for Adobe I/O Runtime, the platform App Builder runs on:
01
Blocking (web) actions time out at 60 seconds — a hard limit.
A synchronous call that might run long needs to be invoked asynchronously instead, or split into a sequence.
02
Non-blocking actions can run up to 3 hours,
but the caller gets an activation ID, not an immediate response — the calling system needs to poll for the result or receive a callback.
03
Memory per action is configurable from 128MB to 4096MB, default 256MB.
Undersizing this is a common cause of failed large-catalog jobs.
04
A namespace is capped at 100 concurrently queued activations by default.
Anything invoking faster than that gets a 429 and needs to back off and retry — worth planning for on a busy sale day.
05
Deployed action code, including dependencies, is capped at 22MB.
06
Activation logs and results are kept for 7 days.
Build your own audit log if you need a longer record than that.
What drives the cost of an App Builder project
- Which systems you're connecting, and how many endpoints each one exposes
- Whether you already hold App Builder access through Adobe Commerce or another Adobe product, or need to license a Pack first
- Event-driven vs. scheduled: reacting to Adobe I/O Events in real time takes more design work than a nightly, cron-style sync
- How much of the integration needs a user interface versus running entirely as background actions
- Ongoing monitoring and support once the app is live
Common concerns
"Doesn't this mean paying Adobe twice?"
Not if you're running Adobe Commerce on Adobe's cloud — App Builder capacity is already included, so you're not licensing it separately.
FAQ
Connect ExpertFind out if App Builder is the right fit before you license a Pack
Send us the systems you want to connect and what Adobe products you're already running. We'll tell you whether App Builder is the right tool, and what building it would involve.