The technology stack we build software with, and how deep we go in each
If you already run a system, find your stack below and see where we stand in it, including the places we would have to build a team for you. If you have not picked a stack yet, Atyantik chooses one with you as part of the work. Either way, the code is yours from the first day.
Every technology we build with, by layer
Grouped by the part of the product it serves.
Frontend
- React
- Next.js
- Remix
- Preact
- Vue
- Angular
- Astro
- Svelte
- HTMX
- Alpine
Mobile
- React Native
- Flutter
- PWAs
- native Android (Kotlin, Java)
Backend
- Node.js
- NestJS
- Express
- Fastify
- Hono
- AdonisJS
- PHP
- Laravel
- Symfony
- CakePHP
- Python
- Django
- REST and GraphQL APIs
- Supabase
- Firebase
- Appwrite
AI and agents
- AI and ML integration
- AI agent workflows
- tool calling
Identity and SSO
- Single sign-on
- secure authentication
Commerce and CMS
- Magento
- WordPress
- headless CMS
Cloud and DevOps
- AWS
- Google Cloud
- Cloudflare
- DigitalOcean
- Vercel
- Netlify
- Docker
- Kubernetes
- CI/CD pipelines
How deep we go in each technology
A name on a list says nothing about depth, so here is ours, in three groups. Each technology links to where you can hire for it or scope a build.
What we lead with
Hire a developer or scope a full build, whichever the work needs.
Also in our range
Real, current work we take on, often as part of a wider build.
- WordPress: new builds, themes, plugins, headless, migration and maintenanceStructuring WordPress at scale
- Python and DjangoHire Python developers
- Vue, Angular, Astro, Svelte, HTMXHTMX or React
- React Native, Flutter, PWAsBuilding a React PWA
- AWS, Google Cloud, Docker and Kubernetes, for software we build or runRancher on Kubernetes
- AI-augmented developmentHow we use AI tooling
- SSO and identityWhat SSO costs to implement
- B2B SaaS platformsScope a SaaS build
We assemble the team for your engagement
We do not lead in these today. If your engagement is large and long enough to support it, we build the team for it. Talk to us first.
Ask about your engagement- Native iOS
- Native Android (Kotlin, Java)We have shipped native Android apps in Kotlin and Java, mostly alongside device and RFID work.
- Model training and fine-tuning
- DevOps and SRE as a standalone service
- MagentoWe have delivered Magento by assembling the team for the engagement.
How common each web framework or technology skill is among professional developers
How easy it will be for you to hire for the stack later is one of the things we weigh when we choose it. If we build your product, you should be able to staff it without us. Node.js and React each reach nearly half of the professional developers who answered. Laravel, WordPress and Django each sit around one in ten. Phoenix, shown for comparison, sits near one in forty.
Show data table
| Item | percent of professional developers answering the web frameworks question |
|---|---|
| Node.js | 49.1% |
| React | 46.9% |
| WordPress | 12.4% |
| Django (Python) | 11.7% |
| Laravel (PHP) | 9.3% |
| Phoenix (Elixir) | 2.5% |
We work inside the system you already run
If you run software today, we start from it. We modernize without forcing rewrites where audits show incremental hardening will do, and we change the parts that need work in steps. Martin Fowler calls this the Strangler Fig pattern: build the new system around the edges of the old one until the old one can be retired. In a McKinsey and University of Oxford study of more than 5,400 IT projects, every additional year a project ran added 15 percent to its cost overrun. That is one reason we change a running system in short steps.
15%
more cost overrun for every additional year an IT project runs
Case study
A supplier portal built beside the system a client already ran
A manufacturer needed a portal for its suppliers. More than 400 suppliers had to use it, most of them outside the client's own systems. The portal had to stand alone. Purchase orders were raised in the client's existing system and uploaded, so nothing depended on an integration project.
- 1Supplier
- 2Gate
- 3Warehouse
- 4Quality checks
Not picked a stack yet? Here is how we choose it
Stack selection is part of our scope. You do not need to bring a tech opinion to the first call.
Your requirements
What the product has to do, who uses it, and the limits it has to work within.
Your team's current capabilities
What the people who will own it already know, so your team can run it after launch.
Your scale targets
How many users, how much data, and how fast you expect both to grow.
An architecture that fits
We propose it and you question it. Two of the things we weigh are how long each runtime or framework will stay supported and how easy it will be for you to hire for the stack later. The hiring chart above shows how common each web framework or technology skill is. AI tooling assists our work, and the judgment behind every architectural and security decision stays with people.
We choose the stack that fits the project, not the one that maximizes our familiarity.
Our software development processWhat you own, and how to check anyone's code
We stop working together
What we commit to
From the first day, every line of code is your IP. The code lives in your repositories and the deployments in your cloud accounts. If you do not have Git hosting, cloud accounts or storage yet, we set them up and hand you the keys.
Someone new has to take it over
What we commit to
Documentation starts on the first day and stays current through delivery. Architecture decisions are written down, and every change goes through code review by a senior software engineer.
You cannot read the code yourself
What we commit to
Use a public yardstick. ISO/IEC 25010:2023 is an international standard that defines a quality model for software products, written for "developers, acquirers, quality assurance and control staff and independent evaluators". Under maintainability it names five qualities: modularity, reusability, analysability, modifiability and testability. Ask any firm, us included, to show how its code does on each one, or hand the list to an adviser you trust.
When we are not the right team
We are a good fit when
- Your stack is in the first two groups above.
- You run a system and want it improved in steps, without a big rewrite.
- You have not picked a stack and want it chosen with you, as part of the build.
Look elsewhere when
- You need a vendor with a SOC 2 report, ISO/IEC 27001 certification or a HIPAA attestation of its own. We hold none of them, though we build software to pass GDPR, HIPAA and SOC 2 audits. Look for a firm that holds the one you must cite.
- You need a native iOS team for a short build, starting now. A firm with a standing iOS team will move faster.
- You need operations only, with no software being built, on an engagement too small or too short to build a team for. A dedicated SRE provider fits that better.
- The core of the work is training or fine-tuning a model, on an engagement too small or too short to build a team for. Look for a team that does that as its main work.
Before you choose a stack partner
Will I be able to hire developers other than you for this?
Do I need to know what stack I want before we talk?
Will you move us to the stack you prefer?
Will we have to rewrite what we have?
Do you build native iOS apps or fine-tune models?
Do you hold a SOC 2 report or HIPAA attestation?
What happens if we stop working together?
Tell us your stack, or tell us you do not have one yet
We will come back with how we would work in it. If we are not the right team, we will say so plainly.

- The code is yours from the first day.
- You do not need a tech opinion to start.