When was Edgescan founded compared with Global App Testing?

Edgescan was founded in 2011, according to the company's own site, checked 2 September 2026. Global App Testing was founded in 2013, according to its own site, checked 2 September 2026. Neither date indicates when either company began offering its current mix of services, since a founding year marks when the company was established, not when a specific service line launched.

Which countries does each company list as a delivery location for testing engagements?

Edgescan lists Ireland and the USA as delivery locations, according to the company's own site, checked 2 September 2026. Global App Testing lists the UK and Romania as delivery locations, according to its own site, checked 2 September 2026. A delivery location on either list names a country the company can staff work from; it does not record which specific site handles a given engagement or what language coverage that site provides.

Edgescan vs Global App Testing

QA Rating is published independently, and its publisher owns no company listed in this catalog.

Edgescan meets the conditions for Security focus; Global App Testing meets the conditions for Crowdtesting at scale. The catalog has Signs a BAA / GDPR DPA only for Edgescan, and Client stages, Minimum project, Crowd tester pool only for Global App Testing. Neither publishes Frameworks, Published rates, Onboarding, Device lab, so the table cannot answer those.

Field by field

Edgescan and Global App Testing compared on the fields published for every company in this catalog
Field	Edgescan	Global App Testing
Headquarters	Dublin, Ireland	London, the UK
Delivery locations	Ireland, the USA	the UK, Romania
Team size	51-200 people	51-200 people
Founded	2011	2013
Ownership	Independent	Independent
Services	Penetration testing, Security testing, Attack surface management	Manual testing, Usability testing, Accessibility testing, Payment flow testing, Localization testing, AI system testing
Industries	Banking, Healthcare, Ecommerce, Telecom	Telecom, Games, Fintech, Ecommerce, Media, Travel
Frameworks	Not published	Not published
Engagement models	Continuous testing program, On-demand testing	Crowdtesting, Project work, Continuous testing program
Client stagespublished by one of the two	Not published	Enterprises, Scaleups
Certificates	ISO/IEC 27001register entryCRESTregister entry	ISO/IEC 27001register entry
Signs a BAA / GDPR DPA	Not confirmed / Yes	Not confirmed / Not confirmed
Published rates	Not published	Not published
Minimum projectpublished by one of the two	Not published	$10,000globalapptesting.com
Onboarding	Not published	Not published
Crowd tester poolpublished by one of the two	Not published	145,035globalapptesting.com
Device lab	Not published	Not published

Who each one fits

Edgescan fits a buyer whose need centers on assessing where a network or application could be broken into: an outside security review focused on a defined attack surface. Global App Testing fits a buyer whose need centers on running many customer-facing checks in parallel, across markets and release cycles, through a distributed workforce sized to a launch calendar.

A published price is missing from each profile, and on this pair that gap is sharper than it usually is, because the work here is not priced on a shared unit. An assessment is scoped against a boundary and quoted against that boundary. Testing spread across a distributed workforce is quoted against volume: how many cycles, how many markets, how often. A buyer holding a proposal from each side is comparing units before ever comparing prices.

Ask each side what its figure is measured against and what makes the figure move, then get that measure written into the scope rather than into a covering email. The published field to weigh the answer against is team size, because a quote that assumes a larger bench than the profile records is a quote that depends on hiring.

A tag is attached when the company's published fields meet its condition, never by judgement. Both lists come from the same closed vocabulary, so a tag missing from one side means the condition was not met, not that nobody looked.

Edgescan

Security focus

Global App Testing

Crowdtesting at scale

Both meet the conditions for Nearshore for the EU, so those conditions do not separate them.

Where the data runs out

Completeness against the 14 fields of the comparison checklist is 71% for Edgescan and 79% for Global App Testing. A field is counted as filled when a source confirms it, so a gap means nobody published it.

Neither company has a value recorded for these fields: Frameworks, Published rates, Onboarding, Device lab. The table shows those rows empty rather than estimating them.

Field definitions and the completeness checklist are on the methodology page. The sources behind each field are listed on the Edgescan profile and the Global App Testing profile.

Questions

When was Edgescan founded compared with Global App Testing?: Edgescan was founded in 2011, according to the company's own site, checked 2 September 2026. Global App Testing was founded in 2013, according to its own site, checked 2 September 2026. Neither date indicates when either company began offering its current mix of services, since a founding year marks when the company was established, not when a specific service line launched.
Which countries does each company list as a delivery location for testing engagements?: Edgescan lists Ireland and the USA as delivery locations, according to the company's own site, checked 2 September 2026. Global App Testing lists the UK and Romania as delivery locations, according to its own site, checked 2 September 2026. A delivery location on either list names a country the company can staff work from; it does not record which specific site handles a given engagement or what language coverage that site provides.

Published by QA RatingUpdated on September 6, 2026

Every fact about a company comes from a listed source. A field without a source stays empty. A certificate counts as confirmed only when a registry, certificate or auditor report backs it; a certificate the company only claims about itself is published separately, under that label. Vendors can request a correction at hello@qa-rating.com. A correction is applied when it comes with a public source.