Web servernginx.conf
Migrate from NGINX
Map server blocks, locations, upstreams, health checks, timeouts, and TLS files into strict Webship TOML with an edge-first cutover.
Open the NGINX guide →Webship migration guides
Move from your current web server to Webship with a controlled cutover.
Move TLS termination, routing, health checks, static delivery, and edge policy into one Rust runtime. Every guide separates direct mappings from vendor-specific behavior that needs deliberate redesign.
Choose your current edge.
Search the major web servers, reverse proxies, caches, and application runtimes commonly replaced or moved behind Webship.
Web serverhttpd.conf
Migrate from Apache HTTP Server
Translate VirtualHost, ProxyPass, TLS, timeout, and upstream behavior into strict Webship TOML, then retire Apache edge listeners in controlled stages.
Open the Apache HTTP Server guide →Web serverCaddyfile
Migrate from Caddy
Convert Caddyfile site addresses, matchers, reverse_proxy targets, health probes, and certificates into explicit, validated Webship configuration.
Open the Caddy guide →Reverse proxyhaproxy.cfg
Migrate from HAProxy
Move HTTP frontends, backends, health checks, balancing, timeouts, and certificate handling into Webship while preserving a fast rollback path.
Open the HAProxy guide →Reverse proxyenvoy.yaml
Migrate from Envoy
Map listeners, virtual hosts, routes, clusters, endpoints, health checks, timeouts, and downstream TLS into a smaller Webship edge configuration.
Open the Envoy guide →Reverse proxytraefik.yaml
Migrate from Traefik
Translate entry points, routers, rules, services, health checks, middlewares, and TLS into stable Webship routes and policies.
Open the Traefik guide →Web serverlighttpd.conf
Migrate from Lighttpd
Translate host conditions, proxy targets, document roots, TLS files, and listener settings into Webship routes or sites.
Open the Lighttpd guide →Web serverweb.config
Migrate from Microsoft IIS
Replace IIS bindings, ARR proxy rules, URL Rewrite routing, and edge TLS with Webship while keeping Windows application dependencies behind it.
Open the Microsoft IIS guide →Web serverWebAdmin / virtual host
Migrate from LiteSpeed / OpenLiteSpeed
Convert virtual hosts, listeners, external applications, proxy contexts, static roots, and certificates into explicit Webship sites and routes.
Open the LiteSpeed / OpenLiteSpeed guide →Web servernginx.conf + Lua
Migrate from OpenResty
Move standard NGINX edge behavior into Webship while isolating Lua application logic for an explicit retain-or-rewrite decision.
Open the OpenResty guide →HTTP cacheVCL
Migrate from Varnish Cache
Move standard backend routing and bounded cache policy into Webship while treating custom VCL behavior as a measured redesign, not a search-and-replace conversion.
Open the Varnish Cache guide →Reverse proxyRust + YAML
Migrate from Pingora
Replace a custom Pingora edge service with declarative Webship routes where standard TLS, proxying, health, policy, and observability are sufficient.
Open the Pingora guide →Application serverTypeScript
Migrate from Bun.serve
Separate application code from edge duties: retain Bun as the origin while Webship takes over TLS, static delivery, HTTP/3, protection, and request routing.
Open the Bun.serve guide →