Purpose-built web serving
Simply serve.
Paranoid by design.
In the post-AI world the complexity of modern software and processors just means increased attack surface.
HewnWeb does one job, and does it well: it serves content directly from hardware, with deliberately limited capabilities and narrowly defined interfaces.
There's no software libraries with hidden flaws waiting to be exploited, and no general-purpose processor to execute them on.
Just high-performance dedicated web-serving hardware, and only exactly what's needed to support it.
Why build it this way? ↗
Understandable.
Trust begins with knowing what a system can—and cannot—do.
Laser-focused.
Only the capabilities needed for the job, with no implicit privileges waiting to be exploited.
Sovereign.
Own your hosting, make your boundaries defendable, manage changes on your terms.
The approach
An attacker can't exploit what isn't there.
Conventional Internet services bring operating systems, runtimes, libraries and plug-ins into the exposed serving path. All that flexibility has a cost: more code to assess, maintain and defend.
HewnWeb takes a different approach. Its serving engine is digital hardware. Functions are divided into compartments with specific jobs. Their interfaces carry only the operations and information they need.
That matters when something goes wrong. A weakness in one compartment should not make the rest of your system a soft target. Hardware-enforced boundaries make that separation a property of the design, rather than another policy for software to remember.
No design is magically immune to bugs. But HewnWeb is designed to limit the consequences of bugs, bad data and configuration errors. The point is to reduce opportunities for faults to become system-wide compromises—and to make the remaining behaviour possible to understand and inspect.
Risk assessment / URL handling
What if the URL parser has a bug?
URL parsing is one of many functions in a web server. Here we assess one specific threat: a crafted URL triggers a defect in request parsing or routing, and the attacker attempts to turn that defect into unauthorised access to customer data.
We compare two defined server configurations that run business applications against a back-end SQL database. Each is assessed with its stated access controls in place. The likelihood score describes escalation from the parser defect to serious harm, not the frequency of parser bugs. Everyone sees and assesses risk differently. This is how we see it using the ENISA's EU Risk Management Toolbox.
01 / Software web server + SQL database
A parser defect reaches a privileged process.
Configuration assessed. A typical software-based web server executes server-side application code and connects to a back-end SQL database using application credentials. Firewall rules permit only the database's SQL port; SSH and direct access to other internal servers are blocked.
Assessment notes
- Failure path: Exploitation of the URL parser gives the attacker control of the serving process, including its application environment and database credentials.
- Remaining authority: The permitted SQL connection remains available. The compromised process can issue queries within the database account's privileges, including access to records of all customer. The normal HTTP response path can carry stolen data back to the attacker.
- Controls credited: The firewall blocks SSH and unrelated internal network access. It does not constrain the SQL statements sent over the permitted port. It relies on the database credentials being correct to limit further damage.
- Likelihood of serious exploitation
- High our assessment
- Potential business impact
- Very high customer-data exfiltration
- Assessed risk
- Very high
Software web server: likelihood ↓ · impact →
| Likelihood | VL | L | M | H | VH |
| Very high | M | M | H | VH | VH |
| High | L | M | H | H | VH● Selected assessment. |
| Moderate | L | L | M | H | H |
| Low | VL | L | M | M | H |
| Very low | VL | VL | L | L | M |
02 / HewnWeb + controlled database portal
A parser defect meets independently enforced limits.
Configuration assessed. A hardware URL-parser state machine is separate from session management, script execution and the database portal. Only the database portal, which accepts only script-specific templated queries, can communicate with the back-end database. The parser has no CPU, shell or general-purpose network interface to commandeer.
Assessment notes
- Failure path: A URL-routing error selects the wrong publicly available file or requests the wrong script. Independent session and script-authorisation checks still apply.
- Remaining authority: An authorised script runs only within that script's defined capabilities and the requester's session. It cannot access other scripts' contexts or create arbitrary database operations.
- Controls credited: The portal accepts authorised query-template identifiers and typed parameter values—not SQL text from scripts. It enforces session user-ID filtering, row-ownership rules, and hardware limits on returned rows and values.
- Blocked escalation: The parser cannot open an SQL connection, submit arbitrary SQL, change database access rules or bypass the independent session and portal checks. It cannot access data related to other customers.
- Likelihood of serious exploitation
- Low our assessment
- Potential business impact
- Low bounded, session-scoped effects
- Assessed risk
- Low
HewnWeb: likelihood ↓ · impact →
| Likelihood | VL | L | M | H | VH |
| Very high | M | M | H | VH | VH |
| High | L | M | H | H | VH |
| Moderate | L | L | M | H | H |
| Low | VL | L● Selected assessment. | M | M | H |
| Very low | VL | VL | L | L | M |
Reading the matrices: VL = very low; L = low; M = moderate; H = high; VH = very high. The dot marks our rating of this scenario. Row = likelihood of serious exploitation; column = business impact. Colours supplement the printed ratings.
These are our assessments of the stated configurations. You should apply your own due-diligence. But we're confident that hardware-enforced compartmentalisation changes the answer in HewnWeb's favour.
Or to put it bluntly: which set of risks would you rather be responsible for managing?
Made to be owned
Serious capacity. Modest machinery.
HewnWeb's hardware does just one thing: Serve web content.
From 100Mbps to 10Gbps or more, a single HewnWeb unit can serve a lot of content for just a few watts.
Keep management separate from public serving. On configurations that support it, use a physically isolated management path—or require physical access for changes. Internet traffic has literally no way to get to your database servers -- except through the specific database queries your application authorises.
Even if your business logic has a bug that attackers might try to exploit, row count limits and row owner rules are enforced in hardware.
The result is applications that run fast, alert you to many sorts of logic errors automatically, and add yet more layers of pain to attackers trying to steal your data.
Self-host when it makes operational and economic sense. Use external hosting when it doesn't. Either way, HewnWeb gives you a unique kind of control of the serving engine and the security boundaries around it.
Trust, not theatre
Know what it's doing.
HewnWeb's server is a few hundred thousand lines of VHDL -- including the network stack, memory controller, dynamic content generators and everything else.
That may sound like a lot.
It is.
But compare that to the tens of millions of lines of software that a conventional web server depends on -- including layers of dependencies outside of your control, and outside the control of the web server vendor.
It all just creates tens of millions of opportunities for attackers to find a way in to the general-purpose processor that will give them the keys to the castle.
HewnWeb's attack surface is tiny in comparison, and in the unlikely event a hacker finds a way in, there's not even a processor to execute their code on.
There's no general-purpose network stack available to leverage to attack other systems.
The straitjacket stays firmly in place.
HewnWeb's real-time console and hardware-enforced logging provides instant insight to server health, load, server errors, and whether it's under attack.
If something is going wrong, you can see it.
Need to reboot the web server for any reason? It's back and serving before most network switches have had time to negotiate link speed.
No operating system means no lengthy boot process.
Built by engineers
Old-fashioned restraint. Modern hardware.
HewnWeb draws on decades of insight into networking, resilient communications and FPGA development -- and matches that with hardware designed for the task.
You don't make web serving secure by adding new complicated layers.
You make it secure by taking away anything that isn't absolutely needed, then making what's left rock-solid.
This website is served by HewnWeb.