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.
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.
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 developmentReact
When we use it: Highly interactive interfaces, dashboards and admin panels, and products with an existing React codebase to extend.
React development
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 developmentReact 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 developmentKotlin
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 developmentSwift
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
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 developmentPython 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
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.
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 developmentAnthropic Claude
When we use it: Claude models for long documents, careful reasoning and agent workflows that use tools step by step.
Generative AI developmentOpen-source models
When we use it: Self-hosted models when data has to stay inside your infrastructure or running costs need to be predictable.
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 servicesVercel
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.
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
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 implementationOdoo
When we use it: Odoo implementation and customisation for operations, inventory and manufacturing processes that fit its modules.
Odoo implementation
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
ZeroVault
Team file storage with permission-aware workspaces.
Built with
- Next.js
- Better Auth
- MongoDB
- S3
Classify-X
A white-label learning platform for coaching institutes.
Built with
- Next.js
- AWS
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?
Flutter or React Native: which do you use?
Do you build native apps in Kotlin and Swift?
Can you work with our existing codebase?
Which AI models do you use?
Where will our application be hosted?
Which CMS do you use for websites?
Will we be locked into your technology choices?
Related pages
- CompanyHow we workFrom discovery to launch, with demos on a preview link.
- CompanySecurity and data protectionAccess, credentials, secure development and hosting.
- GuideChoosing a tech stackA guide for founders who don't write code.
- GuideNative vs cross-platform appsWhen Flutter or React Native fits, and when native does.
- ServiceSoftware modernizationMoving an ageing system onto a current, supported stack.
- ProductOur productsThe software we build and run ourselves.
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.
- +91 95683 56730
- Chat on WhatsApp
- contact@zeroonecreation.com
- 3rd Floor, 113 Double Phatak, Meerut Road, Roorkee, Uttarakhand 247667
- Monday – Saturday, 9 AM – 5 PM

