What tech stack does Miro use?

Miro's backend is built primarily on Java with Spring Boot and Spring Framework — a common choice for high-scale, enterprise-grade SaaS requiring strong typing, mature tooling, and robust concurrency. Kotlin is used alongside Java, consistent with the broader industry shift at JVM shops toward more expressive modern alternatives without abandoning the JVM ecosystem. Node.js handles lighter async workloads and the developer platform API layer. Ruby on Rails appears in the stack as a legacy component from earlier platform iterations.

All infrastructure runs on Amazon Web Services: EC2 for compute, S3 for object storage, CloudFront for content delivery, Route 53 for DNS, and Lambda for serverless workloads. Kubernetes orchestrates containerized services (Docker), and Terraform manages infrastructure as code. Hazelcast provides distributed in-memory data management critical for Miro's real-time collaborative canvas — enabling concurrent multi-user edits across sessions with low latency. PostgreSQL is the primary relational database; Redis handles caching and pub/sub for real-time board state synchronization.

On the AI infrastructure layer, Miro has made two confirmed public commitments to AWS's AI stack: a partnership with the AWS Prototyping and Cloud Engineering (PACE) team to build an Amazon Bedrock-powered BugManager (achieving 6× fewer team reassignments and 5× shorter time-to-resolution in bug triage), and the February 2026 MCP server built in collaboration with Anthropic and AWS. These are the strongest public signals of Miro's AI infrastructure vendor alignment.

The frontend is a mature TypeScript and JavaScript stack with React as the primary component library, alongside legacy AngularJS code from earlier platform iterations. Less CSS is used for styling. Active job postings consistently list TypeScript, Next.js, and React Native (mobile) as required skills, confirming that the React-first, TypeScript-everywhere direction is current rather than legacy. The Miro developer platform documentation confirms a REST API layer and SDK built for third-party app developers integrating with the canvas.

On the data and analytics side, Segment powers event collection and routing, Looker serves as the business intelligence layer, and New Relic plus Sentry handle application performance monitoring. Pingdom provides external uptime monitoring. The GTM stack is substantial: Salesforce (CRM, system of record), HubSpot (inbound marketing automation), Marketo (enterprise campaign management), Gainsight (customer success health scoring and playbooks), and Zendesk (support). Stripe handles self-serve subscription billing. Contentful is detected as the CMS layer for marketing and documentation content.

On the security side, HackerOne confirms a mature bug bounty and vulnerability disclosure program, and OneTrust handles privacy compliance and consent management — both expected given Miro's GDPR obligations and SOC 2 certifications for enterprise buyers.

The Java/Spring Boot + AWS stack signals a security-conscious, enterprise-grade engineering culture that prefers proven, scalable JVM foundations. Vendors selling into Miro's engineering organization should emphasize AWS-native integrations, Kubernetes compatibility, and JVM ecosystem support — not GCP-specific, Azure-specific, or Node.js-only tooling. Miro's confirmed Amazon Bedrock adoption is the strongest public signal for AI infrastructure vendor preference; Anthropic's MCP partnership makes Claude-native integrations particularly relevant.

The GTM toolchain is the most actionable seller signal for sales and marketing vendors. Salesforce is the system of record; any sales engagement, ABM, data enrichment, or revenue intelligence tool with a native Salesforce integration has a clear path to adoption. Gainsight's presence means CS-adjacent vendors (health scoring, QBR automation, in-app messaging) should speak Gainsight's language and demonstrate complementarity or consolidation potential. HackerOne signals a mature security program; compliance and security vendors can reference Miro's existing investment as evidence of buyer sophistication and a receptive security team.

For competitors trying to displace Miro, the key technical moats are the real-time collaborative canvas architecture (Hazelcast + Redis pub/sub), the depth of the AWS partnership and Bedrock integration, and the developer platform ecosystem (Miro Apps Marketplace). Competing on a faster time-to-canvas or lower price point is unlikely to dislodge Miro from Fortune 100 accounts where multi-year contracts are in place. The more viable displacement angle is bundling — Microsoft Whiteboard (free with M365) and Confluence Whiteboards (free with Atlassian) are the most credible low-cost bundled threats.