Stack-Agnostic by Principle: How We Actually Choose a Tech Stack

Every agency says they pick "the right tool for the job." Almost none of them actually do.

It's the most common line on any agency's homepage, and it's usually not true. Most agencies have a stack they know well, a stack their team is hired around, and a stack every project quietly gets steered toward — regardless of what the project actually needs. That's not malicious. It's just easier to sell what you already know.

Stack46 is built differently, and the proof isn't a claim on a page — it's that our own ecosystem runs on genuinely different stacks, chosen for genuinely different reasons. Here's how the decision actually gets made.

The real stack, and why it's this varied

Across the products Stack46 has built — Route46, Cinevenn, 46 Dogs, FourSix46 itself — the technology choices aren't the same, and that's not an accident:

• Cinevenn runs on FastAPI (Python) and MySQL, containerised on AWS. A five-pillar platform with real-time features and a future roadmap that leans on AI needed Python's ecosystem and async performance under load.
• Route46 runs on React, TypeScript and Firebase Functions. It inherited an existing frontend — the decision there wasn't "what's ideal from zero," it was "what's the right infrastructure to build on top of what already exists."
• FourSix46 and 46DC run on Next.js, Firebase Auth, Cloud Firestore and FireCMS — a content-heavy brand site needed a headless CMS and fast, server-rendered pages far more than it needed a custom backend.
• 46 Dogs, still in development, is planned on FastAPI, MySQL and LLM-assisted profile generation — closer to Cinevenn's shape, because it's solving a similarly data-heavy, registry-style problem.

Four products, four different combinations of the same broader toolkit. That's what "stack-agnostic by principle" actually looks like when you check the work instead of the slogan.

The questions that actually decide it

There's no formula, but there is a consistent set of questions we run every project through:

What does the data actually look like? Relational, tightly connected data — identities, transactions, ownership records — points toward something like MySQL or PostgreSQL. Flexible, document-shaped content points toward Firestore or MongoDB. Cinevenn's verified credits and marketplace transactions needed relational integrity; FourSix46's brand content didn't.

Does it need to feel real-time? A platform with live auditions, marketplace activity or messaging needs WebSockets and a backend built for async load — that's FastAPI's strength. A marketing site publishing blog posts doesn't need any of that.

What already exists? Route46 answered this one for us. When there's a working codebase, the right question isn't "what would I build from zero" — it's "what's the best foundation to build on top of what's already here."

Where is it going next? Cinevenn and 46 Dogs are both built with AI features on the roadmap, which made Python's ecosystem the sensible foundation even before those features exist — retrofitting a Python service onto a Node backend later is exactly the kind of cost we try to avoid by deciding early.

Where we land on cloud: genuinely multi-cloud, not a slogan

The same principle holds for infrastructure. Stack46 runs real production work across AWS, Google Cloud, Azure and Firebase — not because we couldn't pick one, but because different products have different needs. Cinevenn's storage and scale requirements suit AWS. FourSix46's content-driven site suits Firebase's tight integration with FireCMS. A client with existing Azure infrastructure doesn't need to be migrated off it just because it's not our default.

What this means if you're evaluating an agency

If an agency's answer to "why this stack" is "it's what we use for everything," that's worth noticing — not necessarily disqualifying, but worth a direct question. The right stack for a five-pillar real-time platform is rarely the right stack for a content-driven brand site, and an agency that reaches for the same toolkit regardless is optimising for their own convenience, not your project.

The short version

Stack46 runs FastAPI and MySQL on AWS for Cinevenn, React and Firebase Functions for Route46, and Next.js with Firebase and FireCMS for FourSix46 — four different combinations across one ecosystem, chosen by what the data, the real-time needs, the existing code, and the roadmap actually require. That's what being stack-agnostic looks like when it's checked against real, shipped work rather than taken on trust.

Stack46 is the full-stack software development agency and in-house engineering arm of FourSix46 Global Ltd (UK Company No. 16712658), founded by Dinesh Koyyalamudi. We recommend the right technology for your project — not the one that's easiest for us to reuse.

Read more: How We Built Cinevenn