Third-Party Integrations

Honeycomb connects to several third-party services to power payments, AI content generation, real-time communication, and media features. Each integration lives in a well-defined boundary — typically a server-side service file, a client-side store, or a standalone Svelte component.

Integration Map

Stripe

Payments, subscriptions, Connect onboarding, platform fees, and webhook processing. Read more

OpenAI

Text generation, text modification, and DALL-E image generation for the site builder and AI docs apps. Read more

Supabase Realtime

Postgres Changes channels, Presence tracking, typing indicators, and live message delivery. Read more

GIPHY

GIF search and picker components embedded in messaging and post creation flows. Read more

Environment Variables at a Glance

All integration keys are loaded through SvelteKit’s $env modules. Server-only secrets use $env/static/private; client-safe keys use $env/static/public.

Variable	Scope	Used By
STRIPE_SECRET_KEY	Private	Stripe SDK on the server
STRIPE_WEBHOOK_SECRET	Private	Webhook signature verification
OPENAI_API_KEY	Private	OpenAI chat and image APIs
PUBLIC_SUPABASE_URL	Public	Supabase client (Realtime, DB)
PUBLIC_GIPHY_API_KEY	Public	GIPHY search API from the browser

Caution

Never expose private keys to the client. Stripe and OpenAI calls always run through SvelteKit server routes or +page.server.ts loaders.

Architecture Principles

1. Server-side by default — Stripe and OpenAI calls happen exclusively on the server. The client only receives redirect URLs or generated content.
2. Lazy singletons — Both the Stripe and OpenAI SDK clients are instantiated once on first use to avoid cold-start overhead on unused code paths.
3. Realtime on the client — Supabase channels are created in onMount lifecycle hooks and torn down on component destroy to prevent memory leaks.
4. Graceful degradation — GIPHY components check for the presence of PUBLIC_GIPHY_API_KEY and hide the picker entirely when the key is absent.