Skip to main content

Tech Stack Decisions

Use first principles to evolve your toolset to go from idea to solving valuable problems with minimum time and effort by leveraging a monorepo architecture to innovate at the edges then draw best practices into shared libraries to build multiple apps from a single code base with the best developer experience possible.

Use Developer Roadmaps for coverage of when and how to use each building block in the architecture.

Know Your Tookkit

Fullstack Network


Pipe compoents together to build an application that processes information to create maximal sustainable value.

The perfect stack would comprise of interoperable components with little ill-effect of swapping out one component for another.

  1. What components required in Web3.0 that are different to Web2.0?
  2. What are right questions to ask to decide the best option?
  3. How frequently should stack options be reviewed?
StackmatesWeb 2.0Web 3.0
LanguagesTypescriptTypescript / Solidity
UI FrameworkReactReact
UI/UX ComponentsTailwindUITailwindUI / Scaffold-Eth
App FrameworkNextjsNextjs
MobileReact Native
Cloud HostingVercel / NX Cloud
App BuildNX Cli
API IntegrationNextjs
APP StateBest FitBest Fit
ServerlessVercelSmart Contract ABI to EVM
AuthSupabase AuthMetamask (Need Multisig Solution)
API DomainNode/Nestjs
Message BusRabbitMQ
OrchestrationDocker, Kubernetes, Skaffold
App Logging
Chain QueriesGraph
API Logging

Simplicity is the ultimate sophistication - Leonardo Da Vinci


Adding traditional tech and metaverse to core Web3 technology.


  • Which Blockchain/L2
  • Payments what? when? how?
StackmatesWeb 2.0Web 3.0
LanguagesC#C# / Solidity

Build Tools

Local ServerNXAll Typescipt, DX, Speed and Utility
Local Blockchain DevHardhatDominates mindshare
Smart Contract Build and TestFoundryAll Solidity, Speed and Advanced Security Testing

Traditional Fullstack



Web3 Stacks