Compare
hostfunc vs Deno Deploy
Deno Deploy runs TypeScript and JavaScript on a global edge network with a clean deploy story. hostfunc is higher-level: instead of shipping a server you wire up yourself, you export a single main() and get triggers, encrypted secrets, an MCP server, a forkable marketplace, and a composition lineage graph out of the box — and you can self-host it.
| Capability | hostfunc | Deno Deploy |
|---|---|---|
| Language | TypeScript-first | TypeScript / JavaScript |
| Programming model | Export one main() per function | Bring your own HTTP server / handler |
| Triggers | HTTP, cron, email, MCP — all unified | HTTP; cron via separate config |
| Agent / MCP native | Built-in MCP server | Not built-in |
| Secrets | Encrypted secrets, fetched at run time | Environment variables |
| Marketplace | Public, forkable functions | None |
| Self-host | Yes — Docker Compose | Hosted only |
| License | Open source (AGPL-3.0) | Proprietary platform |
Choose hostfunc when
- You want to ship a single function fast, without standing up a server or handler yourself.
- You want agent/MCP access and a forkable marketplace built in.
- You want one unified observability pipeline across HTTP, cron, email, and MCP triggers.
Choose Deno Deploy when
- You're already invested in the Deno ecosystem and want raw, low-level control of an edge server.
- You're deploying full applications rather than small composable functions.
- You don't need a marketplace, MCP, or self-hosting.
Ship your first function in 90 seconds
Sign in, drop in some TypeScript, hit deploy. See the pricing or browse use cases.