How functions-as-a-service shows up in this material In the episode with Steve Krouse, functions-as-a-service is Val Town's core product: a platform that runs your backend code for you, so you never start or deploy a server yourself [^ebfee90b-4a43-55ab-9be2-5070c4aaefb0]. The system prompt behind the AI assistant Townie tells the model that code runs in Deno JavaScript and that it “never needs to start or deploy a server” — the platform handles that. It's what lets a single prompt produce a working app with a client-and-server flow, like the question generator that calls OpenAI from the server and returns results to the client. Why it's strategic Krouse positions functions-as-a-service as Val Town's differentiator: backend compute that LLM companies won't want to build themselves, making partnership more likely than competition. It's also why he rejected the pivot to a “Shopify for SaaS apps” full-stack platform — replacing the two dozen tools of a mature engineering org would make a mediocre version of everything, while doing fewer things sharply lets Val Town pour its innovation into making functions-as-a-service the fastest, most pleasurable platform it can be, copycatting the best UI patterns from Cursor, Anthropic, and Bolt. <KeyPoint>Functions-as-a-service runs backend code without the user managing servers or deploys.</KeyPoint><KeyPoint>It's what makes Val Town's disposable software — apps built from a single prompt — actually work end to end.</KeyPoint><KeyPoint>Krouse treats it as the strategic moat: fewer things done sharply, backend compute LLM companies won't build themselves.</KeyPoint>