Full Stack Overview
Why This Stack
The guiding principle is simple: use the most mainstream, well-documented option at every layer. That means:- Easy to hire around. Rust/Anchor, TypeScript, and PostgreSQL are the dominant choices in their respective domains. Contributors joining the project don’t need to learn proprietary tooling.
- Audited primitives, not custom logic. Streamflow handles revenue-share streaming. Jupiter handles swap routing. Meteora handles bonding curves. Squads handles multisig. None of this is built from scratch — every critical financial operation runs on a primitive that has already been audited and battle-tested in production.
- Publicly verifiable. Squads treasury actions, Jupiter buybacks, and Streamflow payouts are all on-chain and checkable by anyone. There is no opaque backend moving funds.
- Low operational overhead. The infrastructure layer is managed hosting (Railway or Fly.io) with Cloudflare in front — no dedicated DevOps headcount required to keep the lights on.
The stack is deliberately inexpensive to run. Infrastructure costs are low — most of the budget is engineering time. That’s intentional: it’s what makes generous developer revenue-share terms structurally viable rather than aspirational.
Explore the Stack in Detail
On-Chain Architecture
Rust/Anchor programs, Squads multisig, Helius RPC, Streamflow, Meteora DBC, and Jupiter Swap API — every on-chain layer explained.
Backend
TypeScript, Node.js, PostgreSQL, and how the backend connects to Solana via Helius.
Infrastructure
Railway/Fly.io hosting, Cloudflare, and a transparent cost breakdown by phase.
Build Journey
The full roadmap — from Phase 0 to Phase 3 — and how contributors fit in.