Technologies
The technologies we build with, and when we would pick each
AMT engineers build backends in Node.js, .NET, Golang and Java Spring, front ends in React, Angular and Vue, native mobile apps in Swift and Kotlin, and AI systems with RAG, agents and MCP servers. Every stack on this page is one we have shipped to production. Below is what we use each for, and when we would advise against it.
Schedule Technical DiscoveryYour first conversation will be with a senior technical partner, not a salesperson.
Our stack, by layer
| Layer | Technologies | What we use them for | Hire or service page |
|---|---|---|---|
| Backend | Node.js (TypeScript), .NET (ASP.NET Core), Golang, Java Spring Boot | APIs, integrations, high-throughput services, enterprise systems | |
| Web front end | React and Next.js, Angular, Vue | Web apps, dashboards, customer portals | React developers |
| Mobile | Swift (iOS), Kotlin (Android) | Native apps where performance or device features matter | Mobile app development |
| AI | LLM applications, retrieval-augmented generation (RAG), AI agents, MCP servers, voice AI | Assistants, agents and AI features that work on your own data | AI development |
| Quality | Selenium, Playwright | Automated test suites in your pipeline | QA automation engineers |
| Cloud and DevOps | Cloud infrastructure, containers, CI/CD pipelines | Infrastructure, pipelines, monitoring | DevOps and cloud |
| Blockchain | Algorand, Casper | Smart contracts and verifiable records | Blockchain development |
The support calendar
Running software on a version that no longer gets security fixes is the most common risk we find when we take over a system. Here is where the main platforms stand.
Stuck on an unsupported version? See legacy application modernization.
| Platform | Version | Status | What to do |
|---|---|---|---|
| .NET | 8 (LTS) | Support ends 10 November 2026 | Plan the move to .NET 10 now |
| .NET | 9 (STS) | Support ends 10 November 2026 | Same move to .NET 10 |
| .NET | 10 (LTS) | Supported to 14 November 2028 | The target for new work and upgrades |
| .NET Framework | 4.8.x | Supported as part of Windows, no new features | Stable, but every new library targets modern .NET. Plan a migration path |
| Node.js | 18 and 20 | End of life, no security fixes | Upgrade to 22 or 24 |
| Node.js | 22 and 24 | LTS | Safe for production. Start new services on 24 |
| AngularJS (1.x) | All | End of life since 31 December 2021 | Migrate. See /services/legacy-application-modernization |
See an AngularJS to Angular 21 migration in progress
Checked against Microsoft's .NET support policy and nodejs.org in October 2026.
Stack choices we push back on
- Starting new work on .NET Framework. It is supported but frozen. New libraries target modern .NET.
- Odd-numbered Node.js releases in production. They never become LTS.
- A microservices architecture for a team of five. You pay the operational cost before you get the benefit.
- Kubernetes before you need it. Most products we see run well on managed services for a long time.
- A cross-platform mobile framework when the app lives on device features. We build native in Swift and Kotlin for those.
- Fine-tuning a model when retrieval would do. Most enterprise AI problems are data access problems, not model problems.
How we choose a stack for you
- Start from what your team already runs. A stack your people can maintain beats a better one they cannot.
- Check the support calendar. No new work on versions near end of support.
- Price the operations, not only the build. Hosting, monitoring and on-call cost more than development over a system's life.
- Write the decision down in your repository, with the options we rejected and why.
FAQ
What technologies does AMT use?
Is .NET 8 still supported?
Which Node.js version should we run in production?
Tell us your stack and what you need built or fixed.