app
Application lifecycle
Wire components explicitly and coordinate their startup, route registration, and shutdown.
Open source · Apache-2.0 · Go, htmx, Postgres
A Go toolkit for server-rendered web applications. Use its packages for auth, jobs, mail and more, or let hm build features from a plan you approve.
app
Wire components explicitly and coordinate their startup, route registration, and shutdown.
config
Load and validate the configuration your application needs at startup, with clear defaults and overrides.
settings
Define typed, validated settings that can change while the application runs, separately from startup configuration.
web · htmx · ui
HTTP helpers, template rendering, forms, and UI primitives. Add interaction to server-rendered pages with htmx.
db
Connect to Postgres, apply SQL migrations, and wire the database into your application components.
auth
User sign-up, sign-in, sessions, and authentication middleware. Use roles to control access.
mailer
Use the Mailer interface with SMTP, SES, SendGrid, or Mailgun. Change providers without changing how your application sends email.
scheduler
Schedule and run background work with a Postgres job store, replaceable through the JobStore interface.
pubsub
Connect components through events using Publisher and Subscriber interfaces, with a Postgres backend included.
hm, the builder
hm is a terminal conversation that can create an application, add a feature, or add a field or validation rule, always with HatMax's own primitives. It can't swap your stack or write arbitrary code.
Every change starts as a sealed plan. Nothing touches your files until you approve it with Ctrl+A. Then HatMax renders the code and runs the project checks.
Howhm works
Start an application
“Create an inventory application with a product feature.”
Keep developing it
“Add a required SKU and an optional reorder level to product.”
$ hm · or hm generate "…" for scripts