Technology

Engineered for what comes next.

We choose tools for the second year, not the launch. Every technology in this list is one we use in production, and one we are prepared to maintain.

Approach
Boring where it counts
Standard
Typed, tested, observable
Hosting
Cloud, multi-provider

Capabilities

The stack, by discipline.

Presented as capability rather than a wall of logos. If a technology is not here, we will tell you honestly whether we use it.

Frontend

01

Interfaces engineered for speed, accessibility, and longevity.

  • TypeScript
  • React
  • Next.js
  • React Native
  • CSS architecture
  • Design tokens

Backend

02

Systems designed around clear domain boundaries and explicit contracts.

  • Node.js
  • Python
  • Go
  • REST
  • GraphQL
  • Event-driven architecture

Mobile

03

Products that behave properly on the device they live in.

  • Swift
  • Kotlin
  • React Native
  • Expo
  • App Store delivery
  • Push and offline systems

Cloud

04

Managed infrastructure, chosen for operational honesty.

  • AWS
  • Google Cloud
  • Azure
  • Vercel
  • Cloudflare
  • Serverless

AI

05

Applied intelligence, grounded in real workflows and evaluated honestly.

  • OpenAI
  • Anthropic
  • AWS Bedrock
  • Retrieval pipelines
  • Evaluation
  • Human oversight

Infrastructure

06

Delivery practice that keeps environments consistent and reversible.

  • Docker
  • Kubernetes
  • Terraform
  • GitHub Actions
  • Observability
  • Incident practice

Data

07

Data modelled as a product asset, not a by-product.

  • PostgreSQL
  • Redis
  • pgvector
  • Analytics pipelines
  • Warehousing
  • Reporting

Security

08

Considered from the first commit rather than the first audit.

  • Authentication and authorisation
  • Encryption
  • Secrets management
  • Audit trails
  • Dependency hygiene
  • Threat modelling

This list describes the technologies TWNTIS actively uses in client work. No certifications, partnerships, or vendor accreditations are claimed on this page.

Engineering standard

Architecture isa promise to the future.

The decisions that are cheapest to make are the ones made early: how data is modelled, how boundaries are drawn, how the system is observed. We treat those decisions as design, not overhead.

Our process

Start a project

Build onsolid ground.

Tell us about your constraints. Good technology decisions start with the constraints, not the tools.