- Response time by severity
- A commitment to respond to an incident within a stated time that depends on how severe the incident is, such as P1 for a site down and P3 for a cosmetic defect. Two agencies on this site publish one for Magento support; a single first-response time with no severity split, such as the 24 hours scandiweb publishes, is not one.
- Resolution target
- A commitment to fix, rather than respond to, an incident within a stated time. Written separately from the response time. No agency on this site publishes one.
- Patch application deadline
- A stated number of days from Adobe's release of a security patch to its deployment in production. Rocket Web publishes five days; no other agency on this site publishes a number.
- Security patch release (-p release)
- Adobe's name for a release that contains security fixes only, appended with -pN where N counts up from 1, for example 2.4.7-p10. Cumulative within its line.
- Isolated security patch
- Adobe's name for a non-cumulative, standalone patch file that fixes one or more security issues, released independently between full patches and folded into the next one. Adobe states a store must be on the latest -p release of its line to apply one.
- Hotfix
- Adobe's name for a fix to a critical issue such as a zero-day vulnerability, which its lifecycle page says it provides to all customers on a supported version even if they are not on the latest patch.
- Standard support
- Adobe's three-year support period from a version's release, which its lifecycle page says includes quality fixes, security patches and full Adobe support.
- Extended support
- Adobe's additional year after standard support, which its lifecycle page says includes quality and security patches for the core application at no additional cost.
- Security-only transitional period
- A one-time period Adobe publishes for 2.4.4, 2.4.5 and 2.4.6 only, after extended support, providing limited isolated security fixes and no quality fixes. Adobe states it will not be extended and should be treated as migration time.
- Version runway
- The time left before a store's Magento version leaves the support window it is in. A store on 2.4.6 has runway to 31 August 2027 for quality fixes; a store on 2.4.4 has none.
- Cloud upgrade enforcement
- Adobe's stated policy that from 1 June 2027 it will no longer maintain Adobe Commerce on Cloud environments running unsupported versions, with the storefront going offline; Cloud deadlines are 1 June 2027 for 2.4.4 and 2.4.5 and 1 June 2028 for 2.4.6 and 2.4.7.
- Regression testing
- Running a suite of tests against a store after a patch or change to catch what the patch broke. Rocket Web publishes automated full-regression testing on its $3,500 plan; no other agency on this site publishes a regression commitment.
- Monitoring
- Software that watches uptime, errors and performance and raises an alert. Distinct from human response; a plan can publish 24/7 monitoring and business-hours response, as Rocket Web's does.
- Exit terms
- The contract length, notice period, handover deliverables and ownership of automation that apply when a retainer ends. JetRails publishes hourly billing with no lengthy contracts; no agency on this site publishes a notice period or a handover list.
- Handover
- What an outgoing provider returns, meaning repository access, hosting and third-party credentials, environment variables, documentation of every custom patch, and the CI/CD configuration.
- Ownership boundary
- The written allocation of root access, firewall and CDN configuration, and the deploy pipeline between a host and an application agency. Most incidents on a mature store land on this boundary.
- Hyvä
- A frontend theme for Magento (Adobe Commerce). The hyva.io partner directory lists agencies at Platinum, Gold and Silver tiers; this site uses that listing as its third-party partner criterion.
- Stated by the agency
- The ledger status for a fact whose only source is the agency's own page. It is linked, it is attributed in the sentence, and no third party confirms it.
- Verified
- The ledger status for a fact the author read on a third-party page, such as hyva.io, Clutch or Adobe's documentation, on the date shown.