Languages and APIs
.NET (C#, ASP.NET), Python (FastAPI, Django), Java, Node.js, TypeScript, PHP, and Go — APIs and services with environments that keep unfinished work off the public URL.
Technologies
We work across the stacks organisations already run — .NET, Python, Java, JavaScript, SQL, and the major clouds — and we pick what the job needs.
12+
Languages and runtimes
.NET, Python, Java, Node, TypeScript, PHP, and Go.
6+
Databases
PostgreSQL, MySQL, SQL Server, and the stores around them.
4
Cloud platforms
AWS, Google Cloud, Azure, and Firebase.
2
Mobile clients
iOS and Android — native or cross-platform.
What we ship with
Web
React, Next.js, Angular, Vue, and accessible HTML. ApexCMS when editors should own the copy.
Mobile
Android, iOS, Flutter, and React Native — with a documented API behind the client.
Cloud
AWS, Google Cloud, Microsoft Azure, Firebase, Linux, Docker, and TLS as default — including backups we have actually restored.
AI
Licensed model APIs, evaluation sets, an audit trail, and a kill switch — on the backend you already run. ProMath is the product proof.
CMS and content
ApexCMS for brochure and product sites: blocks, types, draft, publish. This website is the live example.
SEO and analytics
Metadata, sitemaps, robots, and measurement you can turn off. AI may draft; an editor approves.
Platforms at a glance
.NET
C#, ASP.NET Core, APIs and enterprise apps.
Python
FastAPI, Django, scripting, and AI services.
Java
Services and integrations beside existing estates.
Node.js
TypeScript APIs and tooling.
PHP
When the organisation already lives there.
TypeScript
Typed front ends and Node services.
PostgreSQL
Primary SQL store for new products.
MySQL
Widely deployed, well understood.
SQL Server
Beside .NET and Windows estates.
MongoDB
Document stores when the shape fits.
Redis
Cache, queues, and session.
AWS
Compute, storage, CDN, and production defaults.
Google Cloud
GCP for teams already on Google.
Azure
Microsoft cloud, Entra, and .NET.
Firebase
Auth, realtime, and mobile-first backends.
React / Next.js
Sites and consoles editors can still use.
Android / iOS
Native clients and store listings.
Flutter
Cross-platform when one codebase is the point.
Docker
Containers when they simplify the deploy.
Linux
The usual production OS we stay responsible for.
How we choose
We do not force a favourite stack onto a working organisation. If you already run .NET and SQL Server, we build there. If the product is Python and PostgreSQL, we build there. Cloud follows the same rule: AWS, Google Cloud, Azure, or Firebase when that is the honest home for the app.
What stays the same: a written scope, a private preview, and a live URL that only shows what you published.