Backend architecture, authentication, payments and platform migration — written from code that runs, with working examples in every article.
How to lay out a server that is still readable at the tenth endpoint.
Handler, service, repository — where each piece belongs, why internal/ exists, and how to keep the layout readable once you pass ten endpoints.
12 min
In Checkout Kit
The three models, what each costs at 10 and at 10.000 tenants, and how row-level isolation fails quietly when you get it wrong.
14 min
Tokens, sessions, and the parts every tutorial skips.
Signing and parsing claims, wiring auth middleware in the right order, and a refresh-token flow that survives a stolen token.
15 min
In Registration Kit
Password hashing, session versus JWT, TOTP two-factor, and password reset — the flows a login tutorial leaves you to figure out alone.
16 min
In Registration Kit
The failure modes that only show up in production.
What actually has to move when the managed service stops fitting.
The frontend exports clean. Auth, storage and the data do not. What each piece costs to move, in the order that keeps the app running.
14 min
Two different answers to two different problems. Self-hosting moves the ops burden to you and keeps the architecture; owning a backend changes the architecture. When each one is right.
13 min
What you gain, what you give up, and what you have to build yourself.
What per-seat scheduling actually costs at 10 and 50 users, what you give up by running it yourself, and the parts nobody warns you about — timezones, DST and double-booking.
12 min
In Booking Kit
MAU pricing, what you actually need versus what they sell, and an honest list of what you take on when you own authentication yourself.
14 min
In Registration Kit
Everything in these guides is already wired in the starter kits — Go or Node backend, MUI or Tailwind frontend, field-level RBAC, Stripe. Full source, one-time, self-hosted.
See the starter kits© 2026 Dashforge-UI · Ken Saadi