Software & platform index
Technology with a stated relationship—not a wall of logos.
Every page below says what the technology is and how it relates to GRID EATER. A supported technology is not silently labelled as production infrastructure.
CloudflareCore technology · Edge delivery, DNS, security and selected serverless/data services used across GRID EATER's public platform.
Cloudflare WorkersCore technology · The serverless runtime used for GRID EATER's thin public application and control boundary.Cloudflare D1Core technology · Canonical SQL authority for GRID EATER data where the platform explicitly assigns that role.Cloudflare R2Core technology · Object storage used for evidence, archive-style and other blob workloads where that role is assigned.
HetznerCore infrastructure · The heavy-compute and conventional-server powerhouse behind GRID EATER's long-running, batch and self-hosted workloads.
NGINXActive infrastructure · A conventional web-server and reverse-proxy layer used in bounded GRID EATER Hetzner services.
PostgreSQLActive infrastructure · A mature open-source relational database used for operational state in selected GRID EATER Hetzner workflows.
DockerActive infrastructure · Container packaging used for reproducible deployment of selected GRID EATER services and operational components.
Node.jsActive infrastructure · The asynchronous JavaScript runtime used extensively across GRID EATER services, tooling and operational code.
GitHubDevelopment / operations · Canonical source control, review history and controlled delivery coordination for GRID EATER code.
TypesenseCore technology · The fast visitor-facing search projection for GRID EATER Directory and Shop experiences.
Let's EncryptActive specialised component · Automated public TLS certificate issuance used where current GRID EATER server evidence confirms it.CertbotActive specialised component · An ACME client used by GRID EATER for automated certificate lifecycle work in verified server infrastructure.Google services
Business, search and commerce services.
These are supported service integrations rather than core infrastructure components.
