v4.2 — 31 edge regions live
Push to Git and your functions are live in 31 regions in under 900 ms. No cluster to size, no YAML to memorise, and logs you can actually read.
Trusted by engineering teams at
01 — Platform
Routing, scaling, secrets, and observability ship in the box. You write the handler.
Requests land in the region closest to the user. Failover is automatic and takes 40 ms.
Sample latencies from a Seoul client · illustrative
Encrypted at rest, injected at cold start, never printed in logs.
Structured by default, searchable for 30 days, no query language to learn.
One request or a million — the same handler, no autoscaler to tune.
Every pull request gets its own URL with production-shaped data.
Every deploy is immutable. Roll back to any of the last 100 in 2 seconds.
02 — Speed
The runtime keeps a warm pool per region and snapshots your isolate after the first request. Most handlers never see a cold start after deploy minute one.
// no config file, no Dockerfile
export default {
async fetch(req: Request) {
const city = req.headers.get("x-webis-city");
return Response.json({
hello: city ?? "world",
region: WEBIS.region,
});
},
};03 — Workflow
STEP 01
Point us at a GitHub or GitLab repository. We detect the runtime and entry file automatically.
STEP 02
Every branch gets a preview URL. Merge to main and it promotes to production automatically.
STEP 03
Latency, errors, and logs stream into one dashboard. Alerts go to Slack or a webhook.
04 — Use cases
Rewrite HTML per visitor — locale, currency, A/B bucket — before it leaves the edge. Your origin keeps serving one cached document, so hit rates stay above 95%.
Verify tokens, enforce rate limits, and fan out to internal services from a single handler. Rejected traffic never reaches your origin or your bill.
Accept, validate, and queue provider callbacks in the nearest region. Bursts of 40k webhooks a minute land without a warm-up window.
Resize, re-encode, and watermark on first request, then cache the result at the edge forever. Your bucket stores one original per asset.
05 — Comparison
A typical container setup versus the same workload on the runtime.
| Concern | Container platform | WEBIS Runtime |
|---|---|---|
| Capacity planning | Pick instance sizes, set replica counts, tune the autoscaler | None — isolates spin per request |
| Global presence | Duplicate the stack per region, manage failover yourself | 31 regions on by default |
| Cold start | Seconds — image pull, boot, health check | 7 ms median from snapshot |
| Idle cost | Minimum replicas bill around the clock | Zero — you pay per request |
| Rollback | Re-deploy a previous tag, wait for the rollout | Two seconds, any of 100 revisions |
| Config surface | Dockerfile, manifests, ingress, HPA, secrets store | One handler file |
Illustrative comparison for a sample workload. Your numbers will differ.
06 — Ecosystem
07 — Security
Every request runs in its own V8 isolate with no shared filesystem and no ambient network access. Outbound calls go through an allowlist you control.
08 — Teams
"We deleted 4,000 lines of Terraform the week we moved. Nobody has missed it."
"Preview URLs per pull request killed our staging queue. Reviews got faster overnight."
"Our p95 in Seoul went from 340 ms to 61 ms and the bill went down. That never happens."
09 — Pricing
No seat minimums. No idle charges. Stop deploying and the bill stops.
Side projects and prototypes
$0
forever
Production workloads
$40/mo
+ $0.30 per extra million
Compliance and scale
Custom
annual agreement
10 — FAQ
TypeScript and JavaScript on the V8 isolate runtime, plus WASM modules compiled from Rust or Go. Long-running processes belong on a container platform, not here.
Per request plus CPU milliseconds actually consumed. Idle isolates cost nothing, so a quiet week costs a quiet week.
Yes. Region pinning is available on Team and Enterprise. Pin to icn1 and requests never leave Korea.
Every deploy is immutable and kept for 100 revisions. Roll back from the dashboard or the CLI in about two seconds — no rebuild required.
Handlers use the standard Request and Response objects, so the same code runs on any compliant runtime. Export your config as JSON whenever you like.
Free tier, no card, no sales call. Delete the project any time and nothing lingers.
Demo form — submissions are not sent anywhere.