Skip to content
Steganox Logo
Technology

Chosen for what your team can maintain

We are not loyal to a stack. We are loyal to the outcome, which usually means picking the least exciting technology that solves the problem properly.

The stack

What we build with, and why

Day-to-day working knowledge across the layers most products need. This list is not exhaustive, so if something you rely on is missing, just ask.

Frontend

ReactNext.jsTypeScriptVue.jsTailwind CSSAngular

Backend

Node.jsPythonDjangoLaravelGo.NETJava

Mobile

FlutterReact NativeSwiftKotlin

Cloud & DevOps

AWSAzureGoogle CloudKubernetesDockerTerraform

AI & ML

PyTorchTensorFlowLangChainOpenAIHugging Facescikit-learn

Data

PostgreSQLMongoDBRedisSnowflakeKafkadbt
How we choose

Four rules that decide what goes in a proposal

We are not loyal to a stack. We are loyal to the outcome, which usually means picking the least exciting technology that solves the problem well.

Boring where it counts

Databases, auth and payments get proven technology. Novelty belongs in the parts of the product that differentiate you, not in the parts that simply have to work.

Hireable in your market

We won't leave you with a stack you can't recruit for. If your team is going to maintain it, the technology choice has to match the people you can realistically hire.

Reversible decisions first

Where a choice is hard to undo (data model, tenancy, identity) we spend the time up front. Where it is cheap to change later, we move fast and revisit.

No hidden licences

Everything we build runs on infrastructure and licences in your name. Nothing depends on an account only we can access.

Applied

Where we use it

The stack exists to serve these capabilities.

All services
Next step

Tell us the problem. Not the solution.

You get back an approach, a real range on time and cost, and a straight answer on whether you need us at all. Sometimes that answer is no.

We reply within one business day · NDA on request