How Klaviyo shipped 356 internal apps in two weeks on Vercel
512 builders. 356 apps. Two weeks. Klaviyo just showed how to scale internal development without breaking security.
Why it matters
Klaviyo's citizen-developer platform on Vercel demonstrates a concrete model for scaling app delivery across a large organization while maintaining security defaults—no builder configuration required. The 1-in-5 employee participation rate and shift from platform team as bottleneck to finishing touch is operationally significant for enterprises considering similar internal-app strategies.
The key facts
11 to know512 of 2,000+ Klaviyo employees deployed 356 apps in two weeks
196 of 356 apps were full-stack with their own databases
Apps built by legal, marketing, and HR—non-engineering teams
Idea-to-live deployment: 3 minutes
Every app ships SSO-gated and private by default via Okta + Vercel Passport
K:Forge pipeline built on Vercel SDK; handles GitHub repo creation, deployment, Secure Compute data connection, and security defaults
Citizen developers take apps ~80% of the way; platform team handles final 20% safety review
Private network path into Klaviyo databases via Vercel Secure Compute and Enterprise Managed Users—no public internet traffic
Wiz scans every project; findings feed Klaviyo's SIEM
Public deployment granted case-by-case (e.g., sales microsites vs. internal tools)
One in five employees has shipped an app so far; team targeting higher participation
Go to the source
Vercel Blogvercel.com
Publisher excerpt: Klaviyo on Vercel Implementing safeguards across the stack Built a platform for shipping internal apps 512 builders and 356 live apps in two weeks Every app ships SSO-gated and private by default Builders go from idea to live app in 3 minutes Apps are private and SSO-gated through Okta Sensitive…