Use casesWeb apps

Server-rendered SaaS apps

webkit gives you auto-escaping templates, signed sessions, and security middleware on top of std.web - one language from HTTP handler to HTML.

The problem

Server-rendered SaaS still wins for admin panels, billing portals, and anything SEO matters for. Teams reach for Rails or Django, then add a Python AI script beside it for the one smart feature - two runtimes, two deploy pipelines, two places secrets leak.

Why Ecko

webkit batteries
Auto-escaping templates, signed cookies, session helpers, and CORS/security middleware. The package docs describe it as SaaS web-app batteries - which is the shape most products need.
std.web router
Routes with :params, middleware chains, and traversal-safe static mounts. GET routes answer HEAD automatically for health checks.
ai in the handler
Call ai inside the same request handler that renders the page. No internal HTTP hop to a separate inference service for simple flows.

In practice

app.ecko
import std.web
import webkit

routes = [
  { method: "GET", path: "/dashboard", handler: dashboard },
]

Further reading

Try it on your workload.