A practical view of the technology behind Clarge: application development, integrations, cloud and data. The examples connect specific tools with professional roles and independent work, so you can see the fit with your environment.
For a smaller team, the useful questions are practical: where the application runs, who can access it, how data is stored and what it costs to maintain.
Microsoft environments · Options to assess
Microsoft Azure
For a business using Microsoft tools, we can start the technical discussion with Azure: App Service for web applications and APIs, Azure SQL for relational data, and Entra ID for identity and access.
The professional background includes AWS for serverless services, object storage and managed databases. The Coredination role and the Scania assignment through Coredination show the relevant environments.
AWS Lambda
Amazon S3
Amazon DynamoDB
Amazon RDS
The starting point is the environment you already have. We consider account ownership, access, backups, monitoring and running costs before proposing a change.
Tools from professional roles, studies and independent projects. The examples below show where the main stacks have been used.
01
Backend & integration
Application logic, service boundaries and connections between systems.
C#
.NET
.NET Framework
ASP.NET Core
Entity Framework
Web APIs
Node.js
TypeScript
JavaScript
Python
Django
Express.js
REST APIs
GraphQL
02
Cloud & delivery
Serverless services, containers and the path from a change to a running system.
AWS Lambda
AWS S3
AWS RDS
Docker
Kubernetes
JFrog
SSH
03
Data & observability
Storage, event flows, search and visibility into how a system behaves.
PostgreSQL
DynamoDB
Apache Kafka
OpenSearch
Elasticsearch
Grafana
04
Interfaces & collaboration
The application people use, with shared code and review as part of delivery.
React
Next.js
Tailwind CSS
HTML
CSS
Git
Where the tools meet the work.
Roles and assignments from founder Elias Luzwehimana’s professional background, with the working relationship and technologies shown for each.
Symetri Europe
Senior software engineer · Full-time role
+
A senior engineering role in Symetri’s shared software platform, focused on C# and .NET, ASP.NET Core, Entity Framework and Web APIs. The role combines backend work with architecture discussions and collaboration with product owners.
C#
.NET
.NET Framework
ASP.NET Core
Entity Framework
Web APIs
×
Telia Company AB · Academic Work
Software engineering assignment · Via Academic Work
+
Work on customer portals in a telecom environment, using React and Node.js alongside Kafka, Docker and Kubernetes. The responsibility covered features, maintenance and fixes within an existing team.
React
JavaScript
Node.js
Express.js
Apache Kafka
Docker
Kubernetes
OpenSearch
Elasticsearch
Grafana
Coredination
Software engineer · Coredination
+
Software engineering on a field-service management product: React and Next.js interfaces, Node.js services, GraphQL APIs and serverless AWS infrastructure.
React
Next.js
TypeScript
Node.js
Express.js
GraphQL
AWS Lambda
DynamoDB
S3
Tailwind CSS
Scania
Customer assignment · Through Coredination
+
A backend integration assignment during the Coredination role, supporting Scania’s workflows with Python, Django, PostgreSQL, REST APIs, AWS RDS and container-based deployment.
Python
Django
PostgreSQL
REST APIs
AWS RDS
Docker
JFrog
Independent work.
Our broader background also includes HTML, CSS, Git and Bootstrap through studies and independent projects.
The Clarge website
The Clarge website is an independent project built with Next.js, React and TypeScript and deployed on Vercel. It includes responsive interfaces, English and Swedish content, and server-rendered pages.
Next.js
React
TypeScript
Vercel
Your system sets the starting point.
We review the codebase, dependencies, data flows, deployment process and the knowledge already in your team. Keeping an established tool can be the right decision. A change needs a clear purpose, a realistic migration path and someone able to maintain it.