The Stack We Build On
174 technologies across 12 categories — the languages, chains, frameworks and services our teams work in every day. We pick per project from this list rather than pushing everything through one stack.
Frontend Technologies
18 technologies
Everything the user actually touches. We pick per product — a React or Next build where state is heavy and the interface does real work, something lighter where the page is mostly content and load speed is the point.
React JS
Next.js
Angular
Vue.js
HTML5
CSS3
JavaScript
TypeScript
Bootstrap
Tailwind CSS
Material UI
Svelte
Nuxt.js
Ember.jsBackend Technologies
18 technologies
The services behind the screen: APIs, business rules, scheduled jobs and integrations. The language is chosen for the load pattern and for whoever has to run the system after we hand it over, not for novelty.
Node.js
Express.js
PHP
Laravel
Python
Django
Flask
Java
Spring Boot
Go (Golang)
.NET
ASP.NET
C#
.NET CoreMobile Technologies
10 technologies
Native where the app needs the device — camera, secure storage, background work, platform APIs. Cross-platform where it is mostly screens and API calls, and one codebase across both stores saves real budget.
React Native
Flutter
Swift
Kotlin
.NET MAUIBlockchain Networks
18 technologies
Where your contracts and assets actually live. We choose the chain on fees, finality and where your users already hold funds — and we will tell you when a chain is the wrong answer entirely.
Ethereum
BNB Chain
Solana
Avalanche
Cosmos
Optimism
Arbitrum
Base
Polygon
Polygon zkEVM
StarkNet
Celestia
Polkadot
zkSyncDatabase Technologies
11 technologies
How data is stored, queried and kept correct. Relational for anything financial or reportable, with a document store, cache or search index alongside it where the access pattern justifies the extra moving part.
Cloud & DevOps
16 technologies
Where the product runs and how it gets there. Infrastructure defined as code, services in containers and deploys through a pipeline, so releases are repeatable instead of one person following notes.
Blockchain Frameworks & SDKs
12 technologies
For when a contract is not enough and the project needs its own chain, rollup or subnet. These toolkits turn that from a research project into a build with a known upgrade path.
Cosmos SDK
CosmWasm
Substrate
Polygon CDK
zkRollups
zkEVM
AA (ERC-4337)
OP Stack
Arbitrum Orbit
Avalanche Subnet
Solana AnchorSmart Contract Technologies
11 technologies
The languages, test harnesses and audited libraries we write on-chain code with. Contracts hold funds and cannot be patched quietly, so testing and known-good libraries matter far more than shipping speed.
Hardhat
Foundry
Geth
Chainlink
Solidity
Rust
VyperAI & Machine Learning
15 technologies
Hosted models where time to value matters, open weights where your data cannot leave the estate. Plus the frameworks around them — retrieval, agents, training and evaluation — because the model is rarely the hard part.
CohereWeb3 Libraries & Tools
18 technologies
The layer between your application and the chain: wallet connection, contract calls, node access and indexed data. Most of a dApp's usability is won or lost here rather than in the contract.
Web3.py
Solidity
RainbowKitCMS & E-Commerce
11 technologies
Platforms for teams that need to publish and sell without a developer in the loop. We extend, theme and integrate them rather than rebuilding what they already do well.
API & Integrations
16 technologies
The third-party services a product has to talk to — payments, CRM, messaging, maps and documents. Most of the build time goes into the edge cases and failure paths, not the happy path.
Not sure which stack fits your build?
Tell us what the product has to do, the constraints you are working under and where it has to run. We will come back with a recommended stack and the reasoning behind it.
Get a stack recommendation