TECH_STACK.json
Every tool earns its place. No hype-driven choices — each one is selected for reliability, composability, and production-readiness.
§ 01 // core backend
python · php · fastapi · trioPrimary language for all backend, AI, and automation work. Chosen for ecosystem depth and LLM tooling maturity.
primaryFor low-level performance-critical components where Python's overhead is unacceptable.
selectivePlain PHP, without a framework.
selectiveFastAPI for all async API surfaces. Pydantic for runtime validation and schema generation. Uvicorn + Gunicorn for production serving with worker management.
SQLAlchemy 2.x with async support as the ORM layer. Alembic for all schema migrations — never manual SQL changes in production.
§ 02 // data layer
postgres · mongodb · polars · elasticsearchTransient state, session caching, rate limiting, pub/sub.
Reliable async job queuing and inter-service messaging. Kafka for high-throughput event streaming.
Airbyte for reliable data replication. Feast for feature storage and serving in ML pipelines. NumPy and Polars for fast numeric and tabular processing.
pgvector for PostgreSQL-native RAG. Qdrant and Pinecone for production vector search. FAISS for local/offline similarity. Milvus for large-scale deployments. Elasticsearch for full-text search.
For knowledge graphs, relationship-heavy data models, and Cognee-style pipelines where relational models fall short.
§ 03 // AI / LLM stack
deepseek · gpt-oss · elevenlabs · openmontageSelf-hosted LLM inference for privacy-sensitive workloads and offline environments.
Stateful, graph-based multi-agent orchestration.
Type-safe agent construction with Pydantic validation.
Multi-agent collaboration and role-based crews.
Structured output extraction and schema-bound generation.
§ 04 // agentic development
Opencode · Claude Code · hyperflowAn internal tool being developed on top of the OpenCode ecosystem. Manages workflow state, agent coordination, and project automation at scale.
.hyperflow/state.json as persistent coordination layer
Multi-agent task routing and skill delegation
Extensible via .opencode/plugins directory
Project-level command and task automation
§ 05 // infrastructure & deployment
docker · antel · runpod · apacheAll services containerised. Compose for local dev and simple deployments. Every project ships with a production-ready Dockerfile.
Lightweight global deployment for small to mid-scale workloads. Antel Datacenter for hosting in Uruguay.
Caddy for automatic TLS and simple reverse proxying. nginx for high-performance static serving. Apache for classic web serving, including PHP sites. WireGuard for internal service mesh and private networking.
§ 06 // observability & operations
sentry · langfuse · grafana · otelReal-time error capture, stack traces, and alerting. Every production service ships with Sentry integrated from day one.
Prometheus for metric scraping and alerting rules. Grafana for operational dashboards and SLA visibility. Datadog for hosted APM when managed observability is preferred.
Structured logging and distributed tracing via OpenTelemetry for cross-service visibility.
§ 07 // frontend & interfaces
react · next.js · htmx · expoServer-rendered dashboards and admin panels. HTMX for interactivity without a JS build pipeline. SQLAdmin for database admin interfaces.
React for component-driven interfaces. Next.js for full-stack apps requiring SSR, routing, and API routes in one framework.
Cross-platform mobile via React Native with Expo for managed workflow, OTA updates, and native module access.
Custom operational cockpits for business monitoring. Tailored to the data model, not a generic BI tool.
§ 08 // automation & integrations
n8n · scrapy · browser use · playwrightn8n for visual workflow automation. Self-hosted SearXNG for private web search. Browser automation (Playwright, Selenium, Browser Use), Scrapy crawlers and HTML parsing for data extraction pipelines, with pandas to clean and reshape the results.
§ 09 // documentation & knowledge
obsidian · hugo · neo4j · markdownObsidian as the primary knowledge base with Dataview for dynamic queries across notes. Linked thinking over flat documents.
Hugo for fast static site generation. Cloudflare for edge delivery and zero-config SSL on public-facing documentation.
Every system ships with operational runbooks committed alongside the codebase.
§ 10 // security & access
zitadel · wireguard · cloudflare · oauthAll analytics queries go through a registered registry — no ad-hoc SQL access in production.
§ 11 // selection principles
No tools in production that haven't been run under real load. Hype-driven choices cause post-launch failures.
Each tool does one thing well and integrates cleanly. No monolithic platforms that lock you into a vendor.
Every tool chosen can be operated by your team after handoff. No dependency on proprietary tooling I control.
Kubernetes only when needed. SQLite when Postgres is overkill. The stack fits the problem, not the résumé.
Have a problem that fits
this stack?
Send a short brief — what you're building, what's broken, and what you've already tried. I'll respond within 48 hours.