Armadillo

Armadillo is my auth gateway and service-scaffolding tool — a place to stand up the plumbing a new service needs without hand-wiring it every time.

Today it’s a JWT-based auth handler: a login endpoint that issues signed tokens, a /me endpoint that verifies them, and a Traefik forwardAuth config so other services can sit behind it and let Armadillo answer “who is this?” The scaffolding side — generating a service’s UI, importing an existing one, initialising CLI or workflow boilerplate, picking a deployment tier — is still ahead of it. Armadillo is early: right now it’s the auth gateway for my homelab, with the rest built out as I need it.

Armadillo is my infra scaffolding tool for bootstrapping and deploying new services into my self-hosted stack — a place to stand up the plumbing a new service needs (auth, routing, deployment config) without hand-wiring it every time. I wanted one gateway that could issue and verify tokens for the other things I run, and a growing set of scaffolding around it so spinning up the next service doesn’t mean starting from a blank directory.

Today that means a JWT-based auth handler: a login endpoint that issues signed tokens, a /me endpoint that verifies them, and a Traefik forwardAuth middleware config so other services in the stack (like ibis) can sit behind it and let Armadillo answer “who is this?” The scaffolding side — generating a new service’s UI, importing an existing service, initializing CLI or workflow boilerplate, picking a deployment tier — is still ahead of it. Armadillo is early: right now it’s the auth gateway for my homelab, with the rest of the scaffolding built out as I need it.