I'm a senior software engineer with 21+ years of production shipping experience, now focused on publishing free, MIT-licensed, plug-and-play open-source projects that real teams can drop into prod and actually use.
I work end-to-end — from schema design and worker pipelines to pixel-perfect UI. My north star is no half-finished features: if I ship it, it's tested, documented, deployable, and feels like a product.
focus: [ AI · RAG · Multi-tenant SaaS · Mobile · Telegram · Web3 ]
shipping: [ Open-source, MIT, plug-and-play, enterprise-grade ]
stack: [ Next.js · TypeScript · Postgres · pgvector · Drizzle ·
Flutter · React Native · Auth.js · Stripe · BullMQ · Ollama ]
values: [ Honest READMEs · Adversarial tests · No vendor lock-in ]ai-chatbot-saas — Open-source multi-tenant RAG chatbot platform.
Upload PDF / DOCX / XLSX / JSON / Markdown / URLs / sitemaps / Q&A pairs · pick any LLM (OpenAI · Claude · Gemini · Deepseek · Ollama) · deploy across web widget + Telegram + WhatsApp · full conversation admin · promote-to-training feedback loop.
Inspired by /now — a short, honest snapshot of current focus.
- Shipping
ai-chatbot-saas— multi-tenant RAG chatbot platform with pluggable LLM providers and web / Telegram / WhatsApp deploy targets. - Writing production-grade OSS starters — the goal is drop-in projects, not toy templates.
- Investing in honest READMEs, real tests, and reproducible builds on every repo I publish.
- 🤖 AI-grounded products — RAG, agents, embedding pipelines, LLM provider abstractions
- 📱 Mobile + web SaaS — Flutter, React Native, Next.js, end-to-end TypeScript
- 💬 Messaging bots — Telegram Mini Apps, WhatsApp Cloud API, Discord, Slack
- 🪙 Web3 / Telegram-native apps — TON, smart contracts, on-chain UX
- 🛠 Open-source infrastructure — anything where the README has to be honest and the tests have to be real
💌 Have a hard problem? Email me — I read every message.