Use cases
What people actually build on nvoke.
nvoke is not a replacement for a backend — it is a place to host the small, sharp pieces of code that do not belong in one. Here are the workloads we see most often.
The shape of a good nvoke workload
The workloads that feel best on nvoke share a few properties. They are small: a few dozen lines of code, not a few thousand. They are stateless: the function does its job, returns, and is done — any state lives in a database or an upstream API. They are bursty: a webhook that fires unpredictably, a cron job that runs once an hour, an LLM agent that calls a tool when it decides to.
If your workload needs a long-running process, a WebSocket server, or tens of gigabytes of memory, nvoke is the wrong tool. For the 80% of code that is just small glue between services, it is usually the right one.
Pick a use case and ship it.
Every use case below links to a writeup with a working example. Copy, adapt, deploy.