Abandoned Go projects

Vessel schedules containerized tasks with cron syntax and DAG dependencies. Used to power my side project's data pipeline. I built it because AWS Batch was overkill and Airflow was too much. I'm leaving because I don't run side projects with data pipelines anymore. The scheduler works, the queue is solid, the UI is functional. The Docker socket handling is the part I'm most proud of.

Anvil unifies AWS, GCP, and Cloudflare under one command surface. I built it because I kept switching between clients with different cloud setups. It's not a wrapper — it's a meta-tool that translates your intent to the right provider. I left it when I took a job that uses AWS only. The community picked it up. There's a maintainer team of 3 now.

Driftwood was my weekend project for two years. It served my own blog for 18 months. It does exactly one thing: turns a folder of .md files into a static site. Has RSS, has tags, has a theme system. Doesn't have a build step. Doesn't have a config file. Just runs. It taught me a lot about Go templates. I don't blog publicly anymore (moved to paper journals), so it has no user. Would love to see it find one.

Vellum is a 4k-line Go program that turns MDX into static HTML. No JS, no hydration, no client framework. I built it because every other SSG I tried had a config file longer than my actual content. Vellum has zero config. The trade-off: you can't extend it. That's by design. Maintenance was light — I'd update a dependency every 3 months. I stopped when the Go ecosystem moved to generics and I didn't want to do the migration.