The rating system

Which tech is better suited?

Every project rates how well each technology fits that specific problem (1–5). Read down a column to see the winner for a build; read across a row to see where a technology shines — and where it doesn't.

Technology Aurora CommerceecommerceHelix AssistantaiTickerrealtimeCatalensvisionVitalshealthConcordcollab
Go 5/5 5/5 5/5 5/5 5/5 3/5
Rust 5/5
TypeScript 4/5 4/5 4/5
Python 5/5
Kotlin 4/5 5/5
PostgreSQL 5/5 4/5 4/5 2/5 4/5 4/5
MongoDB 2/5 2/5 3/5 5/5
Redis 5/5 4/5
Jetpack Compose 4/5 4/5 4/5 4/5
SwiftUI 4/5
Flutter 3/5
Gemini API 3/5 5/5 3/5 4/5 3/5 3/5
Google Cloud 4/5 3/5 4/5 3/5 4/5 4/5
Cloudflare 4/5

Best fit, project by project

Aurora Commerce

Spotlight winner: PostgreSQL — 5/5

Transactions + constraints make overselling and money drift structurally impossible.

Helix Assistant

Spotlight winner: Gemini API — 5/5

One API gives you text embeddings, streamed generation, and function calling — the whole RAG loop.

Ticker

Spotlight winner: Redis — 5/5

Streams give append-only ordering, stable ids, and XREAD-from-id replay that pub/sub cannot.

Catalens

Spotlight winner: MongoDB — 5/5

Vector similarity and a metadata pre-filter run in one aggregation over heterogeneous documents.

Vitals

Spotlight winner: Kotlin — 5/5

One correct copy of the hard logic is reused by both native UIs via expect/actual bridges.

Concord

Spotlight winner: Rust — 5/5

Mature CRDT crates (yrs, automerge) and no-GC performance for the merge-heavy hot path.

Scores are editorial and demonstrated by each build. Disagree? Open a project and record your own rating on its TechFit table — it's saved in your browser.