[ blog ]
Field notes
from the edge.
Deep dives into deploy pipelines, edge routing and the infrastructure decisions behind weond. Written by the people who build and operate it.
DeploysZero-downtime deploys: what actually happens after git push
A commit is not a deployment. Here is the full path a push takes through builds, health checks, traffic swaps and rollbacks — and the queue that keeps every release reversible.
Why the weond edge proxy is written in Rust
A request has roughly 15 milliseconds to be understood, authorized, routed and answered. Here is why we rewrote our edge layer in Rust — and what we gave up to get there.
Durable queues: retries without the mystery
Retries are easy to add and hard to make honest. A look at leases, idempotency keys and dead-letter replay in the queue that powers background work on weond.
Sealing secrets per project, not per workspace
Environment variables used to be a workspace-wide convenience. Now every secret is encrypted per project with bound context, rotated independently and never returned in plaintext.