OpenWonton Reference Platform

Start here for the Hetzner + Chubo reference lane.

End Goal

This repository exists to improve the practical stance of the Chubo + OpenWonton + OpenGyoza stack versus Kubernetes without reproducing Kubernetes-level platform complexity.

The target is a platform that is:

• simple enough to reason about,
• complete enough to be credible,
• validated enough to trust,
• documented enough to teach.

In practical terms, this repo is meant to be the canonical, reproducible, operator-grade blueprint for running that stack on a real cloud lane.

OpenWonton is the default scheduler; use the wonton CLI (Nomad-compatible API/tooling). Terraform provider name nomad remains unchanged where required by ecosystem tooling. OpenGyoza is the canonical service-discovery nomenclature; consul names remain only where compatibility interfaces still require them.

Structure (in progress)

• docs/ Golden paths, architecture, component guides.
• infra/ OpenTofu modules + environment wrappers.
• images/ Chubo artifact intake helpers/docs (hcloud lane).
• packs/ OpenWonton packs in Nomad Pack format for platform, apps, and patterns.
• ci/ Checks and integration scaffolding.
• scripts/ Helper tooling.

Terramate

This repo uses Terramate to orchestrate infrastructure stacks and their dependencies. Stacks live under infra/envs/* with stack.tm.hcl.

Primary scripted workflow for the active lane:

cd infra/envs/hetzner-chubo
terramate script run deploy

Reference docs

• Docs home: docs/README.md
• Spec: docs/architecture/reference-platform-spec.md
• Plan: docs/architecture/reference-platform-plan.md
• Architecture index: ARCHITECTURE_INDEX.md

Rollout order (active)

1. Hetzner on Chubo hcloud artifacts.
2. Chubo-only cloud lane is active in this repository.

Current migration status (2026-02-24)

• Hetzner Chubo scaffolding is now in infra/envs/hetzner-chubo with pinned image inputs, Terramate deploy/bootstrap/smoke scripts, and validation helpers.
• Secondary-lane material has been decoupled from active lane guidance in this repo.
• The active Hetzner lane can now optionally create and destroy a Hetzner Cloud DNS zone for platform-owned domains; this is the current foundation for external DNS work on wizerd.dev.

Legacy module

The existing Hetzner module now lives at infra/modules/provider-hetzner.