Our tech stack

The technologies we build with, layer by layer

This is the tech stack Zero One Creation uses to build websites, apps, business systems and AI products, grouped by layer, with a line on when we reach for each one.

It is written for the technical people evaluating us. Every technology here is one we use in client work or in the products we run ourselves.

Browse the stack

The stack

Our tech stack, from interface to infrastructure

Nine layers, from what people tap and click to where the product runs. Where we offer a dedicated service for a technology, the card links to it.

01

Frontend

Websites, web apps and the screens people use every day.

  • Next.js

    When we use it: Our default for marketing sites, SaaS front ends and web apps that need fast pages and search visibility. This website, Classify-X and ZeroVault run on it.

    Next.js development
  • React

    When we use it: Highly interactive interfaces, dashboards and admin panels, and products with an existing React codebase to extend.

    React development
02

Mobile

Android and iOS apps, cross-platform or native.

  • Flutter

    When we use it: Our default for new Android and iOS apps: one codebase and a consistent interface on both platforms.

    Flutter app development
  • React Native

    When we use it: Cross-platform apps for teams that already work in React and TypeScript, or apps that share logic with a React web product.

    React Native development
  • Kotlin

    When we use it: Native Android code when a feature needs deep hardware or platform access, either a full native app or a platform channel inside a Flutter app.

    Android app development
  • Swift

    When we use it: Native iOS code for the same reasons: hardware features, new platform capabilities or screens where performance is critical.

    iOS app development
03

Backend

APIs, business logic, integrations and background jobs.

  • Node.js

    When we use it: APIs, integrations, webhooks and real-time features in TypeScript, sharing one language with the front end.

    Node.js development
  • Python and Django REST

    When we use it: Data-heavy back ends and platforms with rich admin needs. Python is also our language for AI and data pipelines.

    API development
04

Data

Where your records live, and how they stay consistent.

  • PostgreSQL

    When we use it: Our usual choice for business systems: CRMs, ERPs and anything with transactions, reports and strict relationships. Social Sphere CRM runs on it.

  • MongoDB

    When we use it: Document data whose shape varies from record to record, such as file metadata and content. ZeroVault stores its data in MongoDB.

05

AI

Language models for assistants, agents, search and document work.

  • OpenAI

    When we use it: GPT models for assistants, structured extraction and content tasks, with mature tooling for function calling.

    AI agent development
  • Anthropic Claude

    When we use it: Claude models for long documents, careful reasoning and agent workflows that use tools step by step.

    Generative AI development
  • Open-source models

    When we use it: Self-hosted models when data has to stay inside your infrastructure or running costs need to be predictable.

06

Cloud and hosting

Where it runs, always in accounts you own.

  • AWS

    When we use it: Applications that need servers, managed databases, S3 storage and fine-grained control. Classify-X runs on AWS, and ZeroVault keeps its files in S3.

    AWS cloud services
  • Vercel

    When we use it: Next.js websites and front ends, with a preview link for every change so you can review work before it goes live.

07

Commerce

Online stores and the systems around them.

  • Shopify

    When we use it: Stores where a proven checkout, a large app ecosystem and an easy admin matter more than custom logic.

    Shopify development
08

Business platforms

Off-the-shelf CRM and ERP, implemented and customised.

  • Zoho

    When we use it: Implementation and customisation of Zoho apps such as Zoho CRM, for teams that choose the Zoho suite.

    Zoho implementation
  • Odoo

    When we use it: Odoo implementation and customisation for operations, inventory and manufacturing processes that fit its modules.

    Odoo implementation
09

Content management

How your team edits the website without a developer.

  • Sanity

    When we use it: Our headless CMS of choice for content-led Next.js sites, with previews and structured content. We use it on this website.

Also in our toolkit

Supporting tools we use across projects, chosen per product.

  • TypeScript
  • Tailwind CSS
  • Docker
  • GitHub Actions
  • Better Auth
  • Drizzle ORM
  • Hono
  • Firebase
  • Razorpay
  • Stripe
  • LangChain
  • n8n

How we choose

Four rules for picking a stack

The right stack is the one your product and your team can live with for years, not the newest one. For a plain-language version, read our guide to choosing a tech stack.

  • 01.

    Proven and well supported

    Mainstream technologies with long-term support, active communities and plenty of engineers who know them.

  • 02.

    Fits the people who will maintain it

    If your team works in React, that counts. A stack is only good if someone can look after it in five years.

  • 03.

    Your accounts, no lock-in

    Open frameworks, hosted in your accounts and documented, so you can change teams without a rewrite.

  • 04.

    Off-the-shelf when it fits

    If Shopify, Zoho or Odoo already does what you need, we say so rather than building it again.

In production

The same stack runs our own products

We build and run our own software, so the stack on this page is one we depend on ourselves, not a list of logos. A few examples:

  • Social Sphere CRM

    Our own CRM product.

    Built with

    • Next.js
    • PostgreSQL
    • Drizzle ORM
    • Better Auth
    Read the case study
  • ZeroVault

    Team file storage with permission-aware workspaces.

    Built with

    • Next.js
    • Better Auth
    • MongoDB
    • S3
    See the product
  • Classify-X

    A white-label learning platform for coaching institutes.

    Built with

    • Next.js
    • AWS
    Read the case study

Taking over an existing product? We start by reading the code and documenting what we find. If it needs moving onto a current, supported stack, see legacy software modernization.

Evaluating us for a technical project? Talk it through with an engineer.

Bring your architecture questions, your existing stack and your constraints. We'll tell you what we'd use, and why, in writing.

Technical questions

Frequently asked questions

Which tech stack do you recommend for a new web application?

A common starting point is Next.js on the front end, Node.js or Django REST behind it, PostgreSQL for data, and hosting on AWS or Vercel in your own account. We adjust it to your product, your integrations and the people who will maintain it, and explain the choice in the proposal.

Flutter or React Native: which do you use?

Both. Flutter is our default for most new apps because it gives a consistent interface and one codebase for Android and iOS. React Native suits teams already working in React or apps that share logic with a React web product.

Do you build native apps in Kotlin and Swift?

Yes, when the product needs it: deep hardware access, new platform features or performance-critical screens. We also write Kotlin and Swift inside Flutter apps through platform channels when only one feature needs native code.

Can you work with our existing codebase?

Usually, yes. If your product uses the technologies on this page or close relatives of them, we start by reading the code and documenting what we find. If it uses a stack we don't work in, we'll tell you plainly rather than learn on your project.

Which AI models do you use?

We choose per use case, including models from OpenAI and Anthropic and open-source models, based on accuracy, cost and privacy needs. Where data must stay in your infrastructure, a self-hosted open-source model is often the right call.

Where will our application be hosted?

In cloud accounts your organisation owns. Next.js sites usually run on Vercel; applications that need servers, managed databases or storage usually run on AWS. You hold the account and the billing relationship.

Which CMS do you use for websites?

Sanity is our headless CMS of choice for Next.js sites, and we use it on this website. For simpler needs or specific workflows we also build custom admin panels.

Will we be locked into your technology choices?

No. Everything on this page is a mainstream, widely used technology. The code lives in your repository, runs in your accounts and is documented, so another team can pick it up.

Talk to an engineer

Tell us about the product and the stack around it.

Share what you're building, what already exists and anything that's fixed, such as a cloud provider or a framework your team knows. We'll recommend a stack and explain the trade-offs.

We use your details only to reply to this enquiry. See our privacy policy.