Founder & Engineer

Alex K.

I build backend systems, email infrastructure, and privacy-first products. VanishInbox started with a personal frustration: one free-trial sign-up buried my inbox in spam, and the obvious fix — a disposable address — was far more friction than it had any reason to be.

VanishInbox runs on Cloudflare Workers, Cloudflare Email Routing, and Redis. Emails are deleted after 10 minutes at the infrastructure level: no manual purge, no soft-delete flag, no trace. No account required, no PII stored.

@Vanish_Inbox AlexKilsner LinkedIn About VanishInbox →

Areas of Expertise

Eight+ years building production systems across these disciplines

⚙️

Backend Infrastructure

I've designed and run distributed backend systems for high-throughput, low-latency workloads at the edge. My focus is serverless architectures and Cloudflare Workers, with particular attention to cold-start latency: VanishInbox's inbox endpoints respond in under 100 ms under real traffic.

✉️

Email Routing & Delivery

I built the email pipeline that powers VanishInbox: catch-all domain routing via Cloudflare Email Routing, MIME parsing in a Worker, structured storage in Redis with automatic TTL expiry, and sandboxed HTML rendering to neutralise tracking pixels and malicious scripts.

🔒

Privacy Engineering

I build systems where privacy is a hard constraint, not a setting. VanishInbox retains no PII, logs no IPs, and runs no behavioural analytics on user content. GDPR data-minimisation lives at the infrastructure layer here, not in a policy document.

🛠️

Developer Tooling

I've built developer-facing products and internal tooling from API design through to CLI utilities. My stack is Next.js, TypeScript, and Tailwind. I have a strong bias toward boring, maintainable solutions over clever abstractions.

☁️

Edge & Serverless

I run production workloads on Cloudflare Pages, Workers, and KV. I designed VanishInbox specifically for edge deployment: no origin server, globally distributed, no cold-start penalty on inbox polling.

📈

SEO & Growth Engineering

I work at the intersection of technical SEO and product engineering: structured data, Core Web Vitals, crawl budget, and programmatic content. I built VanishInbox's organic growth from zero to consistent non-branded keyword rankings.

Experience Timeline

How I got to building what I build

2016–2018
Early backend work
I started building server-side systems professionally: REST APIs, relational databases, and the fundamentals of distributed architecture. Early on I decided to understand how infrastructure actually works rather than treat it as something you configure and forget.
2018–2021
Email infrastructure
I spent three years deep in email delivery: SPF/DKIM/DMARC configuration, deliverability tuning, inbound routing pipelines, and large-scale parsing. I read the RFCs most engineers skip, and it showed up in the systems I shipped.
2021–2023
Privacy-first product design
I moved toward building products where privacy shaped the architecture from day one. I studied GDPR implementation patterns and zero-knowledge system design, and learned the difference between systems that are genuinely private and systems that are merely compliant.
2024
Founded VanishInbox
I combined my email and privacy background to build VanishInbox: a free, instant, no-account disposable email service. I chose Cloudflare Workers and Redis so that email deletion happens at the infrastructure level automatically, not as a cron job.
2025–now
Growing the platform
I'm expanding VanishInbox with new domains, i18n support, and a content strategy for privacy-conscious users. A Pro tier with extended retention and custom aliases is in progress. The free tier stays free.