webapp.mk
Features

Edge and security

Every site and app is reached through the edge, the load balancer in front of your realm. It serves HTTPS and blocks common attacks before they reach your code.

Edge and security

How it works

  1. Visitor
  2. Edge: HTTPS and filters
  3. Your site or app
  4. Access log, if you want one
Exploit rules

Always on

a set for each kind of resource

Transport

HTTP/2

plain HTTP redirected to HTTPS

Where it runs

Your realm

one home realm per account

Edge and security

What a realm is

The platform runs in realms. A realm is a group of machines in one place, with an edge in front, a private network and database servers of its own.

Your home realm

Your account has a home realm. New sites, apps and databases run there.

One edge in front

Each realm has one active load balancer on its public addresses. It serves every hostname of the sites and apps in that realm.

A private network

Apps and database servers on one network reach each other by name, on every machine of the realm. A database server has no public port unless you open one.

Domains point at a realm

A domain answers from the realm it points at. On managed DNS the records follow when a site or app moves to another realm.

Edge and security

How traffic is served

Set for each site and each app hostname, and changed at any time.

HTTPS first

With HTTPS on, plain HTTP is redirected to HTTPS and HTTP/2 is used. HSTS is one switch.

Compression and caching

gzip and long-lived caching of static assets are switches on each site.

Routing

Static files, a single-page app or clean URLs, a not-found page of your own, and files that are never served.

Rate limits

Each visitor’s address is limited on app routes. Past the limit the edge answers 429 before the request reaches your app.

Your own directives

Add response headers and other load balancer directives to a site or app, on paid plans. The platform rules always run first.

Behind Cloudflare

Keep a proxy such as Cloudflare in front of your domain. The domain is verified by its TXT record and the proxy holds the certificate.

Edge and security

Apps are kept apart

Many accounts share the machines of a realm, so every container is treated as untrusted.

A container each

Every app runs in its own container with every Linux capability dropped and limits on processes, open files and disk IO.

A firewall on every machine

Containers cannot reach the platform, the machine’s management ports or outgoing port 25. Apps send mail through an SMTP server instead.

Abuse detection

Patterns that look like mining, spam or scanning are flagged and looked at, so one tenant cannot slow the rest down.

Edge and security

Who it is for

Site owners

WordPress and PHP sites protected without a security plugin.

Developers

HTTPS, HTTP/2 and headers without writing load balancer config.

Agencies

The same rules on every client site, updated for all of them at once.

  • WordPress hardening
  • Security headers
  • Single-page apps
  • Public APIs
Edge and security

Blocked before it reaches your code

The exploit rules are part of the platform, not of your app, and there is no switch to turn them off. Each kind of resource gets its own set, so nothing legitimate is refused. A new rule reaches every site and app within minutes. /.well-known/ is never blocked, so certificates keep working.

Every site and app

  • PaPath traversal
  • SySystem files
  • DoDotfiles such as .env and .git
  • VuVulnerability scanners
  • LoLog4Shell lookups

Static sites

  • BaBackup files such as .bak and .sql
  • PHPHP probes
  • ReRead-only methods

PHP apps and WordPress

  • SQSQL injection
  • PHPHP stream wrappers
  • BaBackup files
  • cocomposer.json and vendor/
  • phphpinfo.php

WordPress

  • wpwp-config
  • xmxmlrpc.php
  • PHPHP in uploads
  • dedebug.log
  • InInstall pages
  • UsUser listing by ?author=

Registry and log collector

  • OnOnly their own API paths

Start with a free static site

Add resources when you need them.