Slashy tech stack

Firebase

“We chose Firebase because its authentication tooling is reliable, widely supported, and straightforward to integrate across web and mobile. It helped us ship account access without building identity infrastructure from scratch.” — the maker, Sep 2026 ↗

Supabase

“We chose Supabase because it gives Slashy a real Postgres foundation with authentication, storage, APIs, and realtime capabilities in one developer-friendly platform. It helped us move quickly without giving up SQL or control of our data model.” — the maker, Sep 2026 ↗

Temporal

“We chose Temporal because email automations, reminders, and background jobs need to survive retries, delays, and service interruptions. Durable workflows give us a much stronger foundation than stitching together fragile queues and cron jobs.” — the maker, Sep 2026 ↗

Stripe

“We chose Stripe because it makes subscriptions, payments, discounts, and billing operations dependable. Its APIs and dashboard let a small team manage a serious billing system without unnecessary complexity.” — the maker, Sep 2026 ↗

OpenAI API

“OpenAI's models are part of our multi-model architecture. We use different models for different tasks within Slashy: some optimized for speed, others for nuance. OpenAI's API reliability and breadth of capabilities made it a natural part of our stack.” — the maker, Sep 2026 ↗

“We chose OpenAI because its models and developer platform are powerful, fast, and flexible across drafting, classification, research, and agent workflows. It gives us dependable building blocks for several parts of the Slashy experience.” — the maker, Sep 2026 ↗

Claude

“We chose Claude because it is strong at understanding long, messy context and producing thoughtful, natural writing. That makes it especially useful for email workflows that depend on full threads, meeting notes, and CRM history.” — the maker, Sep 2026 ↗

Gemini API

“Gemini's long context window is genuinely useful for Slashy's inbox summarization features. When a user has a sprawling email thread or needs their whole inbox triaged at once, Gemini handles the volume without chunking hacks. It's a powerful complement to our…” — the maker, Sep 2026 ↗

Sentry

“We chose Sentry because production errors need context, not just logs. Its stack traces, release visibility, and issue grouping help us understand what broke and fix customer-facing problems quickly.” — the maker, Sep 2026 ↗

Amazon Web Services

“We chose AWS because Slashy has demanding background workloads and email-processing infrastructure that need reliable, flexible compute. Its breadth lets us run and scale specialized services without forcing everything into one deployment model.” — the maker, Sep 2026 ↗

PostHog

“We chose PostHog because analytics, funnels, and feature flags work together on the same product data. It helps us understand how people actually use Slashy and where the experience needs improvement.” — the maker, Sep 2026 ↗

OpenAI Codex

“We chose Codex because it can work directly across a large, multi-repository codebase and carry implementation through testing and verification. It helps our small team move faster on real engineering work.” — the maker, Sep 2026 ↗

Vercel

“We chose Vercel because it makes deploying and previewing modern web experiences fast. Preview deployments are especially useful for reviewing product and marketing changes before they reach customers.” — the maker, Sep 2026 ↗