ForthWrite's answer

Next.js, React, Supabase, Anthropic Claude, OpenAI, Stripe, Vercel, Chrome Extensions API

Spanlens's answer:

TypeScript across the stack. The dashboard is Next.js, the API and proxy run on Hono, and data is split between Supabase Postgres for accounts and relational data and ClickHouse for request logs, which grow fast. The repo is a pnpm monorepo that also holds the JavaScript and Python SDKs, a CLI, and an MCP server. Self-hosting runs on Docker Compose, and OpenTelemetry traces can be ingested over OTLP.

ForthWrite's answer

ForthWrite learns your writing style from your actual sent mail, not a generic prompt. Every draft sounds like you wrote it because it was trained on how you actually write. It also auto-drafts replies before you open your inbox, so your email is partially handled before your day starts.

Spanlens's answer:

The entire product is MIT licensed, including the dashboard, evals, and prompt A/B testing. There is no separate enterprise edition. Everything ships in one repo you can run with a single Docker Compose file. Integration is one line: you change the baseURL on your OpenAI, Anthropic, or Gemini client, and every call gets logged with its full body, token counts, cost, and latency. A few things that are usually paid add-ons come built in, like agent traces with a critical path view, A/B tests that use Welch's t-test to tell you whether a difference is real, and a recommender that flags cheaper models based on the traffic you actually send.

ForthWrite's answer

Most AI email tools give you a blank box and a "write for me" button. ForthWrite builds a voice profile from your sent history and gets more accurate with every draft you edit or send. Unlike ChatGPT or Gemini, it works natively inside Gmail and Outlook with no copy-paste. Unlike Lavender, it writes the draft, not just scores it.

Spanlens's answer:

Mostly because of where the market went. Helicone was acquired, LangSmith is closed source, and self-hosting Langfuse takes real setup work. Spanlens fills the gap those tools left: setup in about five minutes, one Docker Compose file if you want the data on your own servers, and no feature gating between free and paid tiers. To be fair, if you need SOC 2 reports and enterprise support today, the bigger platforms are ahead. If you want request logs, costs, and traces without adopting a heavy platform, that is what Spanlens was built for.

ForthWrite's answer

Professionals who send high volumes of relationship-critical email and cannot afford to sound generic: lawyers, financial advisors, recruiters, account executives, consultants, and founders managing their own inbox.

Spanlens's answer:

Developers who ship LLM features in production apps. The typical user is a solo developer or a small team that added OpenAI or Anthropic calls to their product and now has no clear picture of what those calls cost or why some are slow. Agent builders are the second group, since multi-step workflows are hard to debug without traces. It is a developer tool through and through: if you don't touch code, you won't get much out of it.

ForthWrite's answer

Built out of frustration with AI writing tools that produce text that sounds nothing like the person sending it, and as a way to handle large amounts of daily email. The core insight was that your sent mail is the best training data you already have, and no tool was using it.

Spanlens's answer:

I was building LLM apps on the side and kept pasting token counts into a spreadsheet to figure out what each feature cost me. The tools I tried were either acquired mid-migration, closed source, or heavier to self-host than the app I was trying to monitor. So in April 2026 I started building the tool I actually wanted: change one line, see every request. It launched in June 2026, and the whole codebase went up on GitHub under MIT from day one.

Spanlens's answer:

We don't publish customer names yet. Spanlens launched in June 2026, and most users so far are indie developers and small AI teams.