nvoke

Feature

Every function is a real HTTPS URL.

You write one function. nvoke gives you a signed, public HTTPS endpoint for it in seconds. No load balancer, no gateway, no YAML.

Open app All features
export default async function (req) {
  const { name = "world" } = req.body;
  return { message: `Hello, ${name}!` };
}
Write this. POST to your endpoint. Get JSON back.

How endpoints work on nvoke

A function in nvoke is a default-exported async function that takes a request and returns a value. There is no handler signature to memorize, no framework to import, no SDK to install. The platform handles the HTTP layer so you can focus on what the function does.

When you save a function, we publish it to a URL like https://app.nvoke.run/api/invoke/your-function. The URL is stable — it stays the same across deploys, versions, and rollbacks. Put it in a webhook field, a cron runner, an LLM tool manifest, or a cURL command.

Requests hit a warm Node.js worker pool. Typical time-to-first-byte for a small function is under 100 ms. There are no cold starts in the usual sense: workers are kept ready for functions that receive traffic, and the first invocation of a rarely-called function warms up in roughly a second.

Authentication and public endpoints

By default, every endpoint requires an x-api-key header. The key lives in the app and is rotated with a single click — old keys keep working for 24 hours so you can roll without a window of broken callers.

For webhooks that cannot attach custom headers (Stripe, GitHub, Slack), mark the function as public. nvoke will still capture the request, but anyone can call it; you are expected to verify signatures inside the function body.

Get a URL in 30 seconds.

Sign up, paste a function, hit save. The endpoint is live before the page finishes reloading.

Open app Read the docs