Skip to content
production / main000%
Home
All tools
ARCH-01RULE ENGINEEVIDENCE-FIRST / NO LOGIN

Tech Stack Architect

Recommend frontend, backend, data, auth, edge/CDN and delivery choices from actual constraints, with rationale and alternatives.

01Decision rationale02Vendor lock-in visibility03Alternative architecture
ARCH-01 / EVIDENCE WORKBENCH
OBSERVED → DERIVED → DECISION

A report can be previewed, but without a target name it is not a shareable technical record.

FRONTEND
01 · React + TanStackFIT 88

Type-safe routing/data flow and framework flexibility for product applications.

02 · Next.jsFIT 80

Strong defaults and ecosystem for content/SEO-heavy surfaces.

BACKEND / DATA
01 · SupabaseFIT 90

Reduces Postgres/auth/storage operations for small teams; managed-service lock-in remains a trade-off.

02 · PostgreSQL + API serviceFIT 90

Provides service-boundary and portability control at higher operational cost.

EDGE / DELIVERY
01 · CloudflareFIT 92

Combines CDN, edge compute and security at one boundary.

02 · VercelFIT 76

Low-operations frontend delivery with strong preview workflows.

AC / EVIDENCE REPORT
AC-ARCH-01-20260810100710 · METHOD 2.0

PDF / human · MD / repo · JSON / automation

ANALYSIS SUBJECT
SELF-REPORTED
TARGET NOT PROVIDED
TARGET
saas · small · solo team
SCOPE
Starting architecture and trade-off scenario
EVIDENCE BASIS
SELF-REPORTED
ARCH-01 / EVIDENCE FILE

Tech Stack Architect

FRONTEND: React + TanStack 88/100 · BACKEND / DATA: Supabase 90/100 · EDGE / DELIVERY: Cloudflare 92/100

EVIDENCE COVERAGE
45/100
CONFIDENCE
LOW
CLAIM BOUNDARY

This tool does not claim one universally correct stack. It produces a trade-off-visible starting hypothesis by scoring alternatives against the supplied constraints.

01

Executive brief

At least two alternatives are compared per layer.
Fit scores are decision support, not benchmark results.
02

Findings and decision points

F-1MEDIUM CONFIDENCE

FRONTEND → React + TanStack

Type-safe routing/data flow and framework flexibility for product applications. Alternative: Next.js (80/100).

EVIDENCE → E-CONSTRAINT-1 · E-CONSTRAINT-2 · E-CONSTRAINT-3 · E-CONSTRAINT-4

Action: Lock the decision with ADR-01 including context, evidence and revisit conditions.

F-2MEDIUM CONFIDENCE

BACKEND / DATA → Supabase

Reduces Postgres/auth/storage operations for small teams; managed-service lock-in remains a trade-off. Alternative: PostgreSQL + API service (90/100).

EVIDENCE → E-CONSTRAINT-1 · E-CONSTRAINT-2 · E-CONSTRAINT-3 · E-CONSTRAINT-4

Action: Lock the decision with ADR-01 including context, evidence and revisit conditions.

F-3MEDIUM CONFIDENCE

EDGE / DELIVERY → Cloudflare

Combines CDN, edge compute and security at one boundary. Alternative: Vercel (76/100).

EVIDENCE → E-CONSTRAINT-1 · E-CONSTRAINT-2 · E-CONSTRAINT-3 · E-CONSTRAINT-4

Action: Lock the decision with ADR-01 including context, evidence and revisit conditions.

03

Evidence ledger

E-CONSTRAINT-1USER INPUT
productType
saas
CONF MEDIUM
E-CONSTRAINT-2USER INPUT
scale
small
CONF MEDIUM
E-CONSTRAINT-3USER INPUT
mobile
false
CONF MEDIUM
E-CONSTRAINT-4USER INPUT
realtime
false
CONF MEDIUM
E-CONSTRAINT-5USER INPUT
ai
false
CONF MEDIUM
E-CONSTRAINT-6USER INPUT
budget
low
CONF MEDIUM
E-CONSTRAINT-7USER INPUT
team
solo
CONF MEDIUM
E-CONSTRAINT-8USER INPUT
lockIn
low
CONF MEDIUM
04

Method, assumptions and boundaries

ASSUMPTIONS
  • • Fit matrix is AC Architecture Matrix v2; it is not a provider benchmark.
LIMITATIONS
  • • Latency, data residency, regulation, team skills and real traffic profile require separate validation.
AUTHORITATIVE SOURCES
AWS · AWS Well-Architected Framework

Architecture decisions are trade-offs across operational excellence, security, reliability, performance efficiency, cost optimization and sustainability; context determines priorities.

AS-OF 2026-08-09
05

Recommended next move

A01Benchmark the top two options on a representative workload.
A02Record the selection in ADR-01.
This report is decision support. Observations, derivations, user inputs and heuristics are deliberately separated.
Turn it into a technical decision with FORGEVerify it together
AC-METHODEVIDENCE → DECISION

The report is not sales decoration; it is a technical decision record.

Each report separates observations, user input, derived conclusions and heuristic assumptions. If evidence is weak, confidence drops.

Continue with FORGERequest technical scope
WHEN TO USE IT
  • Choose a technology stack without following trend lists
  • Balance operational load for a solo builder versus a larger team
  • Evaluate lock-in, scale, mobile, realtime and AI in one architecture decision
METHOD / INTERPRETATION

Why is there no single best stack?

Technology choices depend on traffic, team, budget, delivery and maintenance constraints. The same framework can be leverage for one team and operational debt for another, so the tool outputs rationale rather than a brand list.

What should the output be used for?

The recommended layers form a starting architecture. The best next step is to turn the decision into an ADR or discovery note and record the conditions that would justify changing it.

BOUNDARY

Regulatory requirements, data residency, legacy systems and enterprise-specific contracts are outside this fast model.

If this output needs to become a real technical decision, move it into the FORGE flow.

Open FORGE

AVAILABLE FOR PROJECTS · PRODUCT & SYSTEMS ARCHITECT · TAKEOVER / STABILIZE / OPERATE · WEB · ANDROID · WINDOWS · AHMET CANAL

Contact

Has your product grown faster than its system?

Send the current situation, your biggest blocker and the outcome you want. We will clarify scope together.

Availability

Open to new consulting and project-based work.

GROWTH / SIGNAL LOOP

Move from reading to a decision.

Booking, feedback and system notes in one low-friction exit.

CNV-01

Technical call

If there is a fit, move directly to a 20-minute call.

CNV-02

Decision blocker

Tell me what is still missing with one signal.