Sources and coverage.
Stack Menu is built for your own agent to read and use during an application conversation. This page describes the research available to it.
Covered stacks and use cases
- Phoenix + LiveView
Connected browser products and portals; Real-time collaboration interfaces; JSON APIs for native clients; Durable application background work.
- Next.js
Authenticated web products; Server-rendered React interfaces; Browser applications with owned APIs and relational data.
- React + Vite
Interactive dashboards; API-backed browser tools; Client-rendered applications.
- Rails + Hotwire
SaaS; Business CRUD; Collaboration and workflow products.
- Laravel + Livewire
SaaS; Administrative and business applications; Server-driven interactive products.
- Django
CRUD-heavy SaaS; Internal products and admin tools; Server-rendered business applications.
- Go service
APIs; control planes; concurrent network services; background workers.
- Rust service
Native network services; resource-sensitive APIs; services sharing a Rust core.
- FastAPI
Typed JSON APIs; Integration services; HTTP endpoints for model or worker products.
- Go CLI + TUI
Shipped command-line products; infrastructure administration tools; terminal dashboards.
- Rust CLI + TUI
Fast native developer tools; parsers and analyzers; shipped terminal applications.
- Python automation + AI
Reusable automation scripts; Scheduled imports and transformations; Model/tool orchestration workers.
- Swift + SwiftUI
iPhone and iPad products; Native Apple integrations; Accessible mobile clients for a shared service.
- Kotlin + Compose
Android phones, tablets and foldables; Native Android integrations; Accessible mobile clients for a shared service.
Stack Menu is a reference for choosing an application stack and building with it. It provides 14 curated profiles with tool choices, architecture, working practices and migration guidance.
The original tool research is dated 10 October 2026; architecture and transition research is dated 11 October. Core framework guidance and existing source availability were rechecked on 13 October. Read the check scope and corrections. Setup recipes, complete dependency combinations and application migrations need qualification in the actual project. There is no measured cross-stack ranking.
Human pages, Markdown and JSON derive from the same records. The routing endpoint filters explicit requirements; the visiting agent reasons about the product.
Elixir Menu remains the original editorial owner of its extended reference. Copyright 2026 Optimum Tech, LLC, used under Apache 2.0; original notice. IBM Plex font licenses are retained with the files.