Home › Services › Runtimes

Runtimes: 17 solutions compared

Which Runtimes tools can you self-host, run on a Mac or connect to? FrontierStack's catalogue covers 17 Runtimes options: .NET (ASP.NET Core), Astro, celld (Durable Objects), code-server, Deno, Fermyon Spin and others. For 17 of them FrontierStack installs the service on a Mac or server, or connects to one you already run, and checks status, ports and certificates where they apply.

NameTypeWhat FrontierStack does
.NET (ASP.NET Core)Self-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
AstroSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
celld (Durable Objects)Self-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
code-serverSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
DenoSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Fermyon SpinSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
MojoSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Next.jsSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Nuxt (Vue)Self-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Solid (SolidJS)Self-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Supabase Edge FunctionsSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
SvelteKit (Svelte)Self-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
Tailwind CSSSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
wasmCloudSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
WasmEdgeSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
WasmerSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply
WasmtimeSelf-hosted or connectedInstall or connect; status, ports and certificate checks where they apply

.NET (ASP.NET Core)

Run ASP.NET Core & Blazor apps (Kestrel)

The .NET runtime hosts ASP.NET Core apps; including Blazor Server / Blazor Web Apps; via its built-in Kestrel web server, by default on :5000. brew install dotnet, then dotnet publish your app and run the DLL (dotnet MyApp.dll) under launchd/systemd, usually behind Apache or nginx as a reverse proxy. Blazor WebAssembly standalone needs none of this; it publishes to static files any web server here can serve.

Install or connect .NET (ASP.NET Core); then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Astro

Content-first framework; zero JS by default; popular headless-WordPress front end

Astro is a web framework built for content sites: it renders to HTML at build time and ships no JavaScript unless you ask for it, hydrating only the components you mark as interactive ("islands"). It takes components from React, Vue, Svelte or its own syntax, so a team isn't locked to one UI library. npm create astro@latest; the dev server runs on :4321, astro build emits a static site any web server here serves directly, and the Node adapter produces a real SSR server you host behind Apache/Nginx and monitor here like any other service. Its most common role next to this app is as a headless WordPress front end: WordPress stays the editing back end and Astro pulls posts through the REST API (/wp-json/wp/v2) or WPGraphQL at build time, serving static HTML. That removes PHP and the database from the request path entirely; the reason it comes up in WordPress speed discussions. Note it is unrelated to Astra, the WordPress theme with a similar name.

Install or connect Astro; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

celld (Durable Objects)

Self-hosted Cloudflare Workers & Durable Objects (Deno)

celld, from the Deno team, runs Cloudflare Workers and Durable Objects code unchanged on your own machines; each Durable Object ("cell") gets its own SQLite database, its writes are durable in an S3-compatible, Google Cloud Storage or Azure bucket before they are acknowledged, and nodes coordinate through that bucket alone, with no consensus service. It also covers KV, Queues, D1, R2, Workflows, Cron Triggers and static assets from your existing wrangler.json. celld dev serves a project locally on :9876; a fleet node runs celld --bucket s3://… --listen 0.0.0.0:8080 --internal-listen <private IP>:8081. FrontierStack lists local celld processes, starts celld dev, and reads each node's operator /state (owned and resident cells, WebSockets, memory pressure, restore backlog) and health route; nodes show in Alerts and as tiles in the Server Activity window. Keep the internal listener on a private network or Tailscale: its operator routes have no authentication.

Install or connect celld (Durable Objects); then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

code-server

VS Code in the browser (self-hosted)

code-server runs VS Code on a server and serves it in your browser; full editor + extensions from anywhere. brew install code-server or Docker (codercom/code-server); web UI on :8080.

Install or connect code-server; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Deno

Secure JavaScript/TypeScript runtime with npm support

Deno runs JavaScript and TypeScript with no build step; permissions are off by default (--allow-net, --allow-read…), npm packages and node_modules work, and the toolchain is built in: formatter, linter, test runner, deno compile for single-file binaries and deno serve for HTTP servers (default :8000). brew install deno. Servers started with deno serve or deno run on this Mac are listed below with their ports so you can open or stop them. Its hosted platform, Deno Deploy, is under Hosting, and celld (Deno's self-hosted runtime for Cloudflare Workers and Durable Objects) is next to it here.

Install or connect Deno; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

Fermyon Spin

Serverless WebAssembly apps & HTTP microservices

Spin (Fermyon) builds and serves event-driven WebAssembly apps; write handlers in Rust, JS/TS, Python or Go, spin build compiles them to Wasm components, and spin up serves them locally on :3000 with near-zero cold starts. Includes key-value storage, SQLite and cron triggers; deploy the same app to Fermyon Cloud or SpinKube on Kubernetes. (Its spin CLI shares a name with Spinnaker's; detection here can't tell them apart.)

Install or connect Fermyon Spin; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Mojo

Modular's AI systems language (Python-family syntax)

Mojo is Modular's systems language for AI; Python-family syntax with C-class performance and direct control over SIMD, memory and GPU kernels. It reached 1.0 and is open source under Apache 2.0 with LLVM exceptions, so compiled binaries and commercial use carry no licence obligations. It installs on its own, like any Python or Conda package: uv pip install mojo (or uv add mojo), pip install mojo, or with pixi; pixi init hello-world -c https://conda.modular.com/max/ -c conda-forge then pixi add mojo. Run a file with mojo hello.mojo, or build a binary with mojo build. Modular recommends pixi for environment reliability and uv for the tightest Python interop; the older magic CLI is retired, its work having been upstreamed into pixi. For serving models with the wider Modular platform, see Modular MAX under AI.

Install or connect Mojo; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

Next.js

React framework served by a Node process (SSR/SSG)

Next.js is the most widely used React framework; server-side rendering, static generation, the App Router, API routes and React Server Components. It's the answer to "serve a React app": React itself is a browser library with nothing to run server-side, but a Next.js app runs as a real Node process (next build then next start, default :3000) you host behind Apache/Nginx as a reverse proxy and monitor here like any other service. npm install next; run under launchd/systemd or in Docker. (For a purely static export, next export produces files any web server here serves directly.)

Install or connect Next.js; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

Nuxt (Vue)

Vue framework served by a Node process (SSR/SSG)

Nuxt is the official meta-framework for Vue; server-side rendering, static generation, filesystem routing, auto-imports and a server/API layer (Nitro). Vue itself is a browser UI library with nothing to run server-side, so Nuxt is how you "serve a Vue app": npm create nuxt, the dev server runs on :3000, and nuxt build produces a real Node server (node .output/server/index.mjs, :3000) you host behind Apache/Nginx and monitor here. nuxt generate exports a static site any web server serves directly.

Install or connect Nuxt (Vue); then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Solid (SolidJS)

Fine-grained reactive UI framework; SolidStart serves it as a Node process

Solid is a reactive UI framework with JSX like React's but no virtual DOM; components run once and fine-grained signals update the DOM directly, which is why it tops UI benchmarks. Solid 2.0 (RC) makes async a first-class part of that reactivity: promises can be used directly inside the graph, with reworked Suspense and deterministic batching (npm i solid-js@rc @solidjs/web@rc to try it). Start a project with npm create solid@latest. To *serve* a Solid app there is SolidStart; SSR, streaming, file routing and server functions. SolidStart v2 is stable on Vite 8 + Rolldown (needs Node 24+): the dev server runs on :3000 and vite build produces a real Node server you host behind Apache/Nginx and monitor here like any other service; or a purely static build any web server serves directly.

Install or connect Solid (SolidJS); then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

Supabase Edge Functions

Deno serverless functions on the edge

Supabase Edge Functions are TypeScript/Deno serverless functions deployed globally, with access to your Supabase project. Develop them locally with the Supabase CLI (supabase functions serve) and deploy with supabase functions deploy. Manage the local stack from the Supabase pane.

Install or connect Supabase Edge Functions; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

SvelteKit (Svelte)

Svelte app framework served by a Node process (SSR/SSG)

SvelteKit is the official application framework for Svelte; server-side rendering, static generation, filesystem routing and form actions. Svelte itself is a compile-time UI library with nothing to run server-side, so this is the way to "serve a Svelte app": npm create svelte, then the Vite dev server runs on :5173, and vite build with the Node adapter produces a real Node server (node build, default :3000) you host behind Apache/Nginx and monitor here. With the static adapter it exports plain files any web server serves directly.

Install or connect SvelteKit (Svelte); then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Tailwind CSS

Utility-first CSS; standalone build CLI (no Node)

Tailwind CSS is the utility-first CSS framework: you compose styles from small classes in your markup, and its build step scans your templates and emits a minimal stylesheet of only the classes you used. The standalone CLI is a self-contained binary; no Node or npm; so it fits server-rendered sites (PHP, Python, plain HTML) served from the Websites pane: brew install tailwindcss, then tailwindcss -i in.css -o out.css --watch rebuilds the CSS as you edit, and --minify produces the production file. It's a build tool, not a server; detected by its binary, with no port or daemon to monitor (the compiled CSS is a static asset Apache/Nginx serves like any other).

Install or connect Tailwind CSS; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply. Full page →

wasmCloud

Distributed WebAssembly platform (CNCF)

wasmCloud (CNCF) runs WebAssembly components as distributed applications; hosts form a lattice over NATS (:4222), capability providers supply HTTP/key-value/messaging, and apps declare what they need (WADM manifests). Install the wash CLI (brew install wasmcloud/wasmcloud/wash), start a local host with wash up, and open the washboard UI with wash ui (:3030). The Wasm-native answer to an orchestrator: scale and reschedule components across machines without containers.

Install or connect wasmCloud; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

WasmEdge

Lightweight WASM runtime for cloud/edge & AI (CNCF)

WasmEdge (CNCF) is a lightweight, fast WebAssembly runtime aimed at cloud-native, edge and AI workloads; WASI plus extensions for networking sockets and WASI-NN inference (GGML/llama.cpp backends), and it plugs into container tooling (Docker + containerd can run .wasm images via the crun/runwasi shims). Run modules with wasmedge app.wasm.

Install or connect WasmEdge; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Wasmer

WebAssembly runtime with a package registry

Wasmer runs WebAssembly anywhere; multiple compiler backends (Cranelift/LLVM/Singlepass), WASI plus its extended WASIX (threads, sockets, fork), and a package registry so wasmer run python/python just works. Embed via Rust/C/Go/PHP/Ruby SDKs, or deploy the same modules to Wasmer Edge.

Install or connect Wasmer; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

Wasmtime

Bytecode Alliance WebAssembly runtime (WASI)

Wasmtime is the Bytecode Alliance's reference WebAssembly runtime; fast Cranelift JIT/AOT, first-class WASI (files, sockets, clocks granted explicitly) and the component model. Run a module with wasmtime run app.wasm, or embed it via the Rust/C/Python/.NET/Go APIs. The safe default for running untrusted or portable code server-side.

Install or connect Wasmtime; then check its status, ports and certificate from FrontierStack. The same screen links to firewall checks and backups where they apply.

All service genres →

Run it from your Mac.

FrontierStack installs, monitors and secures services on this Mac and on linked servers; and keeps your passwords and keys out of any AI's sight.

Download FrontierStack

Apple notarized · Safe & secure · macOS 13 Ventura+