OUR STACK
Technologies
Frontend that ships, backend that scales. TypeScript and Java are our primary tools – deep expertise on both sides means your product is maintainable by any senior engineer, not just by us.
BACKEND
Java
Our primary stack for systems that need to stay running for ten years. Every engineer we embed knows it well enough to review anyone else’s code.
Java
Spring
CLOUD
AWS, GCP, Azure
We work with whichever cloud your team already uses. No forced migrations – we build infrastructure alongside the application.
AWS
Azure
GCP
FRONTEND
JavaScript & TypeScript
Angular, React, or Vue – TypeScript throughout. The interfaces your users actually touch: dashboards, admin panels, customer portals. We pick the framework that fits your product and ship frontends that are fast, accessible, and maintainable by any senior engineer.
Angular
TypeScript
React
Vue
DATA & ANALYTICS
PostgreSQL, Python & R
The backbone of every analytics platform we build. Python and R power our data-science and reporting layers – from automated pipelines to interactive dashboards.
PostgreSQL
Python
R
IN PRODUCTION
The stack, deployed
Same stack, different problems. Two recent builds.
-
Learn more: AdMochi – Our SaaS, Built End to EndMost software houses build other people’s products. We also build our own. AdMochi is a campaign data-integrity platform we conceived, designed, and shipped end to end – in production since 2021, evolving with every client it serves.
-
Learn more: Phoenix – Automated MMM PlatformX Lab knew Marketing Mix Modeling inside and out. Their team had the vision – they just needed a partner to bring it to life at scale. We spent 6 months building the first iteration of Phoenix together, and now it’s a platform they sell to enterprise clients.
-
Learn more: mScreen – Media Planning at Full ScaleIn 2018, MediaCom asked us to build a video planning tool. We delivered. Over the next eight years, that tool grew into the planning standard for all of GroupM – used by 2,500+ media planners across 78 markets.
-
Learn more: IoT Workplace AnalyticsA network of IoT sensors and deep market knowledge, turned into a finished analytics product in 10 months — seven modules that take a client from “sensors on desks” to a decision-ready report. New domain for us, and a codebase entirely theirs to keep.
-
Learn more: Dango – Automated Reporting System75% reduction in reporting time – 12-week engagement replacing a 4-day manual workflow with an automated pipeline for Dango.
-
Learn more: Embedded engineering for FinTech – seven years inside SLS’s teamSelf Learning Solutions didn’t outsource their engineering. They expanded it – with us. Since 2018, Codeweaver engineers have worked inside SLS’s team on a daily basis: building infrastructure, shipping a SaaS MVP from scratch, and redesigning the core product interface. Not as a separate vendor with a separate backlog. As part of the team.
-
Learn more: VOD WFM – Video Infrastructure Built to LastMillions of households worldwide watch video-on-demand content delivered through a platform we co-built with TiVO (now XPERI). It runs in 18 markets, processes 66 million tasks a year, and has been operating at production scale since 2016.
Frequently asked
What if my team’s stack doesn’t match yours?
We embed into your stack. Half our engagements are dedicated team work in clients’ existing stacks – Node, .NET, Python, Go. The Technologies page lists what we’d reach for on greenfield builds, not what we refuse to touch.
Won’t we be locked into Codeweaver after this build?
No. Java + Spring is the most senior-dev-portable stack on the market. Any senior backend engineer can pick up and own a Spring Boot codebase in a week. That’s the whole reason we use it.
Do you do greenfield in something other than Java?
Yes, when the use case calls for it. Real-time pipelines in Kotlin, data tooling in Python, frontend-heavy products in TypeScript-only. We don’t force Java on problems that don’t need it.
How do you handle handover?
Documentation lives in the repo, not in our heads. ADRs for every architectural decision, README per module, deployment runbooks in /docs. When the engagement ends, your team owns the codebase – not us.