Architecture

Behind
the page.

A small system, built with intent.
Four stories of how this site works.

01 — Request path

Two hostnames.
One front door.

The browser makes two independent requests. First, renardarv.dev goes through host NGINX to the web container, which serves the Astro and Svelte site. Then the offer form island calls api.renardarv.dev, which goes through the same NGINX straight to the Go API container, never through the web container.CLIENTPUBLIC ROUTESHOSTAPPLICATION SERVICESBrowserPage loadhydratesOffer form0102renardarv.devapi.renardarv.devNGINXReverse proxy · hostTLS · routes by hostnameWebAstro + Svelte · staticCONTAINERAPIGo · application backendCONTAINER
One edge. Two routes. The browser talks directly to each service.

02 — AI estimate

AI, when it
adds value.

An offer draft is fingerprinted and enters the AI gate. The kill switch is checked first, then the cache. A cache hit returns the public estimate directly. A miss must pass the quota and the cost fuse before Anthropic is called; its answer becomes the public estimate.INPUTAI GATEPROVIDERRESULTcache hitOffer draftFingerprinthashwhat the offer says,as a cache keyAI gatedecided locallyKill switchCachehit →missQuotaCost fuse→Anthropicexternal modelPublic estimatefrom cachefrom the modelrange only, no reasoning
Every estimate clears local checks first. A cached answer never reaches the model.

03 — Offer handling

From offer
to delivery.

A submitted offer is validated, then saved in one SQLite transaction together with any matching assessment and its outbox delivery events. Only after the commit does an asynchronous worker deliver the owner and customer emails through Resend.REQUESTSQLITE TRANSACTIONASYNC DELIVERYSubmitoffer formValidateserver-sideSQLiteatomicOfferAssessmentif matchedOutbox eventsper emailall or nothingCOMMITdurableWorkerwith retriesResendemailOwnernotificationCustomerconfirmation
The offer is saved in one transaction. Email delivery starts only after the commit.

04 — Deployment

From commit
to production.

A push to main starts GitHub Actions. Frontend, backend and security checks run in parallel, then both container images are built, scanned and pushed to GHCR tagged with the commit SHA. Production pulls both images with Docker Compose and only counts as live once the health check passes.SOURCECI · GITHUB ACTIONSREGISTRYPRODUCTIONGit pushmainActionsGitHubFrontendBackendSecurityTrivychecks · parallelBuild2 imagesGHCRprivateweb:<sha>backend:<sha>commit SHA · no latestProductionone hostDeployComposeHealth checkweb + APIserving
Checked, scanned and pinned to the commit. A release counts only once the health check passes.