Airwallex operates a global payments and treasury infrastructure, but its public web surface tells a story of two distinct technology layers: a developer-centric documentation portal built with Next.js, Contentful, and Cloudflare, and a parallel, ad-driven demand generation engine powered by Marketo, Demandbase, ZoomInfo, and a sprawling array of ad pixels. That duality is the defining characteristic of its tech stack. The company fronts its digital presence with extensive API references and integration guides, yet the commercial model is pure enterprise sales, with no self-serve conversion paths visible in our captured sample. This analysis breaks down the tools and architectural choices that make that model work, and what it signals for competitors and partners in the B2B fintech space.
The Stack at a Glance
Airwallex’s frontend and delivery stack is built around a statically generated, developer-first experience. The primary documentation site uses Next.js with Contentful as a headless CMS. This combination suggests a preference for pre-rendered pages with fast load times and minimal client-side complexity—ideal for serving global audiences through a CDN. The CDN in question is Cloudflare, which fronts a Google Cloud origin on IP address `34.102.197.111`. Meanwhile, DNS is managed by AWS Route 53 with DigiCert TLS certificates enforcing HTTPS. That’s a multi-cloud posture (Google Cloud for hosting, AWS for DNS) wrapped in a Cloudflare edge, a configuration common among enterprises that prioritize performance and DDoS protection but want to avoid vendor lock-in at the DNS layer.
Monitoring and security tooling is layered on top. Client-side error tracking runs on Sentry, which captures JavaScript exceptions from the Next.js frontend. reCAPTCHA protects forms from bot submissions, and Sardine—a fraud and compliance API—signals that Airwallex embeds identity and transaction risk scoring directly into its digital flows, likely on the backend or lead-generation forms. The documentation site itself includes Polyfills (likely via `core-js` or similar) to ensure broad browser compatibility, a pragmatic choice for a fintech company whose developer users might access docs from restricted enterprise environments.
The analytics and tag management layer reveals a mature measurement stack. Google Analytics (likely GA4) and Google Tag Manager serve as the baseline. On top of that, Microsoft Clarity and Crazy Egg provide session recording and heatmapping, indicating a focus on understanding user behavior within the documentation—perhaps to identify where developers drop off or where API explanations need improvement. The presence of Demandbase, Unify Intent, and ZoomInfo tracking scripts confirms an account-based marketing (ABM) approach. These tools deanonymize website visitors at the company level, feeding intent data into a Marketo marketing automation system for lead scoring and sales routing. This is not a stack optimized for self-serve conversion; it’s built to identify high-value accounts and hand them to a sales team.
The advertising pixel array is extensive: Meta, LinkedIn, TikTok, Bing, Reddit, Taboola, and Quantcast, plus unnamed programmatic partners. This broad coverage suggests a multi-channel paid acquisition strategy that runs retargeting campaigns across social, search, and native advertising. The combination of broad pixel coverage and ABM intent tools means Airwallex can serve highly targeted ads to decision-makers at companies already showing interest, then route those clicks into a Marketo-driven nurture sequence.
How They Acquire Customers
The tech stack reveals a go-to-market motion that is overwhelmingly sales-led, with a partner channel layered on top. The captured sitemap sample—truncated at 200 pages—contained 198 documentation pages and 2 sitemap index files. No pricing, demo, or signup pages were observed in that sample. However, a separate subdomain, `grw-landing.airwallex.com`, was detected via third-party calls, indicating that lead generation and conversion surfaces exist but are decoupled from the main documentation domain. That architecture is deliberate: the docs site serves as a top-of-funnel developer engagement tool, while actual buying conversations happen on sequestered subdomains that aren’t part of the primary sitemap we captured.
The ABM stack is the engine that converts that developer interest into pipeline. Demandbase provides firmographic enrichment and account identification. ZoomInfo offers contact-level data for sales prospecting. Unify Intent captures buying signals from third-party research sites, feeding them into the same system. When a visitor from a target account browses the API docs, these tools de-anonymize the session, attach it to a CRM record, and trigger a Marketo workflow. That workflow likely includes email nurturing, dynamic web content, and alerts for the sales team to reach out. It’s a classic large-deal B2B setup: lead velocity is lower than a self-serve funnel, but average contract value (ACV) is high enough to justify the hand-curated approach.
The partner channel is managed through PartnerStack, a platform specifically designed for B2B partner programs. This suggests Airwallex recruits and rewards integration partners, resellers, or referral sources who drive business to its platform. Combined with the ABM stack, the partner tool indicates a dual-pronged acquisition strategy: direct sales to large enterprises via intent data, and indirect sales through a curated partner network. The heavy ad pixel investment—spanning Meta, LinkedIn, TikTok, Bing, Reddit, Taboola, and programmatic channels—feeds both prongs by keeping the Airwallex brand top-of-mind among developers and financial decision-makers.
One notable gap: no A/B testing or experimentation tool was detected. Tools like Optimizely, VWO, or Google Optimize were absent from our scan. For a company with such an extensive analytics stack, the lack of a client-side testing framework is intriguing. It could mean that testing is done server-side, or that the marketing team relies on incrementality testing within the ad platforms themselves rather than on-site experiments. Given the complexity of a sales-led motion, the ROI of a homepage button-color test would be negligible compared to a well-targeted LinkedIn ad. Still, the absence of any experimentation tool suggests Airwallex optimizes its funnel through audience targeting and intent data rather than through rapid web conversion iterations.
Infrastructure & Operations
Airwallex’s infrastructure choices reflect a mature, security-conscious fintech that balances developer accessibility with operational rigor. The public-facing documentation site is fronted by Cloudflare, providing edge caching, DDoS protection, and Web Application Firewall (WAF) capabilities. Origin traffic routes to a Google Cloud IP within the `34.102.0.0/16` range, likely a load balancer or an instance running a Node.js server for the Next.js application. The DNS is separately managed on AWS Route 53, which offers reliable global resolution and supports advanced routing policies. This multi-provider setup prevents a single cloud provider from becoming a single point of failure at the DNS level, a smart choice for a payments infrastructure company where uptime is critical.
TLS termination uses DigiCert certificates, a premium Certificate Authority chosen over free options like Let’s Encrypt, likely for extended validation (EV) or organizational validation (OV) certificates that convey trust. For a fintech targeting enterprise treasurers and CFOs, that trust signal matters. The DNS configuration earned an ‘A’ grade from security scanners, with DMARC set to `reject`, BIMI published (enabling brand logos in email clients), and SPF set to `soft fail`. The `soft fail` on SPF is a minor concern: it instructs receivers to accept but mark emails that fail SPF checks, rather than outright rejecting them. While not a critical vulnerability, a `reject` policy would be stronger against spoofing. BIMI is a relatively advanced adoption, indicating that Airwallex’s security team is proactive about email authentication and brand protection.
On the backend, `bws.airwallex.com` was detected as a separate domain handling non-public operations. The naming convention suggests “Backend Web Services,” possibly an internal API gateway or admin console. Its separation from the main domain and documentation subdomains keeps operational attack surfaces isolated from the public content. Combined with reCAPTCHA on forms and Sardine for fraud detection, Airwallex demonstrates layered security: edge protection (Cloudflare), bot management (reCAPTCHA), fraud scoring (Sardine), and operational isolation (separate subdomain).
The content delivery architecture for the docs site leverages Next.js’s static generation capabilities. With Contentful as the CMS, content editors can update API references, guides, and changelogs, which then trigger a rebuild and CDN invalidation via Cloudflare. This headless CMS approach decouples content from presentation, allowing the engineering team to version documentation alongside code changes and publish updates without affecting the live site’s stability. Sentry monitors client-side errors, ensuring that any JavaScript regression that breaks the docs experience is caught and flagged quickly.
A public status.airwallex.com subdomain provides operational transparency. This status page—undoubtedly powered by a tool like Atlassian StatusPage or a similar service—offers real-time and historical uptime data for Airwallex’s APIs and services. For a payments company, this is a non-negotiable trust signal. Enterprise buyers evaluating Airwallex against competitors will check the status page before signing a contract, and its mere presence indicates a mature approach to incident communication.
What’s missing from the observable infrastructure is a dedicated trust center or compliance documentation page—at least, not one captured in our sample. Fintech companies frequently stand up a `/trust` or `/security` page detailing SOC 2 reports, PCI DSS compliance, data residency options, and penetration test summaries. The absence of such a page in the sitemap sample doesn’t mean it doesn’t exist; it may reside on a separate domain or be gated behind a login. However, the lack of an easily discoverable trust center is a notable gap for a company competing in the enterprise payments space, where security questionnaires are part of every procurement.
What This Means for Competitors
Airwallex’s tech stack reveals several strategic choices that competitors should scrutinize. First, the company has invested heavily in developer experience (DX) as a competitive moat. 198 documentation pages in a truncated sitemap sample suggest an extensive API reference, SDK guides, and integration tutorials. This is intentional: in the payments infrastructure market, the primary buyer or influencer is often an engineering leader. By saturating SEO keywords around API documentation and developer guides, Airwallex positions itself as the default choice when a developer searches for “cross-border payment API integration.” Competitors with thin or poorly optimized docs will lose that top-of-funnel battle.
Second, the sales-led motion behind the docs disguises the true cost of customer acquisition. BuiltWith or Wappalyzer scans might detect the Next.js and Contentful stack and assume a product-led growth (PLG) model. But the Marketo + Demandbase + ZoomInfo combination is the giveaway. This is a high-touch, high-ACV motion. Companies competing with Airwallex can’t simply match the developer documentation; they must also build the intent data infrastructure to identify which companies are reading those docs and route them to sales. Airwallex likely has a team of sales development representatives (SDRs) receiving enriched lead alerts every time a Fortune 500 engineer hits a specific API endpoint. That integration between DX content and ABM tools is not trivial to replicate.
Third, the ad pixel diversity points to a sophisticated paid media operation. Running campaigns across Meta, LinkedIn, TikTok, Bing, Reddit, Taboola, and programmatic exchanges requires coordinating creative, audience targeting, and attribution across platforms. The presence of Google Analytics and Google Tag Manager combined with platform-specific pixels suggests a unified measurement framework, likely augmented by a data warehouse for multi-touch attribution. For a smaller competitor, matching that ad spend breadth is cost-prohibitive. The strategic move is to narrow the channel mix and win on specific platforms (e.g., owning LinkedIn ads for finance titles) rather than playing catch-up everywhere.
Fourth, the partner channel via PartnerStack highlights a segment that many fintech startups neglect. The platform supports partner onboarding, deal registration, and commission tracking. Airwallex’s use of it indicates a mature ecosystem play: accounting firms, payment consultants, and e-commerce agencies can refer clients and earn recurring revenue. For a competitor, the question is whether to build a similar two-tier model or double down on direct sales. The tech choice itself isn’t the moat—PartnerStack is commercially available—but the execution of a partner program at scale, with the supporting documentation and training, is a significant operational undertaking.
Finally, the operational separation between public docs and lead generation subdomains is a pattern worth copying. By keeping `grw-landing.airwallex.com` and `bws.airwallex.com` off the main sitemap, Airwallex can iterate on conversion flows, A/B tests (assuming they exist on those subdomains), and promotional campaigns without destabilizing the documentation site. This decoupling also isolates security risks: a vulnerability on a landing page builder shouldn’t compromise the API reference content. Competitors with monolithic architectures that cram blog, docs, and pricing onto the same Next.js instance risk combining different update cadences and security postures into a fragile whole.
Key Takeaways
1. Airwallex runs a two-surface digital strategy: a developer documentation portal for SEO and engagement, and a parallel ABM-driven demand gen engine on separate subdomains. The tools that make this possible are Next.js + Contentful for the former, and Marketo + Demandbase + ZoomInfo for the latter. Founders building API-first products should evaluate whether their current architecture supports such a clean separation or if blurring the two streams creates operational drag.
2. The ABM stack is the real growth engine. While developer docs generate organic traffic, the conversion of that traffic into enterprise pipeline hinges on account identification and intent data. Tools like Demandbase and Unify Intent are expensive and require dedicated ops, but they are a force multiplier when paired with high-quality content. Product leaders evaluating build-vs-buy for ABM should consider whether their documentation traffic volume justifies the investment; below a certain threshold, simpler deanonymization tools like Clearbit might suffice.
3. Multi-cloud infrastructure is a reliability choice, not a cost-saving one. Using Cloudflare for CDN, Google Cloud for compute, and AWS Route 53 for DNS spreads risk and optimizes performance. But it also introduces operational complexity around latency, monitoring, and certificate management. Teams copying this pattern need strong DevOps practices and a commitment to infrastructure-as-code, or they’ll drown in configuration drift.
4. The absence of an observable experimentation tool is a calculated trade-off. With a sales-led motion, the website’s primary job is to frame the product and route to a demo request, not to self-convert. The optimization focus shifts from on-page conversion rate to audience targeting and lead quality. Growth teams at sales-led B2B companies can take this as validation: invest in intent data and sales enablement rather than obsessing over CTA button color.
5. PartnerStack signals ecosystem maturity worth monitoring. If Airwallex’s partner channel scales, it will exert downward pressure on customer acquisition costs relative to pure inbound competitors. The move creates an indirect sales force that can reach SMBs and mid-market accounts that the enterprise sales team would ignore. For early-stage fintechs, evaluating whether a partner platform matches the go-to-market strategy early can prevent a reactive scramble later.
Implications for Product and Engineering Leaders
For CTOs evaluating a similar stack: The combination of Next.js, Contentful, and Cloudflare provides a robust, low-latency developer portal. But it’s not plug-and-play—the build pipeline needs careful handling of static regeneration and cache invalidation to keep docs current. The addition of Sentry for error monitoring and reCAPTCHA for bot mitigation is table stakes; adding Sardine for fraud detection on lead forms is a next-level move that signals serious intent to protect the funnel.
For VPs of Engineering at API-first companies: The amount of documentation pages implies a dedicated technical writing team and a docs-as-code workflow. If your docs are a neglected `README.md`, you’re handing the SEO advantage to Airwallex. But deploying a full Contentful-backed site comes with a CMS licensing cost and a learning curve. Weigh that against developer satisfaction metrics and support ticket volume; often, the investment pays for itself in reduced churn.
For product managers evaluating competitive threats: Airwallex’s stack reveals a cohesive vision: dominate the developer search intent with exhaustive docs, then convert the most valuable visitors via ABM. To compete, you need a similar two-pronged approach. That doesn’t mean copying the exact tools; it means ensuring your docs are comprehensive and fast (perhaps on Gatsby or Docusaurus), while your marketing team runs intent-data-driven outbound on a platform like 6sense or Terminus. The gap isn’t technology—it’s the organizational alignment to make both prongs work in concert.
For growth leaders: The ad pixel diversity is impressive but requires sophisticated attribution. If you’re running Google Analytics and platform pixels without a unified data layer, you’re undercounting Airwallex’s cost-per-lead advantage. Consider implementing Segment or building a custom event bus to unify ad platform data, so you can properly measure the interplay between documentation engagement, ad retargeting, and sales outreach.
The Unseen Layers
While this analysis captures the publicly observable surface, several components remain intentionally or cryptographically hidden. The `bws.airwallex.com` domain hints at a backend microservices architecture, possibly involving Kubernetes on Google Cloud or AWS EKS, but no fingerprints confirm that. The fraud detection tool Sardine implies integration with real-time transaction monitoring, likely accessing internal ledgers and risk models that no web scanner would detect. The status page suggests an observability stack built on Datadog, New Relic, or a homegrown solution, but again, no direct evidence.
What’s also hidden is the data pipeline that connects Demandbase, ZoomInfo, and Marketo to the CRM (likely Salesforce, given the enterprise sales profile). That integration layer is where the real competitive differentiation lives. Airwallex’s ability to score leads algorithmically, trigger automated sequences, and route accounts to the right SDR within minutes of a high-intent signal is a function of data engineering maturity, not just tool selection. Competitors who buy the same tools but fail to integrate them into a cohesive revenue operations workflow will find themselves outflanked.
Final Assessment
Airwallex’s tech stack is a study in purposeful contradiction: a developer-friendly public face masking a sales-led commercial core. The choice of Next.js and Contentful delivers fast, indexed documentation that captures organic search traffic. The ABM and marketing automation stack—Marketo, Demandbase, ZoomInfo, and Unify Intent—converts that traffic into high-value enterprise pipeline. The infrastructure choices (Cloudflare + Google Cloud + AWS Route 53) prioritize performance and resilience. The partner channel via PartnerStack adds a scalable indirect sales motion. The missing pieces—a visible trust center, experimentation tooling—may exist behind logins, but their absence from the public surface creates an opportunity for competitors to fill.
The overarching lesson for technology leaders is this: your public stack tells a story, but that story is often curated. Airwallex has curated a story of technical depth and developer empathy. The real story of how they win deals is the ABM machine humming behind the scenes, invisible to casual observers but evident to anyone who reads the script tags. Understanding both layers is essential for anyone competing in the cross-border payments infrastructure space.