How Klaviyo shipped 356 internal apps in two weeks on Vercel
Source
vercel.com
Author
Susan Aziz
Date
Context
Klaviyo made employee-built software easier to deploy by putting infrastructure and access defaults inside a shared pipeline. Vercel'scustomer account reports that 512 employees deployed 356 apps in the program's first two weeks. Its K:Forge pipeline turns a plain-language request into an app, connects data and applies company access settings.
According to the account, apps default to company sign-in, database connections use a private network path, and public deployment requires an exception. Larger builds still receive platform-team refinement and safety review. The organizational change is that shared infrastructure handles recurring deployment decisions while employees develop tools for their own work.
Key takeaways · AI-distilled
In this Vercel customer story, 512 of Klaviyo's 2,000+ employees deployed 356 apps in the first two weeks of a citizen-developer program, 196 of them full-stack apps with their own databases, built by teams including legal, marketing, and HR.
Klaviyo chose guardrailsThe checks around a model that block bad inputs and outputs — filters, validators, and permission rules the model itself can't override.Full definition → over restrictions: every app is private and SSO-gated through Okta, sensitive env vars are set at the team level, GitHub security settings are inherited, and Wiz scans every project into its SIEM. Public deployment is granted case by case.
Vercel Secure Compute gives deployments a private network path into Klaviyo's own infrastructure, so apps read and write company databases without traffic crossing the public internet. Klaviyo says this is what made bring-your-own-database workable.
Klaviyo's in-house K:Forge pipeline, built on the Vercel SDK, turns a plain-language request from Slack, Claude, or Cursor into a GitHub repo and a deployed, SSO-gated app in under three minutes. For bigger builds, the platform team finishes the last 20% and reviews safety.
Terms in this piece · Glossary
guardrails — The checks around a model that block bad inputs and outputs — filters, validators, and permission rules the model itself can't override.
