Stax Digital Garden

HAR-1010 - The Harbor Renderer Roadmap

4 min read

Living Document Notice
Published 2026-09-19. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

The Harbor Renderer Roadmap

The Harbor Renderer Roadmap: Electric cyan P11 vector CRT macro showing polyphonic Lissajous curves and radiating forward-projecting vector field

Summary

The Harbor edge renderer began as a lightweight Hono service deployed inside Docker containers on single-tenant virtual private servers. While containerized Node and Bun environments satisfy current operational demands, scaling an independent publishing network across geographically dispersed edge locations requires reducing operational surface area: eliminating container runtimes, packaging self-contained native binaries, and supporting serverless execution at the CDN perimeter.

This roadmap details the planned architectural evolutions for Harbor across three milestones: compiling the rendering engine into standalone native binaries with embedded SQLite content caches, deploying zero-cold-start edge workers across Cloudflare Workers and D1, and implementing automated multi-origin failover across independent cloud providers.

Target Architectural Evolution

Harbor transitions from an interpreted Node/Bun container workload to a zero-dependency compiled artifact capable of deploying across heterogeneous host environments.

Current State (v1.x)                  Mid-Term Milestone (v2.x)                 Target Architecture (v3.x)
┌───────────────────────┐            ┌───────────────────────────┐             ┌───────────────────────────┐
│ Containerized Runtime │            │ Standalone Native Binary  │             │ Global Edge Workers Mesh  │
│ Docker + Bun + Hono   │    ───►    │ Single Mach-O/ELF Binary  │     ───►    │ Cloudflare Workers + D1   │
│ Directus via REST     │            │ Embedded SQLite/DuckDB    │             │ Multi-Origin Failover     │
│ 45 MB RSS Footprint   │            │ 12 MB RSS Footprint       │             │ Zero Origin Server Fleet  │
└───────────────────────┘            └───────────────────────────┘             └───────────────────────────┘

1. Standalone Native Binary Compilation

By compiling Harbor using native bundlers (Bun Single-File Executables or Go/Rust cross-compilation), deployment simplifies to scp-ing a single static ELF binary to the host. The executable embeds all HTML templates, routes, and baseline CSS stylesheets directly in the .text segment of the binary. No Node modules, container engines, or runtime package managers are required on host nodes.

2. Edge Execution via Cloudflare Workers and D1

Porting the Hono route tree to Cloudflare Workers allows Harbor to execute within V8 isolates across more than 300 edge cities worldwide. Directus content updates will replicate to Cloudflare D1 (edge SQLite) and KV storage. When an author publishes a note, the markdown transforms into edge-accessible database rows, completely bypassing the origin server for public readership.

3. Multi-Origin Failover and Distributed Health Probing

To ensure continuous availability, Harbor’s perimeter proxy layer will monitor multiple origin nodes across distinct VPS providers. If the primary origin fails health checks or exceeds 2,000ms latency, traffic routes to a secondary standby node hosting a synchronized read replica.

MilestoneRuntime TargetDeployment ArtifactPrimary Data StoreMemory BaselineCold Boot Time
v1.4 (Current)Node / Bun on LinuxDocker Container ImageDirectus REST / Postgres~35 MB – 55 MB250ms – 400ms
v2.0 (Planned)Native Compiled ELFStatic Binary (~22 MB)Embedded SQLite + WAL~12 MB< 15ms
v2.5 (Edge)Cloudflare WorkersWebAssembly / JS BundleCloudflare D1 + KV< 5 MB (Isolate)< 5ms
v3.0 (Mesh)Geo-Distributed Multi-CloudMulti-Region Container/BinRaft Replicated SQLite~20 MB per nodeInstant

Native Compilation and Edge Worker Configuration

Harbor v2 builds via standalone compilation scripts, producing zero-dependency executables:

#!/usr/bin/env bash
# Build script: Compile Harbor Hono application into single ELF executable
 
set -euo pipefail
 
echo "==> Bundling Harbor assets and routes..."
bun build ./src/index.ts --compile --minify --sourcemap=none --outfile ./dist/harbor-edge-linux-x64
 
echo "==> Verifying binary symbols and size..."
strip ./dist/harbor-edge-linux-x64
ls -lh ./dist/harbor-edge-linux-x64
file ./dist/harbor-edge-linux-x64

For Cloudflare Workers edge deployment, Harbor targets the standard Hono worker interface via wrangler.toml:

name = "harbor-edge-worker"
main = "src/worker.ts"
compatibility_date = "2026-09-10"
compatibility_flags = ["nodejs_compat"]
 
[vars]
ENVIRONMENT = "production"
CANONICAL_DOMAIN = "bosunpkm.com"
 
d1_databases
binding = "DB"
database_name = "harbor_edge_db"
database_id = "d1-prod-harbor-uuid-4481"
 
[placement]
mode = "smart"

Binary Inspection and Verification Commands

Inspect and benchmark compiled release candidate binaries:

# Verify shared library dependencies of compiled binary (must show statically linked or minimal libc)
ldd ./dist/harbor-edge-linux-x64 || otool -L ./dist/harbor-edge-linux-x64
 
# Test execution and inspect memory footprint via systemd-run
systemd-run --scope -p MemoryMax=32M ./dist/harbor-edge-linux-x64 --port=8080
 
# Probe health endpoint on compiled standalone runner
curl -i http://127.0.0.1:8080/healthz
 
# Dry-run Cloudflare Worker deployment
npx wrangler deploy --dry-run --outdir=./dist/worker-bundle
  • Directus Target: harbor
  • Garden Source Reference: [HAR-1010 - The Harbor Renderer Roadmap](HAR-1010 - The Harbor Renderer Roadmap), MOC - Harbor Ecosystem, MOC - Local-First Systems and Synchronization, MOC - Bosun PKM Tools

Graph View