Home / Technologies
Technologies
A stack picked for your constraints, not our preferences
We work across the Microsoft and open-source ecosystems. What we recommend depends on your team, your budget and how long the system has to last.
Stack
Frontend
- React
- Next.js
- Angular
- Vue
- TypeScript
- Tailwind CSS
- Flutter Web
Backend
- .NET / C#
- Node.js
- Python
- Java
- Laravel
- Express
- FastAPI
Mobile
- Flutter
- React Native
- Kotlin
- Swift
- Firebase
Data & BI
- Power BI
- SQL Server
- PostgreSQL
- MySQL
- MongoDB
- Azure Synapse
- Microsoft Fabric
AI & ML
- Claude API
- OpenAI
- LangChain
- RAG pipelines
- Vector databases
- Azure AI
- scikit-learn
Cloud & DevOps
- Microsoft Azure
- AWS
- Google Cloud
- Docker
- Kubernetes
- Terraform
- GitHub Actions
CRM & Business Platforms
- Salesforce
- Microsoft Dynamics 365
- Syncra ERP
- Power Platform
- SharePoint
- Odoo
Service Desk & ITSM
- ServiceNow
- Jira Service Management
- Freshservice
- Zendesk
Quality & Security
- Playwright
- xUnit
- Jest
- OWASP ZAP
- Burp Suite
- SonarQube
Selection principles
How we choose
The stack is a means, not a position. Four rules decide it.
- Can your team — or the market you hire from — maintain it in five years?
- What does it cost to run at your actual load, not at demo scale?
- Does it integrate with what you already own, or force a replacement?
- Is it boring enough to be dependable where it needs to be?
Already have a stack in place?
We'll work inside it. Bring your architecture and we'll tell you honestly whether it will carry what you're planning.