What tech stack does Canva use?

Canva's backend is predominantly Java, running on Linux and AWS, structured as a mix of microservices and larger services. Public engineering writeups describe reactive patterns built with Project Reactor and the use of open-source RPC tooling like Finagle, with Jetty in the serving path.

Infrastructure is AWS-centric — Amazon EC2 and CloudFront feature heavily — with Cloudflare providing CDN and edge. Observability and error tracking use tools like New Relic and Rollbar. Beyond Java, Canva writes Python, Scala, PHP, and Swift where they fit, and is an active experimenter with new languages per its own engineering blog.

The Canva editor — its most performance-critical surface — is built in TypeScript with React, having migrated off plain JavaScript, with MobX for state management and Webpack in the build pipeline. The mobile apps use native technologies including Swift on iOS.

On the GTM and data side, public signal is thinner and should be treated cautiously; Canva runs a large self-serve and enterprise motion, so finance/IPO-readiness and sales/marketing tooling are areas of active vendor decisions rather than a confirmed public stack. Only technologies with real public evidence are listed above — no GTM vendors are asserted here without a signal.

Canva is a sophisticated, build-heavy AWS shop with a strong in-house engineering culture (its own foundation models via Leonardo.ai, custom reactive infrastructure), so a pure 'replace your homegrown system' pitch is a hard sell — they often build rather than buy.

The better-fit motions are developer-productivity, observability, security, and data tooling that complements a large Java/AWS/React estate; anything that helps run AI at scale; and — given the IPO push — finance, audit, security-compliance, and data-governance platforms. Map your pitch to 'augment a polyglot AWS-native stack at 265M-user scale,' and lead with integration over displacement.