Core Concepts

Anode Overview & The 4 Pillars

Every time you build a Go backend, you declare your architecture twice: once in Go (invoking sql.Open, listening on ports, registering routes), and again in YAML (multi-stage Dockerfiles, 50-line compose files, port maps, env lists).

Anode eliminates configuration drift by analyzing your Go source code using compiler-backed Static Single Assignment (SSA) and Variable Type Analysis (VTA) call graphs rooted at func main(). It extracts an immutable, human-readable anode.lock.json and deploys directly to Linux VPS bare-metal primitives: systemd, cgroups v2, loopback proxies, and automated Let's Encrypt TLS.

Zero Proprietary SDKs

Write idiomatic Go with stdlib database/sql, net/http, and official drivers. Never import vendor-locked libraries.

Bare-Metal Performance

Deploys to Linux systemd with 8ms cold starts and 4.8MB RAM footprint compared to 180MB+ container runtime overhead.

The 4 Pillars of Topology Engine

1. Migration-Driven ProvenanceDatabases are auto-provisioned only when verified migration assets (e.g. Goose SQL files) exist alongside the service.
2. Typed Interface LinkinggRPC stubs (NewPaymentServiceClient) and HTTP routes match 1:1 without naming heuristics.
3. Commit-Backed LockfileEvery inspect run synthesizes an immutable contract committed to Git and reviewed in pull requests.
4. Actionable Build DiagnosticsAmbiguous connection strings trigger compiler warnings with exact line numbers and concrete fix suggestions.