What you can actually build on the platform, explained end to end: the code, the commands, and the bill at the end.
A cold function answers in two seconds; waking a database takes fourteen. Instead of making the visitor wait, split the work across two functions and fire the wake-up on first paint. A playable quiz is the demo, and it publishes its own measurements.
Read the article →An assistant writes the handler, then you do the copying, pasting and rerunning. MCP removes that round trip: one command to connect Claude Code, an OAuth flow with no API key, and an agent that closes the deploy–call–read-logs–fix loop itself. Including what it never sees, and what it costs.
Read the article →An artifact shows an idea in ten seconds, then stays inside the conversation. A function serves the same HTML page, with a URL of your own, a private SQLite database, and four ways to choose who may open it: API key, presigned URL, public, custom domain.
Read the article →A function is stateless, and that's where half of all projects stop. Here's the other route in full: a database that sleeps when nobody queries it, a schema laid down properly, and stock kept as a ledger instead of a counter two writes can clobber.
Read the article →A job that runs once a day doesn't need a server that runs all day. Deploy a function, attach a cron expression, and look at what it actually costs: the seconds it executes, and nothing else.
Read the article →The first article on this blog, and the only one that isn't a tutorial. What we're trying to make possible for people who are neither infra devs nor ops, why the bill can't run away, what AI agents change, and what we'd like to add next.
Read the article →