chunktort
Streaming millions of geological data points to the browser while keeping it interactive is a real performance architecture problem — the kind where how you structure your data pipeline matters as much as the rendering layer.
Relevant: Chatbot Widget SaaS — Next.js 15 + TypeScript + Supabase + pgvector + Shadow DOM widget, real-time WebSocket streaming, full auth + Stripe billing. Built the whole stack as first engineer. GitHub: github.com/ChunkyTortoise/chatbot-widget. Also: AI Dashboard (live at ai-dashboard-rust.vercel.app) — Next.js 15, shadcn/ui, real-time Recharts, Anthropic streaming.
Stack match: TypeScript, Next.js, Supabase, Python, Vercel — AI-native workflow (Claude + Cursor daily). Available within 1 week, 35-40 hrs/week.
Cayman | [email protected] | github.com/ChunkyTortoise
Building reliable AI decisioning for fraud and compliance is a different challenge from most LLM work — the output needs to be auditable and the false-positive cost is real money.
Relevant: Jorge Real Estate AI Bots — production FastAPI + Redis + Claude pipeline, 1,700+ tests, GHL webhook integration with rate limiting, HMAC signature verification, and per-contact Redis locks to prevent race conditions. The same reliability patterns apply to risk decisioning. GitHub: github.com/ChunkyTortoise/jorge_real_estate_bots
Stack match: Python, FastAPI, Claude API, Redis, LLM agent systems — 15+ AI projects in production. Available within 1 week, 35-40 hrs/week.
Cayman | [email protected] | github.com/ChunkyTortoise
Persistent memory and context-aware agents are the hard part of personal AI — retrieval has to be fast enough to feel invisible and selective enough not to be noise.
Relevant: GraphRAG demo — entity extraction (spaCy + Claude), NetworkX DiGraph, hybrid BM25+RRF retrieval, fact-checking pipeline. Purpose-built for context that needs structure, not just semantic similarity. GitHub: github.com/ChunkyTortoise/graphrag-demo. Also: MCP Server Toolkit (PyPI published, 233 tests) — memory and context tooling for AI systems.
Stack match: Python, PostgreSQL, RAG, LLM APIs (Anthropic), pgvector — available within 1 week, 35-40 hrs/week.
Cayman | [email protected] | github.com/ChunkyTortoise
Autonomous AI agents for forensics is a hard problem — managing tool orchestration across 150+ forensic tools while hitting CJIS compliance requirements is exactly the kind of infrastructure challenge most engineers haven't touched.
Relevant: AI Workflow API — FastAPI + ARQ + Redis workflow engine, YAML-driven, 5 node types (trigger/LLM/condition/HTTP/notify), SSE streaming, 148 tests. Similar distributed orchestration pattern to what you're building. GitHub: github.com/ChunkyTortoise/ai-workflow-api
Stack match: Python, TypeScript, Next.js, Docker, Redis — I use Claude as part of my development workflow daily and ship AI-native. Available within 1 week.
Cayman | [email protected] | github.com/ChunkyTortoise
Turning Reddit noise into structured product signals is exactly the kind of pipeline problem where RAG architecture matters — naive semantic search on raw posts misses context that entity-aware retrieval catches.
Relevant: GraphRAG demo — hybrid BM25+RRF retrieval on unstructured text, NetworkX entity graph, Claude for extraction, pgvector for embeddings. Built specifically to handle noisy real-world text. GitHub: github.com/ChunkyTortoise/graphrag-demo. Also: DocExtract AI (production, live) — async document pipeline, pgvector + Claude + ARQ worker, 234 tests. docextract-api.onrender.com
Stack match: Python, PostgreSQL, pgvector, RAG, LLM APIs (Anthropic/OpenAI) — every item in your stack is something I ship with. Available within 1 week.
Cayman | [email protected] | github.com/ChunkyTortoise
[email protected] | github.com/ChunkyTortoise
[email protected] | github.com/ChunkyTortoise
[email protected] | github.com/ChunkyTortoise
[email protected] | github.com/ChunkyTortoise
[email protected] | github.com/ChunkyTortoise
The core realization: most "orchestration" is just routing + retry + caching. Those three things don't require 47 packages or 15MB of dependencies.
What it actually is: ~15KB of Python, 2 runtime deps (httpx + pydantic). Benchmarks on 1,000 requests showed 65ms avg vs LangChain's 420ms, 3MB memory/request vs 12MB.
The part I'm most proud of: the testing layer. MockLLMClient lets you inject deterministic responses so you can test agent routing and retry logic without hitting any APIs. Hard to do that cleanly with LangChain's abstractions.
214 tests, 91% coverage. Live demo at ct-agentforge.streamlit.app if you want to try it without cloning.
Happy to go deep on any part of the architecture.
Show HN: AgentForge – Multi-LLM Orchestrator in 15KB
https://github.com/ChunkyTortoise/ai-orchestrator
I built AgentForge, a minimal multi-LLM orchestrator. Total size: ~15KB of Python code.Why? LangChain added 250ms overhead per request. I needed something simpler.Performance vs LangChain (1,000 requests): - Avg latency: 420ms -> 65ms - Memory/request: 12MB -> 3MB - Cold start: 2.5s -> 0.3s - Test time: 45s -> 3sSize: 15KB + 2 dependencies (httpx, pytest) vs LangChain's 15MB+ and 47...